Date: Mon, 07 May 2018 06:37:15 +0000 From: bugzilla-noreply@freebsd.org To: stable@FreeBSD.org Subject: [Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock Message-ID: <bug-227213-1689-HwqDmxMTsI@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-227213-1689@https.bugs.freebsd.org/bugzilla/> References: <bug-227213-1689@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227213 --- Comment #34 from Andriy Gapon <avg@FreeBSD.org> --- (In reply to Eugene Grosbein from comment #32) Oh, yes, I have. I think that that stack trace indicates two issues. 1. That a sysctl handler to print dev.XXX.N.%pnpinfo performs an ACPI evaluation. That seems to be too heavy. The code should probably use a cached value. 2. That the thread is stuck in AcpiOsAcquireMutex when trying to acquire ACPI_MTX_INTERPRETER (the interpreter lock). This could be either because some other thread is holding that lock (for whatever reason) or because of a bug in AcpiOsAcquireMutex (or maybe a bug = in DSDT). This needs further analysis. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227213-1689-HwqDmxMTsI>