From owner-freebsd-current@freebsd.org Sun May 28 15:54:38 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2BC55D85786 for ; Sun, 28 May 2017 15:54:38 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (unknown [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 16D441307 for ; Sun, 28 May 2017 15:54:37 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.197] (cpe-23-242-94-236.socal.res.rr.com [23.242.94.236]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 330d5f05 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Sun, 28 May 2017 08:54:36 -0700 (PDT) To: freebsd-current@freebsd.org From: Pete Wright Subject: INO64 Effecting Firefox Message-ID: Date: Sun, 28 May 2017 08:54:35 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 May 2017 15:54:38 -0000 Hi all, I can't imagine that this is related to INO64, but since upgrading my world and kernel on drm-next (which merged upstream CURRENT as of May 27 which should include the ino64 work) I am having segfaults running firefox. Previous to this firefox was very stable for work/personal daily use. The error I'm seeing is: Full message: TypeError: malformed UTF-8 character sequence at offset 0 Firefox does start and I can load a page or two before it sefaults. The full console output is here: https://gist.github.com/anonymous/555202b1452503ad9e26750168f87d5f Posting this here in the off chance that it's either related to ino64, or some other recent change has caused this problem. Cheers! -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA