Date: Mon, 4 Feb 2008 07:04:19 -0800 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: Primeroz lists <primeroz.lists@googlemail.com> Cc: freebsd-stable@freebsd.org Subject: Re: Crashing repeatedly: 6.2-RELEASE-p5 and MySQL 5.0.41 Message-ID: <20080204150419.GA11397@eos.sc1.parodius.com> In-Reply-To: <55b8c6fe0802040650m3eefd1cfp79133334ed2df269@mail.gmail.com> References: <55b8c6fe0802040450r7ca3e739s931be2d38f499fc2@mail.gmail.com> <20080204133832.GA6950@eos.sc1.parodius.com> <55b8c6fe0802040619m8728e68kbe408ee4a94e591a@mail.gmail.com> <55b8c6fe0802040650m3eefd1cfp79133334ed2df269@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080204150419.GA11397>