From owner-freebsd-stable@FreeBSD.ORG Fri Mar 6 10:21:01 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F599106564A for ; Fri, 6 Mar 2009 10:21:01 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from buffy.york.ac.uk (buffy.york.ac.uk [144.32.226.160]) by mx1.freebsd.org (Postfix) with ESMTP id 1C62A8FC23 for ; Fri, 6 Mar 2009 10:21:00 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.3/8.14.3) with ESMTP id n26AKwMn030113; Fri, 6 Mar 2009 10:20:58 GMT (envelope-from gavin@FreeBSD.org) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.3/8.14.3/Submit) id n26AKwVl030112; Fri, 6 Mar 2009 10:20:58 GMT (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson To: Boris Kochergin In-Reply-To: <49B07482.4080208@acm.poly.edu> References: <49B07482.4080208@acm.poly.edu> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Fri, 06 Mar 2009 10:20:57 +0000 Message-Id: <1236334857.88789.4.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port Cc: freebsd-stable@FreeBSD.org Subject: Re: "Fatal trap 12: page fault while in kernel mode" on 7.1/amd64, but not 7.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Mar 2009 10:21:01 -0000 On Thu, 2009-03-05 at 19:55 -0500, Boris Kochergin wrote: > Ahoy. I recently upgraded an amd64 machine to 7.1-RELEASE, and started > getting a bunch of these at a pretty high frequency (a few hours to a > day apart): > > http://acm.poly.edu/~spawk/IMG00033.jpg > > The "current process" is always httpd. They're particularly annoying > because the machine doesn't actually ever reboot, requiring manual > intervention. Reverting the kernel back to 7.0 makes the panic go away, > and the machine had been happily running 7.0 for about a year > beforehand. I realize that the photo hardly contains any useful > debugging information, but I was hoping it might look familiar to > someone. If not, I guess I'll come back with a backtrace. A backtrace will almost certainly be necessary to figure out what this issue is, although there is a possibility that the output of "addr2line -e /boot/kernel/kernel.symbols 0x8:0xffffffff802d7010" might help, assuming you've not recompiled your kernel yet. (That number should be the same as the "instruction pointer" shown by the panic, but as the photo is quite blurred there's a chance I've got it wrong, if you have a better picture of it or wrote it down then use that) Gavin