panic: kmem_malloc boot error w/ 6.2
Pekka Savola
pekkas at netcore.fi
Fri Jan 26 18:39:33 UTC 2007
Hello,
(Not subscribed, let's hope this gets through..)
I saw the strangest case I've yet seen today when upgrading a dual-P3
system using sources (buildworld etc.) from FreeBSD 5.5 to RELENG_6
(6.2). The system paniced at boot with a message like:
panic: kmem_malloc(-1059844096): kmem_map too small: 2990080 total allocated
This seemed to be just before one would mount the root filesystem.
GENERIC kernel on 6.2-RELEASE boot CD worked though. FreeSBIE 2.0
kernel (6.2-RELEASE) panicked in the same way, as well as another
Rescue CD based on FreeBSD 6.1.
I did a fair bit of bisecting (about 10 compiles) to find out which
feature in GENERIC removes this panic, and came to a suprising
conclusion:
makeoptions DEBUG=-g
.. when I added this, boot works fine. When removing it, you get the
panic.
Strange, huh? :-/
Below is a snippet of the boot log:
...
acd0: DVDROM <TEAC DVD-ROM DV-28E-C/D.4B> at ata0-master UDMA33
afd0: 6869804134400MB <VIRTUALFLOPPY DRIVE Floppy > at ata2-master PIO3
acd1: CDROM <VIRTUALCDROM DRIVE/> at ata2-slave PIO3
amr0: delete logical drives supported by controller
amrd0: <LSILogic MegaRAID logical drive> on amr0
amrd0: 139900MB (286515200 sectors) RAID 1 (optimal)
panic: kmem_malloc(-1059844096): kmem_map too small: 2990080 total allocated
Uptime: 2s
Cannot dump. No dump device defined.
Automatic reboot in 15 seconds - press a key on the console to abort
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
More information about the freebsd-stable
mailing list