From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 16 15:45:58 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 E3B2116A481 for ; Fri, 16 Jun 2006 15:45:58 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6113043D48 for ; Fri, 16 Jun 2006 15:45:58 +0000 (GMT) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (localhost [127.0.0.1]) by bunrab.catwhisker.org (8.13.3/8.13.3) with ESMTP id k5GFjvqr042177; Fri, 16 Jun 2006 08:45:57 -0700 (PDT) (envelope-from david@bunrab.catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.13.3/8.13.1/Submit) id k5GFjvGS042176; Fri, 16 Jun 2006 08:45:57 -0700 (PDT) (envelope-from david) Date: Fri, 16 Jun 2006 08:45:56 -0700 From: David Wolfskill To: hackers@freebsd.org Message-ID: <20060616154556.GI32476@bunrab.catwhisker.org> References: <20060615232240.GX32476@bunrab.catwhisker.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+xfF7EeK4BVJ+jDf" Content-Disposition: inline In-Reply-To: <20060615232240.GX32476@bunrab.catwhisker.org> User-Agent: Mutt/1.4.2.1i Cc: 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:45:59 -0000 --+xfF7EeK4BVJ+jDf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 P= DT 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? Thanks! Peace, david --=20 David H. Wolfskill david@catwhisker.org Doing business with spammers only encourages them. Please boycott spammers. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --+xfF7EeK4BVJ+jDf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iEYEARECAAYFAkSSz9oACgkQmprOCmdXAD0aLwCeKRUNqF3eO8a0sHHnFDuUztCv CxsAnAk3F2Ki1mYYr6l8UjuVacMCdbhW =jUtT -----END PGP SIGNATURE----- --+xfF7EeK4BVJ+jDf--