From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 16 15:59:24 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 169F616A47A for ; Fri, 16 Jun 2006 15:59:24 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48E5E43D46 for ; Fri, 16 Jun 2006 15:59:16 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost.int.ru [127.0.0.1] (may be forged)) by mp2.macomnet.net (8.13.7/8.13.3) with ESMTP id k5GFw5LJ094493; Fri, 16 Jun 2006 19:58:05 +0400 (MSD) (envelope-from maxim@macomnet.ru) Date: Fri, 16 Jun 2006 19:58:05 +0400 (MSD) From: Maxim Konovalov To: David Wolfskill In-Reply-To: <20060616154556.GI32476@bunrab.catwhisker.org> Message-ID: <20060616195410.L23922@mp2.macomnet.net> References: <20060615232240.GX32476@bunrab.catwhisker.org> <20060616154556.GI32476@bunrab.catwhisker.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: hackers@freebsd.org Subject: Re: Help? 6.1-S: Fatal trap 12: page fault while in kernel mode X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jun 2006 15:59:24 -0000 On Fri, 16 Jun 2006, 08:45-0700, David Wolfskill wrote: > On Thu, Jun 15, 2006 at 04:22:40PM -0700, David Wolfskill wrote: > > I had one of these [kernel panics] a couple of weeks ago or so... > > ...[upgrade to -STABLE as of 15 June; repeat panic]... > > The message to which I'm replying (posted to -stable) has the > particulars about the panic in question, and the machine in question is > still sitting at the DDB prompt, if anyone wishes to work with me on > that. > > But the reason for this message is to report that I upgraded the other > test machines -- identical confguration: 2x3 GHz Xeons w/ 4 GB RAM; > kernel config is called "SMP_PAE_DDB" for a fairly good reason -- to > today's -CURRENT, then started the same test that cause -STABLE to crash > & burn within a couple of minutes. > > That was 30 minutes ago; the test is still running on > > FreeBSD localhost 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Fri Jun 16 07:28:18 PDT 2006 dhw@localhost:/usr/obj/usr/src/sys/SMP_PAE_DDB i386 > > As I commented in email to some colleagues, "color me surprised." > > I've suggested to the vendor (the program under test on the box is > from a vendor, built under & for FreeBSD 5.x; I'm using the > misc/compat5x port) that they consider trying this themselves, and > perhaps also take advantage of John Birrell's work to date on the > FreeBSD port of DTrace. > > I'm still not too keen to run a production workload on a -CURRENT > platform. I don't know if whatever is causing -CURRENT to keep running > while -STABLE dies is an MFC candidate, but it seems to me that > identifying the salient change(s) would be helpful in figuring that out. > > Any suggestions for how to go about doing that? "trace" in ddb would be good start. Do you really need PAE? -- Maxim Konovalov