On 06/29/09 04:07 PM, 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).
Brian, thanks for that hints, there is a little reference guide about
kmdb usage (like blogs, how-to etc...)?
Thanks!
--
Luca Morettoni <luca(AT)morettoni.net> | OpenSolaris SCA #OS0344
Web/BLOG: http://www.morettoni.net/ | http://twitter.com/morettoni
jugUmbria founder - https://jugUmbria.dev.java.net/ | Thawte notary
ITL-OSUG leader - http://www.opensolaris.org/os/project/itl-osug/
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
