Issue #2508 has been updated by ftigeot. Status changed from New to Resolved
This issue can't be reproduced after many recent poudriere-induced kernel changes. ---------------------------------------- Bug #2508: panic running poudriere: lockmgr thrd_sleep from /usr/src/sys/kern/kern_slaballoc.c:1425: called with 1 spinlocks held http://bugs.dragonflybsd.org/issues/2508 Author: ftigeot Status: Resolved Priority: Normal Assignee: Category: Target version: Running 6 poudriere jobs on a 4 cores / 8 threads machine After ~= 30 minutes, the machine panicked and rebooted by itself No core dump was saved. These messages were left in the dmesg buffer after the reboot: panic: lockmgr thrd_sleep from /usr/src/sys/kern/kern_slaballoc.c:1425: called with 1 spinlocks held cpuid = 0 Trace beginning at frame 0xffffffe280c78068 panic() at panic+0x1fb 0xffffffff8050a5f8 panic() at panic+0x1fb 0xffffffff8050a5f8 debuglockmgr() at debuglockmgr+0xab 0xffffffff804f985a kmem_slab_alloc() at kmem_slab_alloc+0x79 0xffffffff80506873 kmalloc() at kmalloc+0x663 0xffffffff80507beb gnode_insert() at gnode_insert+0x30 0xffffffff80592f48 vfs_stdaccount() at vfs_stdaccount+0x12c 0xffffffff805933de vop_write() at vop_write+0x1bc 0xffffffff805a0a60 vn_write() at vn_write+0x23d 0xffffffff8059d6a9 kern_pwritev() at kern_pwritev+0x171 0xffffffff80547c01 sys_write() at sys_write+0x66 0xffffffff80547e23 syscall2() at syscall2+0x3fc 0xffffffff808e1923 Xfast_syscall() at Xfast_syscall+0xcb 0xffffffff808cb1bb boot() called on cpu#0 Uptime: 1h42m57s -- 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
