Date: Tue, 17 Oct 2006 09:59:46 -0500 From: Brooks Davis <brooks@one-eyed-alien.net> To: Norberto Meijome <freebsd@meijome.net> Cc: freebsd-stable@freebsd.org Subject: Re: kernel panic mounting /tmp - 6.2-PRERELEASE Message-ID: <20061017145946.GB68977@lor.one-eyed-alien.net> In-Reply-To: <20061018002558.3a2bcdf6@localhost> References: <20061018002558.3a2bcdf6@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
--CUfgB8w4ZwR/yMy5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 18, 2006 at 12:25:58AM +1000, Norberto Meijome wrote: > Hi everyone, >=20 > tonight when I started my laptop, i was welcomed with a very nice panic, = which > was happening JUST when mounting the filesystems.=20 >=20 > Some info: > Fault code : supervisor read, page not present. > current process : 112 (mount) > trap 12 > panic :page fault >=20 > with nm -m I saw that the following procs where candidates ... >=20 > ufsdirhash_build > ufsdirhas_free > ufsdirhash_lookup >=20 > Booting with 6.1 Release CD and mounting showed no obvious problems at al= l, but > the panic could be reproduced every time with this particular kernel (6 d= ays > old). Commenting out /tmp in fstab worked around the problem. >=20 > recreating the filesystem in /dev/ad0s1e (my /tmp) solved the problem and= now > everything is back to normal. The computer works great as usual. >=20 > $ 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 >=20 > I have a good kernel dump , a copy of /boot/kernel that was being used, a= nd a > dump (dump -0 -a -f usr/ad0s1e.dump /dev/ad0s1e ) of the /tmp partition a= t the > time (before the newfs, of course). Available for anyone interested. >=20 > Is there a bigger issue here? anything I can do to help diagnose / debug = this? Possibly and no. By recreating the file system you've destroyed the information needed to isolate the cause. It's known that an appropriately corrupt file system can do this, but the causes (there are probably several) are not yet known. There is some speculation that the only solution is to add checksums to all key data sections. -- Brooks --CUfgB8w4ZwR/yMy5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFNO/hXY6L6fI4GtQRAiYOAJoD/1aFj4F5i/QtCRm+zlD216aaiwCcDQcw rEag0jVYKZe3k8x81kcUnE0= =+MzE -----END PGP SIGNATURE----- --CUfgB8w4ZwR/yMy5--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061017145946.GB68977>