From owner-freebsd-current@FreeBSD.ORG Tue Aug 7 19:15:15 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50B4A16A41B for ; Tue, 7 Aug 2007 19:15:15 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 48F8B13C46E for ; Tue, 7 Aug 2007 19:15:15 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from rot26.obsecurity.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id C44451A4D86; Tue, 7 Aug 2007 12:14:21 -0700 (PDT) Received: by rot26.obsecurity.org (Postfix, from userid 1001) id 23EE6C23A; Tue, 7 Aug 2007 15:15:14 -0400 (EDT) Date: Tue, 7 Aug 2007 15:15:13 -0400 From: Kris Kennaway To: "A. Rios" Message-ID: <20070807191513.GA57253@rot26.obsecurity.org> References: <5d95d4be0708050332r5b00c5b7h73acb3ae8b94383c@mail.gmail.com> <5d95d4be0708071211q5ede78b3q93d1cc0b21578810@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5d95d4be0708071211q5ede78b3q93d1cc0b21578810@mail.gmail.com> User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org Subject: Re: panic and fs corruption in -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Aug 2007 19:15:15 -0000 On Tue, Aug 07, 2007 at 09:11:46PM +0200, A. Rios wrote: > On 8/5/07, A. Rios 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