From owner-freebsd-stable@FreeBSD.ORG Wed Jan 16 14:31:16 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E14516A41B for ; Wed, 16 Jan 2008 14:31:16 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from angel.ticketswitch.com (angel.ticketswitch.com [IPv6:2002:57e0:1d4e::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4B16513C45B for ; Wed, 16 Jan 2008 14:31:16 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from [10.50.50.2] (helo=smaug.rattatosk) by angel.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67 (FreeBSD)) (envelope-from ) id 1JF9IP-000J2V-8G for stable@freebsd.org; Wed, 16 Jan 2008 14:31:13 +0000 Received: from dilbert.rattatosk ([10.50.50.6] helo=dilbert.ticketswitch.com) by smaug.rattatosk with esmtp (Exim 4.67 (FreeBSD)) (envelope-from ) id 1JF9IP-000GvX-6Q for stable@freebsd.org; Wed, 16 Jan 2008 14:31:13 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1JF9IP-0000n5-5s for stable@freebsd.org; Wed, 16 Jan 2008 14:31:13 +0000 To: stable@freebsd.org Message-Id: From: Pete French Date: Wed, 16 Jan 2008 14:31:13 +0000 Cc: Subject: panic: vm_fault: fault on nofualt entry, addr: 81423000 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: Wed, 16 Jan 2008 14:31:16 -0000 I have an HP dc5750 workstaion and I get the following when I tryand boot it with ACPI enabled. This happens almost instantly, just after the processors are detected. I am running 7.0 these days, but I had the same issue under 6.3 (which I reported in PR 117918, though without the panic line, which I could not get our of 6.3). I just tested again with the latest 7.0 prerelease from this morning (as I saw some ACPI changes) plus the latest HP BIOS update (v02.31), but the problem still exists. I know there were problems with these machines under amd64 (the "missing BIOS smap" probkem in PR 111952), but this appears to be a different issue. Is there anything useful I can do to get a trace out at the point it panics ? It doesnt dump anything into /var/crash when it reboots, preseumably because the panic is far too ealy on in the boot process ? -pcf.