From owner-freebsd-current@FreeBSD.ORG Tue Mar 13 00:50:46 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AD85B16A402 for ; Tue, 13 Mar 2007 00:50:46 +0000 (UTC) (envelope-from admin@garyshood.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.189]) by mx1.freebsd.org (Postfix) with ESMTP id 4F04313C44C for ; Tue, 13 Mar 2007 00:50:46 +0000 (UTC) (envelope-from admin@garyshood.com) Received: by mu-out-0910.google.com with SMTP id g7so2295915muf for ; Mon, 12 Mar 2007 17:50:45 -0700 (PDT) Received: by 10.82.167.5 with SMTP id p5mr456158bue.1173745585990; Mon, 12 Mar 2007 17:26:25 -0700 (PDT) Received: by 10.82.167.14 with HTTP; Mon, 12 Mar 2007 17:26:25 -0700 (PDT) Message-ID: Date: Mon, 12 Mar 2007 18:26:25 -0600 From: "Gary Suggett" To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mailman-Approved-At: Tue, 13 Mar 2007 01:13:08 +0000 Subject: March -Current i386 Panic on boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2007 00:50:46 -0000 Current 200702 runs and loads perfect on this machine, but can't say the same for the newest March snapshot, checksum okay. Booting up will get end up with the following message at the end, right as the blue screen that says probing for devices appears. BARF 170 <105 panic: Going nowhere without my init! cpuid = 0 KDB: enter: panic [thread pid 1 tid 100007] Stopped at kdb_enter+0x2b: nop db> On booting safe mode, the error gets this far. pci0: at device 31.3 (no driver attached) panic: vm_fault: fault on nofault entry addr: c000b000 cpuid = 0 KDB: enter: panic [thread pid 0 tid 0] Stopped at kdb_enter+0x2b: nop Like I said, the machine runs fine on the February snapshot, but won't boot on March. It's an i686 Intel pentium D 915 processor, so dual core, 64 bit, in case that throws anything off.