Issue #2934 has been updated by dillon. Assignee set to dillon
Hmm. It looks like splz() was called while a spinlock was held, but the backtrace doesn't go far enough to see who called splz(). From kgdb you can manually spill the stack and write down any procedural symbols that you get. frame 7 info regi (extract contents of %rsp) x/a 0x<value_of_rsp> And then hit return a lot to iterate the x/a. Write down any procedural symbols that you come across. The goal here is to try to figure out what code path called splz(). -Matt ---------------------------------------- Bug #2934: kernel (4.7) panic at buildworld: assertion "gd->gd_spinlocks == 0" failed http://bugs.dragonflybsd.org/issues/2934#change-12960 * Author: peeter * Status: New * Priority: Normal * Assignee: dillon * Category: Kernel * Target version: ---------------------------------------- Kernel (DragonFly v4.7.0.109.g609bcd-DEVELOPMENT) panics at "make buildworld". /var/crash/info.1: --- Panic String: assertion "gd->gd_spinlocks == 0" failed in dfly_schedulerclock at /usr/src/sys/kern/usched_dfly.c:757 --- kgdb output is attached. ---Files-------------------------------- kgdb.txt.1 (28.7 KB) -- 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
