This is 100% identical to my panic. My system is a dual athlon/2G system too.
In message <[EMAIL PROTECTED]>, "David O'Brien" writes: >--- >#0 doadump () at ../../../kern/kern_shutdown.c:232 >232 dumping++; >(kgdb) bt >#0 doadump () at ../../../kern/kern_shutdown.c:232 >#1 0xc01eac9e in boot (howto=260) at ../../../kern/kern_shutdown.c:364 >#2 0xc01eaf39 in panic () at ../../../kern/kern_shutdown.c:517 >#3 0xc02e25ed in kmem_malloc (map=0xc082e07c, size=4096, flags=4) at >../../../vm/vm_kern.c:336 >#4 0xc02f25a7 in page_alloc (zone=0xc083a600, bytes=0, pflag=0x0, wait=0) at >../../../vm/uma_core.c:798 >#5 0xc02f230d in slab_zalloc (zone=0xc083a600, wait=4) at ../../../vm/uma_core.c:707 >#6 0xc02f33d3 in uma_zone_slab (zone=0xc083a600, flags=0) at >../../../vm/uma_core.c:1486 [...] -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
