If you cannot use the reboot –d or the halt –d command, you can use the kernel debugger (kmdb) to force a crash dump. The kernel debugger must have been loaded, either at boot time or with the mdb –k command for the following procedure to work.
Before You Begin
Ensure that your role has the appropriate rights profiles to perform this procedure. See Using Rights Profiles to Administer Boot Features.
The method that is used to access the debugger is dependent upon the type of console that you are using to access the system.
If you are using a locally attached keyboard, press F1–A.
If you are using a serial console, send a break by using the method appropriate to that type of serial console.
The kmdb prompt is displayed.
[0]> $<systemdump
Panic messages are displayed, the crash dump is saved, and the system reboots.
This example shows how to force a crash dump and reboot of an x86 based system by using the halt –d command.
$ halt -d 4ay 30 15:35:15 wacked.<domain>.COM halt: halted by user panic[cpu0]/thread=ffffffff83246ec0: forced crash dump initiated at user request fffffe80006bbd60 genunix:kadmin+4c1 () fffffe80006bbec0 genunix:uadmin+93 () fffffe80006bbf10 unix:sys_syscall32+101 () syncing file systems... done dumping to /dev/dsk/c1t0d0s1, offset 107675648, content: kernel NOTICE: adpu320: bus reset 100% done: 38438 pages dumped, compression ratio 4.29, dump succeeded Welcome to kmdb Loaded modules: [ audiosup crypto ufs unix krtld s1394 sppp nca uhci lofs genunix ip usba specfs nfs md random sctp ] [0]> kmdb: Do you really want to reboot? (y/n) y