Date: Tue, 7 Aug 2007 15:15:13 -0400 From: Kris Kennaway <kris@obsecurity.org> To: "A. Rios" <cosasvarias@gmail.com> Cc: current@freebsd.org Subject: Re: panic and fs corruption in -current Message-ID: <20070807191513.GA57253@rot26.obsecurity.org> In-Reply-To: <5d95d4be0708071211q5ede78b3q93d1cc0b21578810@mail.gmail.com> References: <5d95d4be0708050332r5b00c5b7h73acb3ae8b94383c@mail.gmail.com> <5d95d4be0708071211q5ede78b3q93d1cc0b21578810@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 07, 2007 at 09:11:46PM +0200, A. Rios wrote: > On 8/5/07, A. Rios <cosasvarias@gmail.com> wrote: > > > > I compiled yesterday's kernel without problems, and it restarted fine. I > > applied jeff roberson's ulehtt.diff (P4 with hyperthreading and 2GB RAM > > here) > > and disabled all kernel debugging (I was testing performance) > > > > Earlier this morning I was portupgrading and everything start to fail. One > > of the > > (random) panics was: > > > > > Ok, now I have a kernel with debug symbols and I've found a way to reproduce > the panic. It occurs when installing a port and after the message "SHA256 > checksum OK for port XXXXX", at this point the system freezes and sometimes > it dumps the memory and reboot itself, and other times it simply freezes and > I have to restart the computer. I think the problem came from somewhere of > the gcc/make toolchain but I don't know where to start. I would guess that your filesystem remains corrupted from a previous panic and you need to offline and fsck -f it. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070807191513.GA57253>