Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 16 Jul 2017 14:02:22 -0400
From:      Tom Lane <tgl@sss.pgh.pa.us>
To:        Roger Leigh <rleigh@codelibre.net>
Cc:        FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>
Subject:   Re: Booting 11-stable problem on a G4 mac mini
Message-ID:  <8068.1500228142@sss.pgh.pa.us>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
Roger Leigh <rleigh@codelibre.net> writes:
> On 17/09/16 15:06, Roger Leigh wrote:
>> gem0: 10kB RX addr......
>> gem0: Ethernet address .......
>> cryptosoft0: <software crypto> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8068.1500228142>