From owner-freebsd-questions@FreeBSD.ORG Tue Jan 29 14:35:25 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8178216A417 for ; Tue, 29 Jan 2008 14:35:25 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from snoogles.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 4499813C442 for ; Tue, 29 Jan 2008 14:35:25 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (localhost [127.0.0.1]) by snoogles.rachie.is-a-geek.net (Postfix) with ESMTP id 6CA301CC8B; Tue, 29 Jan 2008 05:19:37 -0900 (AKST) From: Mel To: freebsd-questions@freebsd.org Date: Tue, 29 Jan 2008 15:19:35 +0100 User-Agent: KMail/1.9.7 References: <715841970801290404x6555a9abn226018c0eb3c8182@mail.gmail.com> In-Reply-To: <715841970801290404x6555a9abn226018c0eb3c8182@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801291519.35919.fbsd.questions@rachie.is-a-geek.net> Cc: Drew Subject: Re: boot panic on 7.0RC1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2008 14:35:25 -0000 On Tuesday 29 January 2008 13:04:48 Drew wrote: > Hello, > I'm posting this in the hopes that someone can point me in the right > direction, and that it may possibly help someone else. The kernel panic > below is generated at boot, and is reproduceable as many times as you want > to do it. A few details on the hardware, the machine is a couple of years > old, but never displayed any real instability. My only suspect hardware is > the hard drive itself, and possibly ram, however seatools and memtest clear > them both with flying colors, for what that's worth. The machine is an > Athlon XP1900+, and I'm still running GENERIC (I usually compile something > custom after a machine has been up and going a while, but this was only > installed this past week) and the machine is under light load at best, > running natd, apache, mysql and postfix for my home network. One thing I > will point out is that the power went out yesterday on this machine, and > while the UPS's normally keep everything up, apparently the power was out > for more than 30 minutes because all of my machine's rebooted. When this > one came back up, it had hosed /var/log, but a good fsck cleared that up. > Later it quit working, and I got a brief look at a panic before it rebooted > - I know nothing about the first panic other than it was a kernel panic. > When it rebooted it came back to where it would mount / and stopped, with > the infamous mountroot> prompt. I politely advised it that it needed to > look ufs:ad1s1a and got the following panic - forgive any formating errors > on my part - I assure you the information I copied off the screen is > correct. > > Warning: / was not properly dismounted > > Fatal Trap 12: page fault while in kernel mode > cpuid = 0, apic id = 00 > fault virtual address = 0x188 > fault code = supervisor read, page not present > instruction pointer = 0x20 : 0xc0747d14 > stack pointer = 0x28 : 0xe3391aa0 > frame pointer = 0x28 : 0xe3391ab8 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor flags = interupt enabled, resume, IOPL = 0 > current process = 1 (swapper) > trap number = 12 > panic: page fault > cpuid = 0 > uptime: 42s > > All of this panic can be reproduced character for character (except the > uptime, unless you try real hard) time and time again. Any pointers on what > might be wrong here? Thanks in advance. Taking a wild guess, but looks like the filesystem is screwed, possibly (current process: swapper) the node that defines the start of the swap partition. To rule out any filesystem issues, try booting from cd-rom. If that works, mount ad1s1a from the rescue console (as /mnt for example). -- Mel