From owner-freebsd-stable@FreeBSD.ORG Mon Oct 3 20:10:52 2005 Return-Path: X-Original-To: stable@freebsd.org 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 6D90916A41F for ; Mon, 3 Oct 2005 20:10:52 +0000 (GMT) (envelope-from pckizer@nostrum.com) Received: from nostrum.com (magus.nostrum.com [69.5.195.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA96D43D46 for ; Mon, 3 Oct 2005 20:10:51 +0000 (GMT) (envelope-from pckizer@nostrum.com) Received: from [165.91.250.64] (magus.tamu.edu [165.91.250.64]) (authenticated bits=0) by nostrum.com (8.12.11/8.12.11) with ESMTP id j93KAPRK007135 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Mon, 3 Oct 2005 15:10:34 -0500 (CDT) (envelope-from pckizer@nostrum.com) In-Reply-To: <35c231bf0510031101v5572fd3fyb69e11e887d41866@mail.gmail.com> References: <200510031430.j93EUxQQ078452@magus.nostrum.com> <35c231bf0510031101v5572fd3fyb69e11e887d41866@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Philip Kizer Date: Mon, 3 Oct 2005 15:10:20 -0500 To: stable@freebsd.org X-Mailer: Apple Mail (2.734) Received-SPF: pass (nostrum.com: 165.91.250.64 is authenticated by a trusted mechanism) Cc: David Kirchner Subject: Re: 5.4 Hanging, have some DDB output, unable to get panic dump X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 20:10:52 -0000 On 10/3/05, Philip Kizer wrote: > The system was updated (from uname): > FreeBSD 5.4-STABLE #2: Wed Sep 21 15:55:00 CDT 2005 > And the console log is (2 events): > [note: machine hung, could not do anything from current logins or > running daemons] On Oct 3, 2005, at 13:01, David Kirchner wrote: > I was seeing this error with 5.4-RELEASE, on a machine with 4GB, and > when using PAE. Are you using PAE? If so, you'll need to either > upgrade to 5-STABLE or apply a 2 line patch to your 5.4-STABLE system > (the patch hasn't been committed to that branch yet, it should > probably be committed to 5-4.RELEASE-p*). You can find the patch by > searching the archives for "PAE" and "pmap.c". Thanks for the response, from what I'm finding from my search, it looks like you mean this: http://lists.freebsd.org/mailman/htdig/freebsd-stable/2005-August/ 017607.html and the referenced patch: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/i386/pmap.c.diff? r1=1.523&r2=1.524&f=h But, the version I'm running as listed above shows to have pmap.c: __FBSDID("$FreeBSD: src/sys/i386/i386/pmap.c,v 1.494.2.10 2005/08/08 15:33:53 jhb Exp $"); which already has the new code (and I'm having a hang, not the panic that was described without that patch). Or did I find some articles that was not what you were referring to? FYI: Just to describe the hang a bit more, I do get some response from the machine, it just cannot do any useful work. For instance, on the console: If I hit return at "login:", I get a new "login:" prompt, but as soon as I enter a username+^M or Ctrl-D it, I cease to receive any feedback besides terminal echo from my input. If I'm logged in on the console I can even hit return in the shell and get a new shell prompt, but any command I try (i.e. 'uptime' or 'uname') then results in the same lack of any further response. Plus, I cannot DDB "db> panic" the box as that then produces a hard-hang, so no sync+core and then I don't even get tty echo from my input. Thanks, Philip