Re: [issue2037] Panic Bad link elm while building packages

Hi Matt,

unfortunately still not ok (for me). Two panics in the last 24 hours (strangely no core dumps) on x86_64.

This issue is in my case unrelated to package building, it happended at times when i wasn't working on the machine, i.e. it was supposed to be (almost) idle.


* with  v2.9.1.1706.gc368d-DEVELOPMENT

Apr 20 14:56:52 randy syslogd: kernel boot file is /boot/kernel/kernel
Apr 20 14:56:52 randy kernel: spin_lock: 0xffffffe005dab660, indefinite wait!
Apr 20 14:56:52 randy kernel: panic: Bad link elm 0xffffffe042c67878 next->prev != elm
Apr 20 14:56:52 randy kernel: cpuid = 0
Apr 20 14:56:52 randy kernel: boot() called on cpu#0
Apr 20 14:56:52 randy kernel: Uptime: 2h51m44s
.....
and so on with same pattern many times; rest of output is corrupted and unreadable


and this after update to v2.11.0.4.ge92d7-DEVELOPMENT:

Apr 21 03:08:49 randy syslogd: kernel boot file is /boot/kernel/kernel
Apr 21 03:08:49 randy kernel: spin_lock: 0xffffffe005dab660, indefinite wait!
Apr 21 03:08:49 randy kernel: panic: Bad link elm 0xffffffe042c67878 next->prev != elm
Apr 21 03:08:49 randy kernel: cpuid = 0
Apr 21 03:08:49 randy kernel: boot() called on cpu#0
Apr 21 03:08:49 randy kernel: Uptime: 4h45m40s
Apr 21 03:08:49 randy kernel: spin_lock: 0xffffffe005dab660, indefinite wait!
Apr 21 03:08:49 randy kernel: panic: Bad link elm 0xffffffe042c67878 next->prev != elm
Apr 21 03:08:49 randy kernel: cpuid = 0
Apr 21 03:08:49 randy kernel: boot() called on cpu#0
Apr 21 03:08:49 randy kernel: Uptime: 4h45m40s
Apr 21 03:08:49 randy kernel: spin_lock: 0xffffffe005dab660, indefinite wait!
Apr 21 03:08:49 randy kernel: panic: Bad link elm 0xffffffe042c67878 next->prev != elm
Apr 21 03:08:49 randy kernel: cpuid = 0
Apr 21 03:08:49 randy kernel: boot() called on cpu#0
Apr 21 03:08:49 randy kernel: Uptime: 4h45m40s
Apr 21 03:08:49 randy kernel: spin_lock: 0xffffffe005dab660, indefinite wait!
Apr 21 03:08:49 randy kernel: panic: Bad link elm 0xffffffe042c67878 next->prev != elm
Apr 21 03:08:49 randy kernel: cpuid = 0
Apr 21 03:08:49 randy kernel: boot() called on cpu#0
Apr 21 03:08:49 randy kernel: Uptime: 4h45m40s


Thanks!

On Tue, 05 Apr 2011 18:17:23 +0000
"Matthew Dillon \(via DragonFly issue tracker\)" <[e-mail]> wrote:

> 
> Matthew Dillon <[e-mail]> added the comment:
> 
> See issue 2037, possible fix committed.  It looks like there may have been a
> race in tsleep() where the stack-declared callout structure could wind up not
> being reset prior to tsleep() returning.
> 
> 8d4468507289f84cc7f60a6520c607713f84f009
> 
> ----------
> assignedto:  -> dillon
> nosy: +dillon
> status: chatting -> testing
> 
> _____________________________________________________
> DragonFly issue tracker <[e-mail]>
> <http://bugs.dragonflybsd.org/issue2037>
> _____________________________________________________
>