(Re-sending, my original post was accepted by mx1.freebsd.org, but seems to have been lost somewhere.) Thus spake Damian Gerow (dgerow_at_afflictions.org) [29/11/03 17:04]: > But this is a little OT. I'll find some way to update my system, and > respond back if the problem's fixed or not in a later -CURRENT. Nope, I'm still seeing the double fault: # uname -a FreeBSD 5.2-BETA-20031129-JPSNAP FreeBSD 5.2-BETA-20031129-JPSNAP #0: Sat Nov 29 02:47:57 GMT 2003 root_at_ushi.jp.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386 # make buildworld <snip> panic: Duplicate free of item 0xc1cd8e1c from zone 0xc102e1c0(PV ENTRY) cpuid = 0; Debugger("panic") Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0 db> trace Debugger(c0898ddc,0,c08b186e,d8a11c10,100) at Debugger+0x55 panic(c08b186e,c1cd8e1c,c102e1c0,c08b66c4,c08b13a5) at panic+0x156 uma_dbg_free(c102e1c0,0,c1cd8e1c,6d0,0) at uma_dbg_free+0x111 uma_zfree_arg(c102e1c0,c1cd8e1c,0,a2f,c08968de) at uma_zfree_arg+0x123 pmap_remove_pages(c1d0ef60,0,bfc00000,11a,c08968de) at pmap_remove_pages+0x209 exit1(c4712c80,0,c08968de,65,d8a11d40) at exit1+0x66c sys_exit(c4712c80,d8a11d14,c08b6d61,3ee,1) at sys_exit+0x41 syscall(2f,2f,2f,bfbfe938,0) at syscall+0x2c0 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x826aa63, esp = 0xbfbfe8f4, ebp = 0xbfbfe910 --- db> show pcpu 0 cpuid = 0 curthread = 0xc4712c80: pid 34357 "cc1" curpcb = 0xd8a11da0 fpcurthread = none idlethread = 0xc1cff640: pid 11 "idle: cpu0" APIC ID = 0 currentldt = 0x28 spin locks held: db> It /does/ take a bit longer to get to, and I didn't see any of the previous console-flooding messages. But the panic still happens.Received on Sun Nov 30 2003 - 16:29:13 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:32 UTC