From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 17:21:04 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 EAB1316A4C9 for ; Mon, 4 Feb 2008 17:21:04 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail04.syd.optusnet.com.au (mail04.syd.optusnet.com.au [211.29.132.185]) by mx1.freebsd.org (Postfix) with ESMTP id 9B7C713C4E9 for ; Mon, 4 Feb 2008 17:21:03 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mail04.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m14HL1bZ001521 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Feb 2008 04:21:01 +1100 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.1) with ESMTP id m14HL0Qv001412; Tue, 5 Feb 2008 04:21:00 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m14HL0bY001408; Tue, 5 Feb 2008 04:21:00 +1100 (EST) (envelope-from peter) Date: Tue, 5 Feb 2008 04:21:00 +1100 From: Peter Jeremy To: Jeremy Chadwick Message-ID: <20080204172100.GB1124@server.vk2pj.dyndns.org> References: <55b8c6fe0802040450r7ca3e739s931be2d38f499fc2@mail.gmail.com> <20080204133832.GA6950@eos.sc1.parodius.com> <55b8c6fe0802040619m8728e68kbe408ee4a94e591a@mail.gmail.com> <55b8c6fe0802040650m3eefd1cfp79133334ed2df269@mail.gmail.com> <20080204150419.GA11397@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline In-Reply-To: <20080204150419.GA11397@eos.sc1.parodius.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) 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 17:21:05 -0000 --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 04, 2008 at 07:04:19AM -0800, Jeremy Chadwick wrote: >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. By definition, if a userland process causes a kernel panic, it's the fault of the kernel. >> > $ sudo -u mysql limits >> Resource limits (current): >> cputime infinity secs >> filesize infinity kB >> datasize 33554432 kB These are defaults and so are unlikely to be causing problems. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHp0l8/opHv/APuIcRAlZBAKCgSb4V1OORbGmaYW2KhvT4BgwVUwCfeHzZ p0tC1hD0gklomasxYFrBYqw= =d6AN -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh--