Date: Wed, 16 Jun 2004 01:45:23 -0400 (EDT) From: Daniel Eischen <eischen@vigrid.com> To: Daryl Chance <chancedj@yahoo.com> Cc: freebsd-threads@freebsd.org Subject: RE: Possible Threading problem with -CURRENT / MySQL? Message-ID: <Pine.GSO.4.10.10406160142460.10906-100000@pcnet5.pcnet.com> In-Reply-To: <20040616051052.98903.qmail@web53708.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10406160142460.10906-100000>