Bug #2352

panic: Bad link elm 0xffffffe0a3775670 next->prev != elm

Added by jaydg over 4 years ago. Updated about 4 years ago.

Status:ClosedStart date:04/27/2012
Priority:NormalDue date:
Assignee:-% Done:


Target version:-


Though there already are some bugs open with a similar message, this one seems to be different:

Unread portion of the kernel message buffer:
panic: Bad link elm 0xffffffe0a3775670 next->prev != elm
cpuid = 1
Trace beginning at frame 0xffffffe0b7349948
panic() at panic+0x1fb 0xffffffff802fa588
panic() at panic+0x1fb 0xffffffff802fa588
proc_remove_zombie() at proc_remove_zombie+0x57 0xffffffff802f1f0e
kern_wait() at kern_wait+0x28e 0xffffffff802e5d25
sys_wait4() at sys_wait4+0x44 0xffffffff802e5ff4
syscall2() at syscall2+0x370 0xffffffff80547f61

This happens on DragonFly v3.1.0.586.g6c7e9-DEVELOPMENT x86_64.

A dump is available.

Related issues

Related to Bug #2369: panic: Bad link elm 0xffffffe07edf6068 next->prev != elm New 05/16/2012
Related to Bug #2402: Showstopper panics for Release 3.2 New 08/15/2012


#1 Updated by alexh over 4 years ago

Please upload the dump to leaf.


#2 Updated by jaydg over 4 years ago

I've uploaded the dump on leaf, ~jaydg/crash/2352.

#3 Updated by dillon about 4 years ago

  • Status changed from New to Closed

This bug should be fixed in 0730ed66e3324415127af9bc0fe9dafa399f4e91 now.

Also available in: Atom PDF