Thank you all for the very quick and informative responses. If it
happens again, I will try to get a core out of it.
Chris
___
zfs-discuss mailing list
zfs-discuss@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
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 $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
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 forc
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 maili
