Date: Fri, 10 Nov 2006 14:47:56 -0800 From: "Jack Vogel" <jfvogel@gmail.com> To: "Barry Boes" <barry.boes@acciodata.com> Cc: Scott Long <scottl@samsco.org>, RelEng <re@freebsd.org>, John Baldwin <jhb@freebsd.org>, freebsd-net <freebsd-net@freebsd.org>, jfv@freebsd.org, freebsd-stable@freebsd.org Subject: Re: EM stability Message-ID: <2a41acea0611101447j29acdc3k820276de92204735@mail.gmail.com> In-Reply-To: <17748.64782.579350.492909@gargle.gargle.HOWL> References: <17748.37662.708865.764722@gargle.gargle.HOWL> <20061110150840.GK32700@cell.sick.ru> <17748.53164.372871.270153@gargle.gargle.HOWL> <17748.64782.579350.492909@gargle.gargle.HOWL>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/10/06, Barry Boes <barry.boes@acciodata.com> wrote: > > Luck ran out. Hard "must press the reset button" hang. No console > messages. The system was idle at the time. > Is there anything you'd like me to do to attempt to narrow down the > problem or get debugging output? I do not know if the freeze was > related to em or something else. Is this a machine running some graphic head? If not can you see anything on the console? Are you sure the machine is dead, like can you get in over the network... ? One thing I often do when you are dealing with unpredictable hangs is run 'vmstat 3' on one of the virtual terminals. You might also define the kernel debugger into your kernel, its best to have a serial console for this, I've seen the hardware console be locked but the serial will still work. The only way we will track this down is thru repetitive reproduction I'm afraid. Jack
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a41acea0611101447j29acdc3k820276de92204735>