my system panicked and I got a /var/crash/vmcore.4 file. The corresponding
info.4 file is:
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
Is there some sysctl that I can tweak to keep this from happening? Or is
this a bug?
TIA
Elliot
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 corresponding > info.4 file is: > > 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 > > 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20050916/1e827438/attachment.bin
Elliot Finley wrote:> my system panicked and I got a /var/crash/vmcore.4 file. The > corresponding > info.4 file is: > > 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 > > Is there some sysctl that I can tweak to keep this from happening? Or is > this a bug?Google says: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html#KMEM-MAP-TOO-SMALL> TIA > > Elliot > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >HTH, -- Dominic