From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 15:04:19 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79FDC16A420 for ; Mon, 4 Feb 2008 15:04:19 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 6425013C447 for ; Mon, 4 Feb 2008 15:04:19 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 33AA01CC038; Mon, 4 Feb 2008 07:04:19 -0800 (PST) Date: Mon, 4 Feb 2008 07:04:19 -0800 From: Jeremy Chadwick To: Primeroz lists Message-ID: <20080204150419.GA11397@eos.sc1.parodius.com> References: <55b8c6fe0802040450r7ca3e739s931be2d38f499fc2@mail.gmail.com> <20080204133832.GA6950@eos.sc1.parodius.com> <55b8c6fe0802040619m8728e68kbe408ee4a94e591a@mail.gmail.com> <55b8c6fe0802040650m3eefd1cfp79133334ed2df269@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55b8c6fe0802040650m3eefd1cfp79133334ed2df269@mail.gmail.com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-stable@freebsd.org Subject: Re: Crashing repeatedly: 6.2-RELEASE-p5 and MySQL 5.0.41 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2008 15:04:19 -0000 On Mon, Feb 04, 2008 at 02:50:09PM +0000, Primeroz lists wrote: > Just wanted to point out that anyway our crash is a Kernel panic crash and > not a Mysqld crash. But the process that's inducing the panic *every time* is mysqld; this you've already confirmed. To me this means that mysqld is responsible for tickling some sort of condition that causes a panic; it could be the fault of mysqld or it could be the fault of FreeBSD. > Platform is AMD64 so , i'm don't think it can be a problem of process size : > > > $ sudo -u mysql limits > Resource limits (current): > cputime infinity secs > filesize infinity kB > datasize 33554432 kB ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is interesting, since your machine only has 8GB of RAM. I am not familiar with the amd64 platform, so it's possible that kern.maxdsiz and kern.dfldsiz get set to something completely different than what I'm used to seeing on i386. -- | 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. PGP: 4BD6C0CB |