From owner-freebsd-current@FreeBSD.ORG Wed Jun 16 05:49:57 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 9DBFE16A4CF for ; Wed, 16 Jun 2004 05:49:57 +0000 (GMT) Received: from web53702.mail.yahoo.com (web53702.mail.yahoo.com [206.190.37.23]) by mx1.FreeBSD.org (Postfix) with SMTP id 2A72043D41 for ; Wed, 16 Jun 2004 05:49:53 +0000 (GMT) (envelope-from chancedj@yahoo.com) Message-ID: <20040616054951.37343.qmail@web53702.mail.yahoo.com> Received: from [24.170.135.170] by web53702.mail.yahoo.com via HTTP; Tue, 15 Jun 2004 22:49:51 PDT Date: Tue, 15 Jun 2004 22:49:51 -0700 (PDT) From: Daryl Chance To: freebsd-current@freebsd.org, freebsd-threads@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: RE: Possible Threading problem with -CURRENT / MySQL? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: chancedj@yahoo.com 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:49:57 -0000 We're actually upgrading tomorrow night to -CURRENT, if it continues, I will let you guys know. :). -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Daniel Eischen Sent: Wednesday, June 16, 2004 1:45 AM To: Daryl Chance Cc: freebsd-current@freebsd.org; julian@elischer.org; mike@mike2k.com; freebsd-threads@freebsd.org Subject: RE: Possible Threading problem with -CURRENT / MySQL? 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 _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com