From 51e1b77859b1cc4f8a67542a0135885121b29389 Mon Sep 17 00:00:00 2001 From: Matthew Dillon Date: Wed, 18 Oct 2017 21:43:27 -0700 Subject: [PATCH] kernel - Increase ACPI_SEMAPHORES_MAX_PENDING * Increase ACPI_SEMAPHORES_MAX_PENDING to a very large number. Some of the ACPI codes assumes that mutexes always succeed, but the mutex code uses the semaphore code and the semaphore code appears to have an arbitrary failure path based on the number of concurrent requests. * This fixes kernel confusion and console spam from the ACPI subsystem when running sysctl -a concurrently on more than 4 threads. --- sys/dev/acpica/Osd/OsdSynch.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sys/dev/acpica/Osd/OsdSynch.c b/sys/dev/acpica/Osd/OsdSynch.c index 826902f315..51f960800a 100644 --- a/sys/dev/acpica/Osd/OsdSynch.c +++ b/sys/dev/acpica/Osd/OsdSynch.c @@ -71,7 +71,7 @@ struct acpi_semaphore { #ifndef ACPI_NO_SEMAPHORES #ifndef ACPI_SEMAPHORES_MAX_PENDING -#define ACPI_SEMAPHORES_MAX_PENDING 4 +#define ACPI_SEMAPHORES_MAX_PENDING 0x1FFFFFFF #endif static int acpi_semaphore_debug = 0; TUNABLE_INT("debug.acpi_semaphore_debug", &acpi_semaphore_debug); -- 2.11.4.GIT