[DragonFlyBSD - Bug #2352] (Closed) panic: Bad link elm 0xffffffe0a3775670 next->prev != elm

[Matthew Dillon via Redmine <bugtracker-admin@xxxxxxxxxxxxxxxxxxxxx>]

Issue #2352 has been updated by Matthew Dillon.

Status changed from New to Closed

This bug should be fixed in 0730ed66e3324415127af9bc0fe9dafa399f4e91 now.

----------------------------------------
Bug #2352: panic: Bad link elm 0xffffffe0a3775670 next->prev != elm
http://bugs.dragonflybsd.org/issues/2352

Author: Joachim de Groot
Status: Closed
Priority: Normal
Assignee: 
Category: 
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.


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account