Hi, 2014-03-14, 12:05:01 -0400, Valdis Kletnieks wrote: > Surprisingly enough, this hasn't seemed to have bitten many Linux people yet, > Google only finds a BSD thread (where the same ACPICA code is in use): > > http://comments.gmane.org/gmane.os.dragonfly-bsd.user/1817 I was about to report the same issue on a Dell Latitude D830. Boot failure, flood of these messages: ACPI Exception: AE_AML_MUTEX_ORDER, while evaluating GPE method [_L1C] (20140214/evgpe-580) ACPI Error: Method parse/execution failed [\GPE._L1C] (Node f5e0c9a8), AE_AML_MUTEX_ORDER (20140214/psparse-536) ACPI Error: Cannot acquire Mutex for method [SX30], current SyncLevel is too large (1) (20140214/dsmethod-362) ACPI Exception: AE_AML_MUTEX_ORDER, while evaluating GPE method [_L1C] (20140214/evgpe-580) With acpi_no_auto_serialize things look good. Before I tried that option, a bisection led me to remove "| AML_CREATE" from commit f56b05bd111b. That made the laptop boot, things seemed okay, except for the battery not being detected: the normal battery line was gone ("ACPI: Battery Slot [BAT0] (battery present)") and there's this instead: ACPI Error: Cannot acquire Mutex for method [SX45], current SyncLevel is too large (1) (20140214/dsmethod-362) ACPI Error: Method parse/execution failed [\_SB_.BIF_] (Node f5c250d8), AE_AML_MUTEX_ORDER (20140214/psparse-536) ACPI Error: Method parse/execution failed [\_SB_.BAT0._BIF] (Node f5c25168), AE_AML_MUTEX_ORDER (20140214/psparse-536) ACPI Exception: AE_AML_MUTEX_ORDER, Evaluating _BIF (20140214/battery-416) -- Sabrina -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
