From owner-freebsd-current@FreeBSD.ORG Tue Jun 15 23:19:20 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 4B3A216A4D0; Tue, 15 Jun 2004 23:19:20 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB0F843D54; Tue, 15 Jun 2004 23:19:19 +0000 (GMT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (sccrmhc12) with ESMTP id <20040615231910012002hokie>; Tue, 15 Jun 2004 23:19:11 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA50694; Tue, 15 Jun 2004 16:19:08 -0700 (PDT) Date: Tue, 15 Jun 2004 16:19:07 -0700 (PDT) From: Julian Elischer To: Lasse Laursen In-Reply-To: <01c301c45239$940781f0$6401a8c0@animal> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org 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: Tue, 15 Jun 2004 23:19:20 -0000 On Mon, 14 Jun 2004, Lasse Laursen wrote: > The server runs fine until a single thread/query suddenly locks up the > entire MySQL daemon. After that all queries are just queued and a restart of > the daemon is needed to unlock the system. The system itself is stable > enough as far as I can see. 'top' reports a lot of locks (*Giant) so I > assume that it's some weird problem with the threading? We used to use > FreeBSD on non-SMP machines without any problems. > > I have tried with linux threads as well but the same problem occurs. > > Have anyone experienced any similar problems and found a solution to this > rather weird problem? When this happens you need to examine the state of each thread. I have not seen teh result of a 'ps alxH' when this happens.. Also you should try 'ktrace' the process for a while when stopped as it might be retrying something , which may show up. julian