From owner-freebsd-current@FreeBSD.ORG Mon Jun 28 21:01:28 2004 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 C7B2716A503 for ; Mon, 28 Jun 2004 21:01:28 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C61C43D39 for ; Mon, 28 Jun 2004 21:01:26 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 28593 invoked from network); 28 Jun 2004 21:01:25 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 28 Jun 2004 21:01:25 -0000 Received: from 131.106.58.153 (p58.n-nypop02.stsn.com [199.106.89.58]) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i5SL18E7004987; Mon, 28 Jun 2004 17:01:13 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Mon, 28 Jun 2004 17:02:19 -0400 User-Agent: KMail/1.6 References: <20040628202944.GB73213@atrbg11.informatik.tu-muenchen.de> In-Reply-To: <20040628202944.GB73213@atrbg11.informatik.tu-muenchen.de> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406281702.19726.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Daniel Lang Subject: Re: Please help, panic with current, kern/68442 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: Mon, 28 Jun 2004 21:01:28 -0000 On Monday 28 June 2004 04:29 pm, Daniel Lang wrote: > Hi, > > I filed and updated PR kern/68442 today. I am sort of desperate, since > this is a production machine (a FreeBSD.org mirror among other > services). I know that -current is not yet production quality, but > > a) it behaved very well in the past and > b) it is encouraged to track down problems which tend to appear > only on real-world loaded systems. > > So I hope someone will take a look at the PR, which includes some > ddb stack trace at least and maybe comes up with a solution. > I did not have been able to generate a core image for gdb > debugging, yet. Usually the machine just hangs, even with the > panic-message I don't get a ddb prompt, dump or even reboot. > In most cases I need to hit the reset button. :( Do you have a date from a kernel that worked ok? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org