Re: kernel panic with latest sources

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

    I added some additional sanity checks to hopefully avoid a crash
    here, but my guess is that you tried to boot DragonFly with a
    5.x userland, which won't work (5.x binaries are not even close to
    being backwards compatible with 4.x and 5.x's mount would look like
    total garbage to a 4.x kernel).

					-Matt
					Matthew Dillon 
					<dillon@xxxxxxxxxxxxx>


:I just cvsup'd the latest sources and built/installed a kernel and rebooted.
:
:Upon rebooted, it was initializing userland when it failed with something
:like this:
:
:Starting final network daemons: mountd
:Panic: kmem_alloc (134676480) kmem_map too small 8273920 total allocated
:
:[ hand-transcribed ]
:db> trace
:Debugger(c02a76fb) at Debugger+0x34
:panic(c02bda20,8070000,7e4000,c0305cbc,c02e52c0) at panic+0x70
:kmem_malloc(c030fcc0,8070000,0,806f9d9,cc240b58) at kemm_malloc+0xdd
:malloc(806f9dd,c02e52c0,0,c10d5600,cc240b58) at malloc+0x1ef
:vfs_hang_addrlist(c10d5600,c10d5440,cc240b58,0,c10d6000) at
:vfs_hang_addrlist+0xa0
:vfs_export(c10d5600,c10d5440,cc240b58,0,c10d5600) at vfs_export+0x61
:ffs_mount(c10d5600,809b0b0,bfbff440,cc240c40,cae80980) at ffs_mount+0x367
:mount(cc240d20,809b0b5,80a1040,0,cc240d20) at mount+0x65f
:syscall2(2f,2f,2f,0,80a1040) at syscall2+0x200
:
:--
:Matt Emmerton