Date: Thu, 10 Nov 2016 11:24:12 -0800 From: Tamiji Homma <tamiji@me.com> To: Justin Hibbits <jhibbits@freebsd.org> Cc: freebsd-ppc@freebsd.org Subject: Re: FreeBSD 11 on PowerBook G4 Message-ID: <248A0F3E-7456-4470-83CA-A2FE19759FE9@me.com> In-Reply-To: <20161108205349.1b5b26a6@zhabar.knownspace> References: <9421DD34-95A4-4435-84CB-D9C3A1D52DC5@me.com> <20161108205349.1b5b26a6@zhabar.knownspace>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Justin, I=E2=80=99ve tried following FreeBSD 12 snapshots from ftp.freebsd.org FreeBSD-12.0-CURRENT-powerpc-20161021-r307747-disc1.iso FreeBSD-12.0-CURRENT-powerpc-20161031-r308137-disc1.iso Both installed OK but both kernels didn=E2=80=99t boot. After kernel = started, screen went blank and nothing. It is different from fatal kernel trap on FreeBSD 11-RELEASE. Is your Oct 31st snap same as what I tried or something different, you = built from the source code? sha256: 01641184c3fc4d434cb475d754c62f2bc2f8b92ffefaf0ffba907bee904b8aa5 = FreeBSD-12.0-CURRENT-powerpc-20161031-r308137-disc1.iso Tammy > On Nov 8, 2016, at 6:53 PM, Justin Hibbits <jhibbits@freebsd.org> = wrote: >=20 > On Tue, 08 Nov 2016 18:34:09 -0800 > Tamiji Homma <tamiji@me.com> wrote: >=20 >> I=E2=80=99ve been running FreeBSD-ppc on PowerBook G4 1GHz/1GB DRAM = since >> 9.1-RC2. I upgraded to 10.2 some time back. It works fine. >>=20 >> I gave it a try 11.0. Installer worked flawlessly but installed >> kernel crash during boot. >>=20 >> Since it reboots spontaneously, I couldn=E2=80=99t write it down. I >> video-captured screen and took a snapshot. >>=20 >> Here is screenshot fatal kernel trap. >> http://www.pbase.com/tammyhomma/image/164488840/original=20 >>=20 >> Anyone seen this? >>=20 >> I also tried Nov. 6th 11-stable snapshot. Kernel crashes at the same >> point. >>=20 >> Thanks. >>=20 >> PS: I installed 10.3 for now and it works. >>=20 >> Tammy >=20 > Hi Tammy, >=20 > 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. >=20 > - Justin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?248A0F3E-7456-4470-83CA-A2FE19759FE9>