Hm. If the system is hung, it's unlikely that a reboot -d will help.
You want to be booting into kmdb, then using the F1-a interrupt sequence then dumping using $<systemdump at the kmdb prompt. See the following documents: Index of lots of useful stuff: http://docs.sun.com/app/docs/doc/817-1985/6mhm8o5p3?a=view Forcing a crashdump on x86 boxes: http://docs.sun.com/app/docs/doc/817-1985/6mhm8o5q5?a=view And booting from grub into kmdb: http://docs.sun.com/app/docs/doc/817-1985/6mhm8o5q2?a=view I'm not sure how the serial console is going to impact you. I'm expecting it'll still be f1-a to drop to the debugger... That's assuming it's not a hard hang. :) Cheers. Nathan. On Wed, 2006-11-15 at 14:16, Sean Ye wrote: > Hi, Chris, > > You may force a panic by "reboot -d". > > Thanks, > Sean > On Tue, Nov 14, 2006 at 09:11:58PM -0600, Chris Csanady wrote: > > I have experienced two hangs so far with snv_51. I was running snv_46 > > until recently, and it was rock solid, as were earlier builds. > > > > Is there a way for me to force a panic? It is an x86 machine, with > > only a serial console. > > > > Chris > > _______________________________________________ > > zfs-discuss mailing list > > zfs-discuss@opensolaris.org > > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss -- _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
