From owner-freebsd-current@FreeBSD.ORG  Fri Apr  2 19:48:37 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 5BF4916A4CE
	for <current@freebsd.org>; Fri,  2 Apr 2004 19:48:37 -0800 (PST)
Received: from web9601.mail.yahoo.com (web9601.mail.yahoo.com
	[216.136.129.180])
	by mx1.FreeBSD.org (Postfix) with SMTP id 2918243D1D
	for <current@freebsd.org>; Fri,  2 Apr 2004 19:48:37 -0800 (PST)
	(envelope-from chancedj@yahoo.com)
Message-ID: <20040403034837.80399.qmail@web9601.mail.yahoo.com>
Received: from [24.170.136.111] by web9601.mail.yahoo.com via HTTP;
	Fri, 02 Apr 2004 19:48:37 PST
Date: Fri, 2 Apr 2004 19:48:37 -0800 (PST)
From: Daryl Chance <chancedj@yahoo.com>
To: Doug White <dwhite@gumbysoft.com>
In-Reply-To: <20040402190329.G46609@carver.gumbysoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: current@freebsd.org
Subject: Re: FBSD 5.2.1-p4 and mysqld problems
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Apr 2004 03:48:37 -0000

ah! thanks :)

It just happened again and I was able to collect the
data again.

Before I did mysqladmin shutdown/killall -11 mysqld
http://sql.tribalwar.com/before-ps.txt

a few times the 3 giant processes would show as -, but
then it got to the point where they weren't changing
one bit (staying at Giant)

after I did mysqladmin shutdown/killall -11 mysqld
http://sql.tribalwar.com/after-ps.txt

this eventually cleared up after a minute or so.

I've given some serious thought to upgrading to
-CURRENT, but with the network stack commit comming
soon (or happening now), I don't want to get caught in
the middle of it and have severe problems. Perhaps I
should use a tag for the time right around the sysctl
change for the mp stack?

The guy running the site just wants me to (have
someone at the colo) format the machine and go back to
4.9.

Oh, I now have witness in the kernel...no deadlocks
from what I've seen.

HTH,
Daryl

--- Doug White <dwhite@gumbysoft.com> wrote:
> On Fri, 2 Apr 2004, Daryl Chance wrote:
> 
> > Thanks for your response.  It just happened a few
> > minutes ago and i was able to capture all the
> output
> > into a text file.
> >
> > http://sql.tribalwar.com/ps.txt
> 
> oops, sorry, I get those confused. You want 'ps
> axlwww'.  WCHAN will be a
> string like "select".
> 
> > I have WITNESS* options compiled into the kernel
> and
> > am going to reboot soon.  Do you think it would
> help
> > in debugging this to see if there are any
> deadlocks?
> 
> Potentially, although I get 100% cpu loops with kde
> that won't trigger any
> witness or invariants checks.
> 
> -- 
> Doug White                    |  FreeBSD: The Power
> to Serve
> dwhite@gumbysoft.com          |  www.FreeBSD.org


__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway 
http://promotions.yahoo.com/design_giveaway/