Re: panic at serial boot

On Tue, Apr 02, 2013 at 08:23:20PM +0200, mh_at_kernel32.de wrote:
> Hi Konstantin,
> 
> Am 2013-03-27 15:33, schrieb mh_at_kernel32.de:
> > Am 2013-03-27 14:32, schrieb Konstantin Belousov:
> >>
> >> Do you use preload md(4) ? If yes, try the following patch:
> >>
> >
> >
> > Not sure whether time permits that today, but I'm starting right 
> > away.
> >
> Had no time before easter, but I tried it now.
> This time, no panic, but also it doesn't continue to boot ;)
> 
> This is the last output I can see:
> ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 1 vector 48
> ioapic0: routing intpin 3 (ISA IRQ 3) to lapic 2 vector 48
> ioapic0: routing intpin 9 (ISA IRQ 9) to lapic 3 vector 48
> ioapic0: routing intpin 16 (PCI IRQ 16) to lapic 4 vector 48
> ioapic0: routing intpin 20 (PCI IRQ 20) to lapic 5 vector 48
> ioapic0: routing intpin 21 (PCI IRQ 21) to lapic 6 vector 48
> msi: Assigning MSI-X IRQ 264 to local APIC 7 vector 48
> SMP: passed TSC synchronization test
> TSC timecounter discards lower 1 bit(s)
> Timecounter "TSC-low" frequency 1300027430 Hz quality 1000
> WARNING: WITNESS option enabled, expect reduced performance.
> Root mount waiting for: usbus2 usbus1 usbus0
> uhub1: 2 ports with 2 removable, self powered
> uhub2: 2 ports with 2 removable, self powered
> uhub0: 2 ports with 2 removable, self powered
> Root mount waiting for: usbus2 usbus0
> ugen0.2: <vendor 0x8087> at usbus0
> uhub3: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> 
> on usbus0
> ugen2.2: <vendor 0x8087> at usbus2
> uhub4: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> 
> on usbus2
> Root mount waiting for: usbus2 usbus0
> uhub3: 6 ports with 6 removable, self powered
> uhub4: 8 ports with 8 removable, self powered
> ugen2.3: <vendor 0x0424> at usbus2
> uhub5: <vendor 0x0424 product 0x2660, class 9/0, rev 2.00/8.01, addr 3> 
> on usbus2
> Root mount waiting for: usbus2
> uhub5: 2 ports with 1 removable, self powered
> Trying to mount root from ufs:/dev/md0 []...
> start_init: trying /sbin/init
Good, thank you for testing.

> 
> And it stayed there for the last 10 minutes.
> 
> What can I do now?
I booted the image in qemu, initially there were no output on the
screen. In fact, the system is very much alive, I broke into the
debugger several times, and saw the tar/xz/sh working. More, after some
time, I got a login: prompt.

I have no idea what to expect from this thing, should it output anything
after the kernel finished initializing, and why it sit there for 10 minutes.

Try breaking into the debugger and see where it progresses. To do this,
you would need to boot with the 'boot -d' command from the loader prompt,
then do 'w kbd_break_to_debugger 1', then ctrl-alt-esc when you want to
activate the debugger. In the debugger, start with the 'ps' command.

> 
> thanks and best regards,
> Marian
> 
> PS.: FWIW, the image I build via mfsbsd is here: 
> http://mon.kernel32.de/mfsbsd-se-CURRENT-mdpatch.iso
> And the hd image used for pxe booting is this one: 
> http://mon.kernel32.de/FreeBSD-10.0-CURRENT-amd64.hd
> 
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"