From owner-freebsd-threads@FreeBSD.ORG Tue Nov 24 15:50:03 2009 Return-Path: Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F90D1065698 for ; Tue, 24 Nov 2009 15:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6DB2F8FC1E for ; Tue, 24 Nov 2009 15:50:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nAOFo3jf032897 for ; Tue, 24 Nov 2009 15:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nAOFo3WM032896; Tue, 24 Nov 2009 15:50:03 GMT (envelope-from gnats) Date: Tue, 24 Nov 2009 15:50:03 GMT Message-Id: <200911241550.nAOFo3WM032896@freefall.freebsd.org> To: freebsd-threads@FreeBSD.org From: Conor McDermottroe Cc: Subject: Re: threads/135673: databases/mysql50-server - MySQL query lock-ups on 7.2-RELEASE amd64 X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Conor McDermottroe List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Nov 2009 15:50:03 -0000 The following reply was made to PR threads/135673; it has been noted by GNATS. From: Conor McDermottroe To: bug-followup@FreeBSD.org, freebsd-bugs@desert.net Cc: Subject: Re: threads/135673: databases/mysql50-server - MySQL query lock-ups on 7.2-RELEASE amd64 Date: Tue, 24 Nov 2009 15:19:38 +0000 Thanks very much for the patch, we were running into it as well. The good news is that it improves the situation quite a bit. The bad news is that it does not appear to cure the problem entirely. Under heavy load we see the same problem re-occurring. We'll be bringing up another machine with 8.0 in the coming weeks and I hope to test it then. We're currently avoiding this bug by under-loading the 7.2 machine and handling more queries on a different 7.0 machine. Is there any information I can provide which would help diagnose this bug further?