From owner-freebsd-bugs@FreeBSD.ORG Tue Apr 24 21:58:23 2007 Return-Path: X-Original-To: freebsd-bugs@FreeBSD.org Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6457816A401 for ; Tue, 24 Apr 2007 21:58:23 +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 471CF13C469 for ; Tue, 24 Apr 2007 21:58:23 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id E73A81A4DD6; Tue, 24 Apr 2007 14:58:46 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 4622C5139A; Tue, 24 Apr 2007 17:58:22 -0400 (EDT) Date: Tue, 24 Apr 2007 17:58:22 -0400 From: Kris Kennaway To: Remco Bressers Message-ID: <20070424215822.GA40483@xor.obsecurity.org> References: <200704242110.l3OLA93u057070@freefall.freebsd.org> <20070424211426.GA39603@xor.obsecurity.org> <1177449699.5638.25.camel@localhost> <20070424212637.GA39829@xor.obsecurity.org> <1177450685.5638.29.camel@localhost> <20070424214220.GA40150@xor.obsecurity.org> <1177451257.5638.31.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1177451257.5638.31.camel@localhost> User-Agent: Mutt/1.4.2.2i Cc: freebsd-bugs@FreeBSD.org, pvdsteen@signet.nl, "Michael R. Wayne" , Kris Kennaway Subject: Re: kern/111458: [panic] Panic on 6.2-RELEASE AMD in kern_mutex X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Apr 2007 21:58:23 -0000 On Tue, Apr 24, 2007 at 11:47:37PM +0200, Remco Bressers wrote: > On Tue, 2007-04-24 at 17:42 -0400, Kris Kennaway wrote: > > On Tue, Apr 24, 2007 at 11:38:05PM +0200, Remco Bressers wrote: > > > On Tue, 2007-04-24 at 17:26 -0400, Kris Kennaway wrote: > > > > On Tue, Apr 24, 2007 at 11:21:39PM +0200, Remco Bressers wrote: > > > > > On Tue, 2007-04-24 at 17:14 -0400, Kris Kennaway wrote: > > > > > > On Tue, Apr 24, 2007 at 09:10:09PM +0000, Remco Bressers wrote: > > > > > > > > > > > > > To update this bugreport and to keep it 'warm' > > > > > > > > > > > > > > I've got the very same problem overhere. > > > > > > > > > > > > > > Our box : > > > > > > > > > > > > > > # uname -r > > > > > > > 6.2-RELEASE-p2 > > > > > > > > > > > > > > This is an amd64 release > > > > > > > > > > > > > > Updates on GENERIC : > > > > > > > > > > > > > > options QUOTA > > > > > > > device pf > > > > > > > device pflog > > > > > > > options SMP > > > > > > > > > > > > > > Kernel messages : > > > > > > > > > > > > > > cpuid = 0; apic id = 00 > > > > > > > fault virtual address = 0x18c > > > > > > > fault code = supervisor read, page not present > > > > > > > current process = 5 (thread taskq) > > > > > > > trap number = 12 > > > > > > > panic: page fault > > > > > > > cpuid = 0 > > > > > > > > > > > > How do you know it is "the very same problem"? In order to determine > > > > > > this you need to compare backtraces from the panic, which you didn't > > > > > > provide. > > > > > > > > > > I contacted the submitter for this problem and compared hardware and > > > > > software. The symptoms are the same > > > > > > > > Which just means "it crashed" > > > > > > > > , the kernel panic is the same and > > > > > > > > The panic message also just means "it crashed" > > > > > > > > > the installed FreeBSD version is exactly the same. > > > > > > > > You're both running the most recent version, no real surprises there. > > > > > > > > > Sounds fair enough to me. Ofcourse i cannot be 100% sure, but it > > > > > sounds too obvious to me. > > > > > > > > Well, maybe, but I respectfully submit that you don't understand the > > > > issue well enough to conclude that :) Please follow up with a > > > > backtrace and then we'll see where things stand. > > > > > > You didn't write anything about the fact that software combinations + > > > hardware is almost identical! That's no coincidence in my humble > > > opinion :). Anyway.. > > > > I'd prefer not to prematurely jump to conclusions before you have any > > supporting evidence. It is of course an obviously true statement that > > two identical systems may panic in two completely different and > > unrelated ways. > > > > > The problem in this case is, that the backtrace isn't written to disk. I > > > must wait for the next opportunity to get that backtrace. > > > > OK, let us know. > > Is it right that i have to configure the dump device with 'dumpdev' in > rc.conf ? I'm a little lost here :S See the developers handbook chapter on kernel debugging. Kris