From owner-freebsd-current@FreeBSD.ORG Sat Aug 14 00:49:38 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 DC59916A4CE for ; Sat, 14 Aug 2004 00:49:38 +0000 (GMT) Received: from mail.parodius.com (mail.parodius.com [64.62.145.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9747543D46 for ; Sat, 14 Aug 2004 00:49:38 +0000 (GMT) (envelope-from jdc@pentarou.parodius.com) Received: from pentarou.parodius.com (jdc@localhost [127.0.0.1]) by mail.parodius.com (8.12.11/8.12.11) with ESMTP id i7E0ncOB027096 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 13 Aug 2004 17:49:38 -0700 (PDT) (envelope-from jdc@pentarou.parodius.com) Received: (from jdc@localhost) by pentarou.parodius.com (8.12.11/8.12.11/Submit) id i7E0ncFo027095 for freebsd-current@freebsd.org; Fri, 13 Aug 2004 17:49:38 -0700 (PDT) (envelope-from jdc) Date: Fri, 13 Aug 2004 17:49:38 -0700 From: Jeremy Chadwick To: freebsd-current@freebsd.org Message-ID: <20040814004938.GA26808@parodius.com> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: MySQL on -current (possible gcc issue?) 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: Sat, 14 Aug 2004 00:49:39 -0000 I've been trying to figure this one out for a few weeks now, maybe someone can shed some light on the problem. This may or may not be cross-posted to freebsd-threads (if someone wants to forward it over there -- I'm not on the list) -- I'm starting to wonder what the _true_ source of the problem is (compiler bug? I don't know for sure). Here's an initial comment about the problem, dated back in March: http://lists.freebsd.org/pipermail/freebsd-threads/2004-March/001791.html The issue is that MySQL (4.0.x, 4.1.x, and 5.x) all sig11 on machines which lack a defined CPUTYPE in make.conf (which translates over to a missing -march flag to gcc during compile-time). I've confirmed this on two -current machines, and one 5.2.1-RELEASE machine, all with different hardware and different configurations. The 5.2.1-RELEASE test I did solely to see if it was due to the latest gcc -- doesn't seem to be. Also, WITH_PROC_SCOPE_PTH makes no difference either. Details about the sig11: mysqld will sig11 on a TCP socket connect to the server itself. UNIX domain socket access does not cause the crash. Defining CPUTYPE (in my case, CPUTYPE=p4) fixes this problem and things work as they should. Can someone give me some pointers as to how I can assist in debugging what exactly is going on? Why would using -march fix this? Is this a scheduler problem per chance (a shot in the dark, I know...)? Thanks. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. |