From owner-freebsd-stable@FreeBSD.ORG Tue Oct 17 14:26:10 2006 Return-Path: X-Original-To: freebsd-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 6A9B416A412 for ; Tue, 17 Oct 2006 14:26:10 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: from sigma.octantis.com.au (ns2.octantis.com.au [207.44.189.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id C526243D5A for ; Tue, 17 Oct 2006 14:26:05 +0000 (GMT) (envelope-from freebsd@meijome.net) Received: (qmail 31209 invoked from network); 18 Oct 2006 00:26:04 +1000 Received: from 124-168-3-158.dyn.iinet.net.au (HELO localhost) (124.168.3.158) by sigma.octantis.com.au with (DHE-RSA-AES256-SHA encrypted) SMTP; 18 Oct 2006 00:26:04 +1000 Date: Wed, 18 Oct 2006 00:25:58 +1000 From: Norberto Meijome To: freebsd-stable@freebsd.org Message-ID: <20061018002558.3a2bcdf6@localhost> X-Mailer: Sylpheed-Claws 2.5.2 (GTK+ 2.10.6; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: kernel panic mounting /tmp - 6.2-PRERELEASE 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: Tue, 17 Oct 2006 14:26:10 -0000 Hi everyone, tonight when I started my laptop, i was welcomed with a very nice panic, which was happening JUST when mounting the filesystems. Some info: Fault code : supervisor read, page not present. current process : 112 (mount) trap 12 panic :page fault with nm -m I saw that the following procs where candidates ... ufsdirhash_build ufsdirhas_free ufsdirhash_lookup Booting with 6.1 Release CD and mounting showed no obvious problems at all, but the panic could be reproduced every time with this particular kernel (6 days old). Commenting out /tmp in fstab worked around the problem. recreating the filesystem in /dev/ad0s1e (my /tmp) solved the problem and now everything is back to normal. The computer works great as usual. $ uname -a FreeBSD ayiin.xxx 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #14: Wed Oct 11 14:13:49 EST 2006 root@ayiin.xxx:/usr/obj/usr/src/sys/AYIIN i386 I have a good kernel dump , a copy of /boot/kernel that was being used, and a dump (dump -0 -a -f usr/ad0s1e.dump /dev/ad0s1e ) of the /tmp partition at the time (before the newfs, of course). Available for anyone interested. Is there a bigger issue here? anything I can do to help diagnose / debug this? TIA! B _________________________ {Beto|Norberto|Numard} Meijome "Lots of people who complained about us receiving the MBE received theirs for heroism in the war -- for killing people. We received ours for entertaining other people. I'd say we deserve ours more." John Lennon I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned.