The break sequence on more recent builds of OpenSolaris was changed to
"Shift-Pause" but I forget which build this came in.
Also note that if the console is in graphics mode, the kmdb prompt may
have come up behind the graphics screen (we make no attempt to switch
back to text mode). You can try typing this:
$<systemdump
(followed by return) although you'll be typing blind. Try it a few times
in case you mis-spell it.
You can try setting the deadman timer (although I've not often seen
cases that this can recover from, if the hardware is truly hung).
Add "set snooping=1" to /etc/system and reboot.
This enables a timer, which will try and panic the system after 50
seconds of inactivity. However, if the hardware has gone out to lunch
and not returned, it may not be able to trigger a panic.
You might also get more help by posting some details about your system,
hardware config, OS build, etc...
Regards,
Brian
Saadia Fatima wrote:
How can I catch a system panic/freeze. I tried booting up with a kernel debugger, with -k option in the GRUB menu. When the system freezes how can I switch to the debugger? I tried f1+shift+a but it did not work.
Thanks
SF
--
Brian Ruthven
Solaris Network RPE (Sustaining)
Oracle UK
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
