From owner-freebsd-threads@FreeBSD.ORG Wed Feb 16 23:06:46 2005 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 254EE16A4CE for ; Wed, 16 Feb 2005 23:06:46 +0000 (GMT) Received: from mail.trippynames.com (mail.trippynames.com [38.113.223.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id F226B43D41 for ; Wed, 16 Feb 2005 23:06:45 +0000 (GMT) (envelope-from sean@chittenden.org) Received: from localhost (localhost [127.0.0.1]) by mail.trippynames.com (Postfix) with ESMTP id B5041CC6DA; Wed, 16 Feb 2005 15:06:45 -0800 (PST) Received: from mail.trippynames.com ([127.0.0.1]) by localhost (rand.nxad.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 23307-05; Wed, 16 Feb 2005 15:06:44 -0800 (PST) Received: from [192.168.102.100] (c-67-168-93-230.client.comcast.net [67.168.93.230]) by mail.trippynames.com (Postfix) with ESMTP id 5BA50B47CA; Wed, 16 Feb 2005 15:06:44 -0800 (PST) In-Reply-To: <20050211001252.GY1060@sean.gigave.com> References: <20050211001252.GY1060@sean.gigave.com> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Sean Chittenden Date: Wed, 16 Feb 2005 15:06:43 -0800 To: Sean Chittenden X-Mailer: Apple Mail (2.619.2) cc: threads@FreeBSD.org Subject: Re: Strange backtrace from amd64 + mysqld... X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 23:06:46 -0000 > Howdy. I'm running into a strange issue with MySQL 4.1.9 wherein its > eating itself every 24hrs. I grabbed a back trace, but haven't > recompiled MySQL with debugging given the strangeness of the backtrace > (can't tell if this is gdb or if the call stack is massively corrupt > due to some error). Given I've watched this repeat itself a few times > now and it seems to be dying in a pthread call, I'm posting here. > MySQL is the only process having problems, but it's also the most > heavily threaded and is getting pounded pretty hard. Without going > back to MySQL (esp given the backtrace), I want to verify that this > isn't a pthreads issue. Can someone comment on whether or not they've > seen this before? Out of desperation, I recompiled MySQL with system scoped threads instead of process scoped threads and MySQL has been running as well as MySQL runs. Seems as though there's some locking issue that gets exposed with process scoped threads vs. system scoped threads. Regardless, for those dropping in, MySQL should be used with system scoped threads if you're experiencing any abnormal MySQL instability (I'm also not sure if this is an amd64 specific issue or not). -sc -- Sean Chittenden