Brian,
Yes, thanks for the "-k" flag, as that got me to root cause. I had an
older VirtualBox installed, and I could see that the vbi module wasn't
happy during loadup of it. Once I 'pkgrm' the Vbox packages, I have a
bootable system, but have other Video/Mouse issues. I see others
complaining about similar problems.
Thanks,
Jim
Brian Ruthven - Sun UK wrote:
Add the -k flag to the kernel$ line in grub and when it panics you
will be given the kmdb prompt. From here, you can get the stack trace
by typing $c. All this should be done in text mode (no splash screen,
etc...). There are no core files or messages because the panic
probably happens way before the dump device is set up, so there is
nowhere to record the crash dump yet.
I haven't tested this, but off the top of my head, typing *panicstr/s
should print out the panic string with the %d stuff unexpanded
(although you may need to drop the * from the front - I can't
remember). $<msgbuf may also work to give you the kernel message
buffer (which may contain the full panic string).
$q will quit kmdb (and reboot IIRC).
HTH
Brian
Jim Nissen wrote:
After upgrading from b111 to b117, twice, my Toshiba M5 laptop gets
stuck in a panic boot loop. I booted it in text mode, to try and
catch the panic stack, but unfortunately, it happens so fast I can't
read it. Plus, there are no core files or messages with panic string.
Any clues as to what this might be?
Thanks,
Jim
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
