From owner-freebsd-bugs@FreeBSD.ORG Tue Apr 24 21:14:28 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 5D2B016A403 for ; Tue, 24 Apr 2007 21:14:28 +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 4C6EF13C43E for ; Tue, 24 Apr 2007 21:14:28 +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 1F4661A4DD5; Tue, 24 Apr 2007 14:14:52 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8B8FB5139A; Tue, 24 Apr 2007 17:14:27 -0400 (EDT) Date: Tue, 24 Apr 2007 17:14:27 -0400 From: Kris Kennaway To: Remco Bressers Message-ID: <20070424211426.GA39603@xor.obsecurity.org> References: <200704242110.l3OLA93u057070@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200704242110.l3OLA93u057070@freefall.freebsd.org> User-Agent: Mutt/1.4.2.2i Cc: freebsd-bugs@FreeBSD.org 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:14:28 -0000 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. Kris