Date: Wed, 3 May 2006 14:55:16 -0400 From: Kris Kennaway <kris@obsecurity.org> To: "No@SPAM@mgEDV.net" <nospam@mgedv.net> Cc: freebsd-questions@freebsd.org Subject: Re: 6.1-RC2: strange kernel panic! Message-ID: <20060503185516.GA31515@xor.obsecurity.org> In-Reply-To: <007f01c66e97$b44bc760$dededede@avalon.lan> References: <20060502201054.GA93912@xor.obsecurity.org> <007f01c66e97$b44bc760$dededede@avalon.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
--BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 03, 2006 at 11:55:26AM +0200, No@SPAM@mgEDV.net wrote: > =20 > > Don't you think you should test it instead of guessing? :-) I suggested > > it because it *is* a possibility (that is why I have it in my kernel). > yes, but doesn't it make sense to find memory consuming things > before adding more? > btw. how can we check for such things? >=20 > > Are you sure you are using swap backing and not malloc? > nope, i'm not sure if it was that, but -M was passed to mdmfs, > so malloc(9) was used. we changed the code to swap-based, let's > see if that fixes our problem. Since you were using malloc backing that is what used up all your kernel memory. Increasing memory per my suggestion would have fixed it. Chances are you don't want to use malloc backing anyway though, because it's slower (unless you're swapping). Kris --BXVAT5kNtrzKuDFl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEWPyUWry0BWjoQKURAopXAJ95jKU1+8E+8Du1D+wnBAxGh0mvJwCg53qY JRZYzBuEsNXtlKBxv9cHNbc= =ySJl -----END PGP SIGNATURE----- --BXVAT5kNtrzKuDFl--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060503185516.GA31515>