Le dim. 20 oct. 2019 à 18:30, Michael <macallan%netbsd.org@localhost> a écrit :
> That's what I use for development, but ofwboot.xcf loaded from a HFS+
> partition should be able to load a kernel from a netbsd partition.
OK thanks, I'll try that - though I can't remember finding a syntax
for that. How do you tell ofwboot the partition ?
(I have a dedicated drive for NetBSD, HFS+ w/ kernel on 3, root is on
5 IIRC, swap on 6, working OSX on another drive).
> How far into the boot process does that happen?
> Or rather, what's the kernel output right before the KASSERT fires?
After the fans (three lines of "Using X fans for Y") and one more line
(vmmask 3fc0000 schedmask ...), there's one line 'cpu1 started', then
an immediate panic with the assert.
Then the kernel dump a cpu1 traceback (only addresses), and then
"Failed to pause: cpu0".
Then "Stopped in pid 0.16 (system) at ...", this one without a timestamp first.
Then the db{1} prompt, and the cooling system goes full power (which
is a bit scary, that machine is _noisy_, though not the worse I own
;-) ).
Then - nothing. Seems dead.
> Do all CPUs attach? If so, are there error messages between / around
> their output?
I don't see anything in that visible last screen about anything other than cpu1.
> Meanwhile, please send me the dmesg and ofctl -p output.
dmesg is there: <https://dmesgd.nycbug.org/index.cgi?do=view&id=5164>
(from a working boot using 1 cpu only).
I attach to this mail the (compressed) ofctl output.
In case this fails, it's also here : <http://dl.free.fr/wvH7CyYoV>.
Thanks a lot! & cordially,
--
Romain Dolbeau
Attachment:
ofctl-p.txt.gz
Description: application/gzip