From owner-freebsd-current@FreeBSD.ORG Tue Oct 28 15:12:13 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECA8716A4CE for ; Tue, 28 Oct 2003 15:12:13 -0800 (PST) Received: from mail.speakeasy.net (mail9.speakeasy.net [216.254.0.209]) by mx1.FreeBSD.org (Postfix) with ESMTP id F37DB43F85 for ; Tue, 28 Oct 2003 15:12:12 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 796 invoked from network); 28 Oct 2003 23:12:12 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 28 Oct 2003 23:12:12 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.9/8.12.9) with ESMTP id h9SNC7ce029056; Tue, 28 Oct 2003 18:12:08 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20031028224604.GA2284@dan.emsphone.com> Date: Tue, 28 Oct 2003 18:12:07 -0500 (EST) From: John Baldwin To: Dan Nelson X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: current@freebsd.org Subject: RE: page fault in propagate_priority X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2003 23:12:14 -0000 On 28-Oct-2003 Dan Nelson wrote: > > I've gotten the following panic twice in the last few days. I'm pretty > sure truss has something to do with it, since I just started trussing > something when it paniced. No crashdumps unfortunately, and the system > locks up hard so I have to reset it. > > The fault address is 0x24 so it looks like a null pointer dereference > of some sort. I've added asserts to propagate_priority any place a > pointer to a structure is dereferenced, so if it happens again I should > have the line number at least. > > panic1 was on an Oct 15 kernel, panic2 was on an Oct 27 kernel. It might help some if you could use gdb -k on your kernel.debug and do 'l *propagate_priority+0x66' to see where it is dying. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/