From owner-freebsd-current@FreeBSD.ORG Wed Jun 16 05:45:30 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 0045C16A4CE; Wed, 16 Jun 2004 05:45:30 +0000 (GMT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BC7C43D48; Wed, 16 Jun 2004 05:45:29 +0000 (GMT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i5G5jNqb011596; Wed, 16 Jun 2004 01:45:23 -0400 (EDT) Date: Wed, 16 Jun 2004 01:45:23 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Daryl Chance In-Reply-To: <20040616051052.98903.qmail@web53708.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: julian@elischer.org cc: mike@mike2k.com cc: freebsd-threads@freebsd.org Subject: RE: Possible Threading problem with -CURRENT / MySQL? 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: Wed, 16 Jun 2004 05:45:30 -0000 On Tue, 15 Jun 2004, Daryl Chance wrote: > Sorry for the top post. > > We've had this same problem (with mysqld locking up). > I was able to get a trace, but since it's a live sql > box, I didn't have time to find your email (If I knew > I had kept a copy in my inbox, I would have done this > correctly, instead I thought I had to look up the > email in the archives) but I was able to get a ktrace > -p pid output of the process. I let it run about 10 > seconds and then killall -11 mysqld'd the process (it > allows mysqld to shutdown gracefully, thus not > corrupting our tables). > > Here is the link to the .out file > http://sql.tribalwar.com/ktrace.out > > here is the link to the .txt file of the kdump output > http://sql.tribalwar.com/kdump.txt > > That was all I could remember to do in the short time > I had to get it back up and running :). > > It's a stock kernel (w/ some minor things commented > out). It's FBSD 5.2.1 p6 > http://sql.tribalwar.com/SQL I don't think 5.2.1 is going to tell us much. We know there was a problem in 5.2-release. We really need -current. -- Dan Eischen