From owner-freebsd-stable@FreeBSD.ORG Sun Apr 10 13:49:24 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0667616A4CE for ; Sun, 10 Apr 2005 13:49:24 +0000 (GMT) Received: from mail22.sea5.speakeasy.net (mail22.sea5.speakeasy.net [69.17.117.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 941F643D2D for ; Sun, 10 Apr 2005 13:49:23 +0000 (GMT) (envelope-from omniBSD@speakeasy.net) Received: (qmail 15892 invoked from network); 10 Apr 2005 13:49:23 -0000 Received: from acute.anhedonia.com (HELO [10.20.30.10]) (omni@[66.93.24.213]) (envelope-sender ) by mail22.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 10 Apr 2005 13:49:22 -0000 Message-ID: <42592FBD.1070903@speakeasy.net> Date: Sun, 10 Apr 2005 08:53:01 -0500 From: Ash User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20041104 Netscape/7.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Jeremy References: <4258324D.8070405@speakeasy.net> <20050409220331.GF89047@cirb503493.alcatel.com.au> In-Reply-To: <20050409220331.GF89047@cirb503493.alcatel.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: 5.4-RC1 Freezing, but pingable (may be related to gvinum) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Apr 2005 13:49:24 -0000 Peter Jeremy wrote: > On Sat, 2005-Apr-09 14:51:41 -0500, Ash wrote: > > This is consistent with the kernel continuing to run normally but being > unable to schedule userland processes - usually due to a deadlock. > > Do the caps-lock, num-lock, scroll-lock buttons on a local keyboard > still toggle the relevant LEDs? > > Assuming the LEDs toggle: Do you have "options DDB" and "options KDB" > in your kernel? If so, can you break into DDB? (If not, I think > you'll need to build a kernel with DDB). Once the system has hung, > you need to enter DDB and run 'ps'. The output from that will give > (hopefully) give an indication as to what is going wrong (and where to > look next). If you've build the kernel with debugging symbols and got > a dump device enabled, "call doadump()" should also generate a > crashdump which will be much easier to examine. > Peter, Thanks for the reply. I should have included this information in my initial e-mail: I did not have a keyboard connected to the system before either crash. I did plug a keyboard in after the crash out of desperation. The keyboard LEDs were not responsive. However, it's a ps/2 keyboard, which does not get detected by this system unless it's plugged in before the machine POSTs. I did not have DDB/KDB compiled in my kernel at the time, so I wasn't able to try to break into a debugger from the serial console. Shortly after the second crash I recompiled the kernel with DDB/KDB. Essentially at this point I'm just waiting for another crash to see if I can get get into DDB from the serial console. I was hoping that someone on the list may have run into a similar issue with 5_4_0 so that I could at least figure out how to reproduce the problem rather than simply waiting for the machine to hang again. Patience is not my greatest virtue :) -Ash