Re: panic: kmem_malloc(171642880): kmem_map too small: 31387648 total allocated

On Sun, Jan 22, 2006 at 08:03:52AM +0000, Pawel Worach wrote:
> Stefan Ehmann wrote:
> > I had similar problems. removing atatpicam fixed this.
> > 
> > Also I could run a buildworld without a panic. Might be only by chance
> > though (don't know how easily the panic was reproducible).
> > 
> 
> I have a similar panic here, seems like ATAPICAM finds a bogus CD in the 
> drive and then GEOM_ELI tries to taste it.
> 
> cd0_at_ata1 bus 0 target 0 lun 0
> cd0: <HL-DT-ST RW/DVD GCC-4242N 0201> Removable CD-ROM SCSI-0 device
> cd0: 33.000MB/s transfers
> cd0: \M-_at_:\M-W\M-D\^P
> 
> panic: kmem_malloc(536870912): kmem_map too small: 14929920 total allocated
> KDB: stack backtrace:
> kdb_backtrace(c071ee05,c0774e20,c072fcb3,e35a85ac,100)_at_kdb_backtrace+0x2e
> panic(c072fcb3,20000000,e3d000,e35a85dc,c070cfed)_at_panic+0xb7
> kmem_malloc(c104c0a8,20000000,2,e35a862c,c068e532)_at_kmem_malloc+0xab
> page_alloc(0,20000000,e35a861f,2,c56d47bc)_at_page_alloc+0x27
> uma_large_malloc(20000000,2,e35a8650,c04ead43,20000000)_at_
> uma_large_malloc+0x52malloc(20000000,c0746c80,2,0,c56ef9c0)_at_malloc+0x9e
> g_read_data(c56ef9c0,0,200000,20000000,0)_at_g_read_data+0x50
> g_eli_read_metadata(c0746980,c56e0600,e35a8a7c,c0719b38,c56e0658)_at_
> g_eli_read_metadata+0xe1
> g_eli_taste(c0746980,c56e0600,0,c56e0700,4)_at_g_eli_taste+0xdc
> g_new_provider_event(c56e0600,0,0,c072c28d,0)_at_g_new_provider_event+0x7a
> one_event(66666667,c4aa1bd0,0,e35a8d00,c04eb955)_at_one_event+0x219
> g_run_events(c0772c90,0,4c,c072c28d,64)_at_g_run_events+0x15
> g_event_procbody(0,e35a8d38,0,0,0)_at_g_event_procbody+0x85
> fork_exit(c04eb8d0,0,e35a8d38)_at_fork_exit+0x7f
> fork_trampoline()_at_fork_trampoline+0x8
> --- trap 0x1, eip = 0, esp = 0xe35a8d6c, ebp = 0 ---
> Uptime: 16m5s
> Dumping 1023 MB (2 chunks)
>    chunk 0: 1MB (159 pages) ... ok
>    chunk 1: 1023MB (261728 pages) 1007 991 975 959 943 927 911 895 879 
> 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 
> 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 
> 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15
> 
> #0  doadump ()_at_pcpu.h:166
> 166     pcpu.h: No such file or directory.
>          in pcpu.h
[..]

I have had similar problem on my laptop few weeks ago, ASUS A4D.
Unfortunately I didn't have opportunity to obtain more information.
Although I don't have dmesg -v output, traces are here:

	http://zsno.ids.czest.pl/~dunstan/FreeBSD/kmem01.log
	http://zsno.ids.czest.pl/~dunstan/FreeBSD/kmem02.log

Some information about an environment: FreeBSD-CURRENT from the middle
of December, filesystem with softupdates, snapshots, ACLs, MAC enabled.
My case was somehow different: I was able to build world, but system got
a panic while starting X environment.

-- 
* Wojciech A. Koszek && <dunstan%zsno.ids.czest.pl>