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
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 at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
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 at opensolaris.org > > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss--
Chris, To force a panic on an x86 system using GRUB, you''ll first need to boot kmdb. This can be accomplished by adding the ''kmdb'' option to the multiboot line in menu.lst. Rather than hacking your menu.lst: - power your machine on - arrow to the OS you want to boot in GRUB - type ''e'' - arrow to the line that says ''kernel /platform/i86pc/multiboot'' - type ''e'' again - type a space, then the string kmdb. It should read: kernel /platform/i86pc/multiboot kmdb - Hit return - Type ''b'' (for boot) After the system boots, you should be able to drop to kmdb via the console key sequence F1-a (simultaneously, like L1-a on SPARC machines). Once you drop to kmdb, type: $<systemdump This should dump core and reboot. This is all contingent on what caused the system to hang. You may or may not be able to get to kmdb. hth, John 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 at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss-- John Cecere Sun Microsystems 732-302-3922 / john.cecere at sun.com