Date: Fri, 16 Sep 2005 11:20:36 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Elliot Finley <efinleywork@efinley.com> Cc: freebsd-stable@freebsd.org Subject: Re: vmcore.4 Message-ID: <20050916152036.GA27619@xor.obsecurity.org> In-Reply-To: <039201c5bad0$be34c360$37cba1cd@emerytelcom.com> References: <039201c5bad0$be34c360$37cba1cd@emerytelcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 16, 2005 at 09:10:15AM -0600, Elliot Finley wrote: > my system panicked and I got a /var/crash/vmcore.4 file. The correspondi= ng > info.4 file is: >=20 > postmaster root:/var/crash#>less info.4 > Dump header from device /dev/ar0s1b > Architecture: i386 > Architecture Version: 16777216 > Dump Length: 2146631680B (2047 MB) > Blocksize: 512 > Dumptime: Sat Sep 3 14:15:04 2005 > Hostname: postmaster.etv.net > Magic: FreeBSD Kernel Dump > Version String: FreeBSD 5.4-RELEASE-p3 #4: Fri Jul 1 00:22:45 MDT 2005 > root@postmaster.etv.net:/usr/obj/usr/src/sys/GENERIC > Panic String: kmem_malloc(4096): kmem_map too small: 335544320 total > allocated > Dump Parity: 290305146 > Bounds: 4 > Dump Status: good >=20 > Is there some sysctl that I can tweak to keep this from happening? Or is > this a bug? See a recent post I made to stable that explains how to tune your kernel to fix this (you're running it out of memory). Kris --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDKuLEWry0BWjoQKURAvbzAJsFHUhWqyrjOZvPcCLaC/47xxHasgCg+/BV 47tlyhrCKUwJEne+TWGicQU= =We20 -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050916152036.GA27619>