From owner-freebsd-ppc@freebsd.org Sun Jul 16 18:10:08 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 2D505C0AF23 for ; Sun, 16 Jul 2017 18:10:08 +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 E98DF2D97 for ; Sun, 16 Jul 2017 18:10:07 +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 v6GI2Mjf008069; Sun, 16 Jul 2017 14:02:22 -0400 From: Tom Lane To: Roger Leigh cc: FreeBSD PowerPC ML Subject: Re: Booting 11-stable problem on a G4 mac mini In-reply-to: <40de15e2-df76-f282-dc1d-c93a9258adc5@codelibre.net> References: <252659f3-6000-d019-283a-5538bff8a3da@codelibre.net> <40de15e2-df76-f282-dc1d-c93a9258adc5@codelibre.net> Comments: In-reply-to Roger Leigh message dated "Sun, 16 Jul 2017 11:22:59 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <8067.1500228142.1@sss.pgh.pa.us> Date: Sun, 16 Jul 2017 14:02:22 -0400 Message-ID: <8068.1500228142@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, 16 Jul 2017 18:10:08 -0000 Roger Leigh writes: > On 17/09/16 15:06, Roger Leigh wrote: >> gem0: 10kB RX addr...... >> gem0: Ethernet address ....... >> cryptosoft0: on nexus0 >> and then just stops and doesn't make any further visible progress. > This continued through into 11.0-RELEASE, but when testing with -CURRENT > I now no longer even get the freeze during boot; I get a black screen as > soon as I press Enter in the bootloader and the kernel boots, and I have > no way of seeing what's going on during the boot after than point. > Has anyone else had any recent success with Mac Mini G4 hardware with > current builds? This sounds like the problem I was investigating back in January. The freeze-instantly-with-black-screen behavior happens if you have a kernel built with debug options (the default for -CURRENT). If you build without, you get a hang or kernel trap after the message about cryptosoft0. For me, reverting r269278 made both problems go away. I don't know exactly what's wrong with that patch, and haven't gotten around to poking at it further than what's described in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216123 regards, tom lane