[DragonFlyBSD - Bug #2934] (In Progress) kernel (4.7) panic at buildworld: assertion "gd->gd_spinlocks == 0" failed

bugtracker-admin at leaf.dragonflybsd.org bugtracker-admin at leaf.dragonflybsd.org
Mon Aug 8 10:59:19 PDT 2016

Issue #2934 has been updated by dillon.

Status changed from New to In Progress
% Done changed from 0 to 80

Excellent backtrace, I believe I found the issue and I committed a fix to both master and the release branch that should work around the problem.

The issue is that the ACPI code is issuing a kmalloc() while holding a spinlock.  This is illegal, but I couldn't immediately fix it (I have to research it a bit more).  However, the particular panic is from a yield via that path (kmalloc -> issues any prior staged frees -> vm system -> lwkt_user_yield), and I can detect the problem in the yield and return rather than yield for now.


Bug #2934: kernel (4.7) panic at buildworld: assertion "gd->gd_spinlocks == 0" failed

* Author: peeter
* Status: In Progress
* Priority: Normal
* Assignee: dillon
* Category: Kernel
* Target version: 
Kernel (DragonFly v4.7.0.109.g609bcd-DEVELOPMENT) panics at "make buildworld". 

Panic String: assertion "gd->gd_spinlocks == 0" failed in dfly_schedulerclock at /usr/src/sys/kern/usched_dfly.c:757

kgdb output is attached.

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

More information about the Bugs mailing list