From owner-freebsd-questions@FreeBSD.ORG Mon Jun 14 10:08:39 2010 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 633C3106566C for ; Mon, 14 Jun 2010 10:08:39 +0000 (UTC) (envelope-from matthew.hambley@manchester.ac.uk) Received: from tranquility.mcc.ac.uk (tranquility.mcc.ac.uk [130.88.200.145]) by mx1.freebsd.org (Postfix) with ESMTP id 2597B8FC17 for ; Mon, 14 Jun 2010 10:08:38 +0000 (UTC) Received: from kelvin.its.manchester.ac.uk ([130.88.25.195]) by tranquility.mcc.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1OO6KI-0009Hv-Lg for freebsd-questions@freebsd.org; Mon, 14 Jun 2010 10:51:30 +0100 Received: from [130.88.9.82] (port=48182) by kelvin.its.manchester.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1OO6KI-0001Fa-Go for freebsd-questions@freebsd.org; Mon, 14 Jun 2010 10:51:30 +0100 Message-ID: <4C15FB9F.5040602@manchester.ac.uk> Date: Mon, 14 Jun 2010 10:51:27 +0100 From: Matthew Hambley User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100515 Lightning/1.0b1 Icedove/3.0.4 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-Sender: Matthew Hambley from ([130.88.9.82]) [130.88.9.82]:48182 X-Authenticated-From: Matthew.Hambley@manchester.ac.uk X-Spam-Score: -5.0 (?) X-Spam-Flag: NO Subject: Sudden refusal to boot with page fault in swapper 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: Mon, 14 Jun 2010 10:08:39 -0000 My FreeBSD system (amd64, SATA, root on ZFS) has suddenly started refusing to boot up. It crashes out with a page fault just after the ZFS warning that I "only" have 4GB of RAM. The following is a transcription of what I see: > ZFS file system version 13 > ZFS storage pool version 13 > Timecounters tick every 1.000msec > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x4 > fault code = supervisor write data, page not present > instruction pointer = 0x20:0xf...810c522a > stack pointer = 0x28:0xf...81128af0 > frame pointer = 0x28:0xf...81128b10 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interupt enabled, resume, IOPL = 0 > current process = 0 (swapper) > trap number = 12 > panic: page fault > cupid = 0 > uptime : 1s > Cannot dump, Device not defined or unavailable > Automatic reboot in 15 seconds The ellipses in addresses represents continued f's. These addresses seem to be the same each time. I have tried using the "Without ACPI" boot option to no avail. Originally I had a problem in that using a USB keyboard meant I was unable to press a key to halt the reboot timer but a USB to PS/2 adapter solved that. This problem has suspiciously started happening after I had trouble performing the big "gettext" upgrade to the ports tree but I don't see how changes to the ports tree can affect the base system which is presumably where I still am this early in the boot process. However, for completeness, the "portmaster -w -r gettext" command kept failing half way through over the "xz" archiver. In the end I gave up and went with a "portmaster -a" expecting some minor problems which could be fixed with manual recompilation of effected ports. While some web searching didn't turn up an answer to my problem it did show that a memory fault is often suspected in these situations. I used an "Ultimate Boot" disc to test the memory and it tested okay. Have I hosed my system? And help gratefully received. -- (\/)atthew