From owner-freebsd-current@FreeBSD.ORG Tue Aug 31 06:49:59 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 F1D6716A4CE; Tue, 31 Aug 2004 06:49:59 +0000 (GMT) Received: from pimout2-ext.prodigy.net (pimout2-ext.prodigy.net [207.115.63.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D16043D53; Tue, 31 Aug 2004 06:49:59 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (adsl-69-104-103-54.dsl.snfc21.pacbell.net [69.104.103.54])i7V6nvK6205234; Tue, 31 Aug 2004 02:49:58 -0400 Message-ID: <41341F94.6000803@elischer.org> Date: Mon, 30 Aug 2004 23:49:56 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030524 X-Accept-Language: en, hu MIME-Version: 1.0 To: Richard Todd References: <20040820211618.62A1C7E4@mx2.synetsystems.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: David Xu 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: Tue, 31 Aug 2004 06:50:00 -0000 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, >>linked against libpthread; using libmap.conf to force usage of libc_r avoids >>the panic, so it's definitely a thread/KSE issue. (Also note the oddness >>of the backtrace in the frames between doreti_ast and sched_switch -- is this >>normal, is the stack mangled, or is gdb just hallucinating?) My kernel config > 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.