Bug #2369

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

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

Status:NewStart date:05/16/2012
Priority:NormalDue date:
Assignee:-% Done:


Target version:-


Another panic out of the blue, this time in the wireless stack.
Version String: DragonFly v3.1.0.704.gee39c-DEVELOPMENT

panic: Bad link elm 0xffffffe07edf6068 next->prev != elm
cpuid = 1
Trace beginning at frame 0xffffffe07eca3ac0
panic() at panic+0x1fb 0xffffffff802fa6e8
panic() at panic+0x1fb 0xffffffff802fa6e8
_ieee80211_free_node() at _ieee80211_free_node+0x76 0xffffffff803c598f
ieee80211_free_node() at ieee80211_free_node+0x3c 0xffffffff803c5d9a
rt2661_reset_tx_ring() at rt2661_reset_tx_ring+0x87 0xffffffff802b13a4
rt2661_stop_locked() at rt2661_stop_locked+0x232 0xffffffff802b2261
rt2661_ioctl() at rt2661_ioctl+0x7f 0xffffffff802b46a4
parent_updown_task() at parent_updown_task+0x3f 0xffffffff803cf007
taskqueue_run() at taskqueue_run+0xc2 0xffffffff8032a16f
taskqueue_thread_loop() at taskqueue_thread_loop+0x5e 0xffffffff8032a4e5
boot() called on cpu#1

The dump is available on leaf.

Related issues

Related to Bug #2352: panic: Bad link elm 0xffffffe0a3775670 next->prev != elm Closed 04/27/2012
Related to Bug #2402: Showstopper panics for Release 3.2 New 08/15/2012


#1 Updated by marino about 4 years ago

I'm not entirely sure it's related, but it's the same panic message as #2352

Also available in: Atom PDF