From owner-freebsd-ppc@freebsd.org Sun Jan 15 21:24:25 2017 Return-Path: Delivered-To: freebsd-ppc@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 86E0FCB1E1A for ; Sun, 15 Jan 2017 21:24:25 +0000 (UTC) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) (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 5229F1C44; Sun, 15 Jan 2017 21:24:25 +0000 (UTC) (envelope-from tgl@sss.pgh.pa.us) Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v0FLGPum021670; Sun, 15 Jan 2017 16:16:25 -0500 From: Tom Lane To: Justin Hibbits cc: Tamiji Homma , freebsd-ppc@freebsd.org Subject: Re: FreeBSD 11 on PowerBook G4 In-reply-to: <20161108205349.1b5b26a6@zhabar.knownspace> References: <9421DD34-95A4-4435-84CB-D9C3A1D52DC5@me.com> <20161108205349.1b5b26a6@zhabar.knownspace> Comments: In-reply-to Justin Hibbits message dated "Tue, 08 Nov 2016 20:53:49 -0600" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <21668.1484514985.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Sun, 15 Jan 2017 16:16:25 -0500 Message-ID: <21669.1484514985@sss.pgh.pa.us> X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jan 2017 21:24:25 -0000 Justin Hibbits writes: > Tamiji Homma wrote: >> Since it reboots spontaneously, I couldn’t write it down. I >> video-captured screen and took a snapshot. >> Here is screenshot fatal kernel trap. >> http://www.pbase.com/tammyhomma/image/164488840/original >> >> Anyone seen this? > Unfortunately, you're in good company with that panic. I've seen that > since at least February on my PowerBook, but haven't made the time to > track it down (11-CURRENT from mid-October 2015 worked fine). On the > bright side, though, 12-CURRENT as of October 31 works fine on my > PowerBook. I still don't have the time to bisect and track down the > cause of the problem or the fix, but if you feel like bisecting and > trying to find the snapshot that fixes the problem, that could help > narrow down where it got fixed, and a fix could be backported to > 11-STABLE. I took up the challenge of bisecting this, and it appears to be a two-year-old fault in the ofwfb screen driver. It is *NOT* fixed in CURRENT, at least not as of yesterday. Details at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216123 regards, tom lane