From owner-freebsd-current@FreeBSD.ORG Thu Sep 2 03:16:22 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 D9BF816A4CE for ; Thu, 2 Sep 2004 03:16:22 +0000 (GMT) Received: from mx2.synetsystems.com (mx2.synetsystems.com [216.226.140.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0B2443D4C for ; Thu, 2 Sep 2004 03:16:22 +0000 (GMT) (envelope-from rmtodd@servalan.servalan.com) Received: by mx2.synetsystems.com (Postfix, from userid 66) id 0BAF31DB; Wed, 1 Sep 2004 23:16:22 -0400 (EDT) Received: from rmtodd by servalan.servalan.com with local (Exim 4.41 (FreeBSD)) id 1C2hEL-0003Hy-Jb; Wed, 01 Sep 2004 21:21:41 -0500 Date: Wed, 1 Sep 2004 21:21:41 -0500 From: Richard Todd To: Julian Elischer Message-ID: <20040902022141.GA12192@ichotolot.servalan.com> References: <20040820211618.62A1C7E4@mx2.synetsystems.com> <41341F94.6000803@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41341F94.6000803@elischer.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: Panic 'kernel trap doesn't have ucred' in last night's -current 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: Thu, 02 Sep 2004 03:16:23 -0000 On Mon, Aug 30, 2004 at 11:49:56PM -0700, Julian Elischer wrote: > Richard Todd wrote: > >In the freebsd-current mailing list I wrote last week: > > > >>Hi. Upgraded to -current last night and got the following panic. The > >>panic > >>seems to be fairly repeatable and is triggered by a minute or so's worth > >>of > >>database activity with mysqld. The version of mysql is 3.23.58_1 from > >>ports, [...] > I've been working on this and have some fixes on the way.. > > you might try tomorrow's -current as I just committed a possibly relevent > change. I've upgraded to current as of last night, and ran the test I mentioned in my original mail 20 times without causing a panic; I've now been up for a couple hours in "normal" operation with mysqld using libpthread busily handling requests from the various amavisd/spamassasin copies running without triggering a panic (which it did repeatedly before.) Looks like the bug's fixed. Thanks.