Bugzilla – Bug 157380
ACPI AE_AML_MUTEX_NOT_ACQUIRED and AE_TIME errors
Last modified: 2008-06-25 09:53:51 UTC
Environement : SUSE 10 KERNEL : 2.6.13-15.8-default LAPTOP : BENQ 5000 Kernel ACPI BOOT LOG OUTPUT BIOS-e820: 000000001fff0000 - 000000001fffffc0 (ACPI data) BIOS-e820: 000000001fffffc0 - 0000000020000000 (ACPI NVS) ACPI: RSDP (v000 OID_00 ) @ 0x000e6010 ACPI: RSDT (v001 INSYDE RSDT_000 0x00000001 _CSI 0x00010101) @ 0x1fffb690 ACPI: FADT (v001 INSYDE FACP_000 0x00000100 _CSI 0x00010101) @ 0x1ffffb00 ACPI: BOOT (v001 INSYDE SYS_BOOT 0x00000100 _CSI 0x00010101) @ 0x1ffffb90 ACPI: DBGP (v001 INSYDE DBGP_000 0x00000100 _CSI 0x00010101) @ 0x1ffffbc0 ACPI: SSDT (v001 INSYDE GV3Ref 0x00002000 INTL 0x20021002) @ 0x1fffb6d0 ACPI: DSDT (v001 BENINV INT810 0x00001002 INTL 0x02002036) @ 0x00000000 ACPI: PM-Timer IO Port: 0x1008 ACPI: local apic disabled ACPI: Looking for DSDT in initrd... not found! ACPI: setting ELCR to 0200 (from 0c00) ACPI: bus type pci registered ACPI: Subsystem revision 20050408 ACPI-0229: *** Warning: Could not acquire Global Lock, AE_NO_GLOBAL_LOCK ACPI: Interpreter enabled ACPI: Using PIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) ACPI: Assume root bridge [\_SB_.PCI0] segment is 0 ACPI: Assume root bridge [\_SB_.PCI0] bus is 0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI2._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 4 5 7 *10 11) ACPI: PCI Interrupt Link [LNKB] (IRQs 6) *10 ACPI: PCI Interrupt Link [LNKC] (IRQs 4 5 7 10 *11) ACPI: PCI Interrupt Link [LNKD] (IRQs 4 5 7 10 *11) ACPI: PCI Interrupt Link [LNKE] (IRQs 4 5 7 10 *11) ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 7 10 11) *0, disabled. ACPI: PCI Interrupt Link [LNKG] (IRQs 4 5 7 10 11) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 7 10 11) *0, disabled. ACPI: Embedded Controller [EC0] (gpe 16) ACPI: Power Resource [PUT2] (on) ACPI: Power Resource [PFA1] (off) ACPI: Power Resource [PFA0] (off) pnp: PnP ACPI init pnp: PnP ACPI: found 11 devices PCI: Using ACPI for IRQ routing ACPI-0212: *** Warning: Device is not power manageable ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10 ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10 ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11 ACPI: PCI Interrupt 0000:02:09.1[B] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 apm: overridden by ACPI. ACPI-0212: *** Warning: Device is not power manageable ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 6 ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [LNKB] -> GSI 6 (level, low) -> IRQ 6 ACPI: PCI interrupt for device 0000:00:1f.6 disabled ACPI wakeup devices: ACPI: (supports S0 S3 S4 S5) ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11 ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3]) ACPI: Processor [CPU0] (supports 8 throttling states) ACPI: Thermal Zone [THZN] (32 C) ACPI: Fan [FAN0] (off) ACPI: Fan [FAN1] (off) ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10 ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11 ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 10 ACPI: PCI Interrupt 0000:00:1d.7[D] -> Link [LNKH] -> GSI 10 (level, low) -> IRQ 10 ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10 ACPI-0212: *** Warning: Device is not power manageable ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 11 ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [LNKE] -> GSI 11 (level, low) -> IRQ 11 ACPI: PCI Interrupt 0000:02:09.1[B] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 ACPI-0212: *** Warning: Device is not power manageable ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [LNKB] -> GSI 6 (level, low) -> IRQ 6 ACPI-0212: *** Warning: Device is not power manageable ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 10 ACPI: PCI Interrupt 0000:02:0a.0[A] -> Link [LNKG] -> GSI 10 (level, low) -> IRQ 10 ACPI: PCI Interrupt 0000:07:00.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 ACPI: AC Adapter [AC] (on-line) ACPI: Battery Slot [BAT0] (battery present) ACPI: Power Button (FF) [PWRF] ACPI: Sleep Button (CM) [SLPB] ACPI: Lid Switch [LID] ACPI: Power Button (CM) [PBTN] ACPI: PCI interrupt for device 0000:02:08.0 disabled ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|0], AE_TIME ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|4095], AE_TIME ACPI-0262: *** Error: Cannot release Mutex [MUT1], not acquired ACPI-1174: *** Error: Method execution failed [\STEV] (Node dfe28ca0), AE_AML_MUTEX_NOT_ACQUIRED ACPI-1174: *** Error: Method execution failed [\_SB_.AC__._PSR] (Node dffdd740), AE_AML_MUTEX_NOT_ACQUIRED ACPI-0098: *** Warning: Error reading AC Adapter state ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|0], AE_TIME ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|4095], AE_TIME ACPI-0262: *** Error: Cannot release Mutex [MUT1], not acquired ACPI-1174: *** Error: Method execution failed [\_SB_.AC__._PSR] (Node dffdd740), AE_AML_MUTEX_NOT_ACQUIRED ACPI-0098: *** Warning: Error reading AC Adapter state ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|0], AE_TIME ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|4095], AE_TIME ACPI-0284: *** Error: Thread B cannot release Mutex [MUT1] acquired by thread 132C ACPI-1174: *** Error: Method execution failed [\_TZ_.THZN._TMP] (Node dfe28a40), AE_AML_NOT_OWNER ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|0], AE_TIME ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|4095], AE_TIME ACPI-0262: *** Error: Cannot release Mutex [MUT1], not acquired ACPI-1174: *** Error: Method execution failed [\STEV] (Node dfe28ca0), AE_AML_MUTEX_NOT_ACQUIRED ACPI-1174: *** Error: Method execution failed [\_SB_.AC__._PSR] (Node dffdd740), AE_AML_MUTEX_NOT_ACQUIRED ACPI-0098: *** Warning: Error reading AC Adapter state ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|0], AE_TIME ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|4095], AE_TIME ACPI-0262: *** Error: Cannot release Mutex [MUT1], not acquired ACPI-1174: *** Error: Method execution failed [\_TZ_.THZN._TMP] (Node dfe28a40), AE_AML_MUTEX_NOT_ACQUIRED ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|0], AE_TIME ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|4095], AE_TIME ACPI-0284: *** Error: Thread B cannot release Mutex [MUT1] acquired by thread 132C ACPI-1174: *** Error: Method execution failed [\_TZ_.THZN._TMP] (Node dfe28a40), AE_AML_NOT_OWNER ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|0], AE_TIME ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|4095], AE_TIME ACPI-0262: *** Error: Cannot release Mutex [MUT1], not acquired ACPI-1174: *** Error: Method execution failed [\_SB_.AC__._PSR] (Node dffdd740), AE_AML_MUTEX_NOT_ACQUIRED ACPI-0098: *** Warning: Error reading AC Adapter state ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|0], AE_TIME ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|4095], AE_TIME ACPI-0262: *** Error: Cannot release Mutex [MUT1], not acquired ACPI-1174: *** Error: Method execution failed [\STEV] (Node dfe28ca0), AE_AML_MUTEX_NOT_ACQUIRED ACPI-1174: *** Error: Method execution failed [\_SB_.AC__._PSR] (Node dffdd740), AE_AML_MUTEX_NOT_ACQUIRED ACPI-0098: *** Warning: Error reading AC Adapter state ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [LNKE] -> GSI 11 (level, low) -> IRQ 11 ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|0], AE_TIME ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|4095], AE_TIME ACPI-0262: *** Error: Cannot release Mutex [MUT1], not acquired ACPI-1174: *** Error: Method execution failed [\_TZ_.THZN._TMP] (Node dfe28a40), AE_AML_MUTEX_NOT_ACQUIRED ACPI: PCI interrupt for device 0000:02:08.0 disabled Every few seconds I also get the following error in /var/log/messages ar 6 11:53:18 linux kernel: ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|0], AE_TIME Mar 6 11:53:18 linux kernel: ACPI-1048: *** Warning: Failed to acquire semaphore[dffd83a0|1|4095], AE_TIME Mar 6 11:53:18 linux kernel: ACPI-0262: *** Error: Cannot release Mutex [MUT1], not acquired Mar 6 11:53:18 linux kernel: ACPI-1174: *** Error: Method execution failed [\_TZ_.THZN._TMP] (Node dfe28a40), AE_AML_MUTEX_NOT_ACQUIRED
Can you reproduce this one on a current SL10.1 Beta distribution? First this one should fixed in current mainline kernels. If there is a patch that seem to be safe it could be backported.
(In reply to comment #1) > Can you reproduce this one on a current SL10.1 Beta distribution? > First this one should fixed in current mainline kernels. If there is a patch > that seem to be safe it could be backported. > I have no access to SL10.1 as I am running SUSE 10 not SUSE 10OSS , I have tried all kernel ACPI options except acpi=off as that is no use for a laptop. Can you post a link for me to an updated kernel >=2.6.14 with source and default-nongpl so that I can test it with that kernel.
ftp://ftp.suse.com/pub/projects/kernel/kotd/i386/HEAD/kernel-default.i586.rpm
Thomas, I'd like to hand this over to you for tracking.
The new kernel stops the continous ACPI-1048 messages appearing but there is a new error ACPI-0240 but it does not appear continously. Following is the log output. Mar 13 23:44:35 linux kernel: ACPI-0240: *** Error: Cannot release Mutex [MU T1], not acquired Mar 13 23:44:35 linux kernel: ACPI-0508: *** Error: Method execution failed [\_TZ_.THZN._TMP] (Node cffda940), AE_AML_MUTEX_NOT_ACQUIRED what does it mean? also yast2 complains about kernel-default-nongpl !
(In reply to comment #5) > The new kernel stops the continous ACPI-1048 messages appearing but there is a > new error ACPI-0240 but it does not appear continously. > Following is the log output. > > Mar 13 23:44:35 linux kernel: ACPI-0240: *** Error: Cannot release Mutex > [MU T1], not acquired > Mar 13 23:44:35 linux kernel: ACPI-0508: *** Error: Method execution failed > [\_TZ_.THZN._TMP] (Node cffda940), AE_AML_MUTEX_NOT_ACQUIRED > > what does it mean? also yast2 complains about kernel-default-nongpl ! > The message appeared again ACPI-0240 , is it due to a fault bios but I even upgraded the Benq joybook bios to 0.30. Any solution ?
F.Y.I Also the link for the kernel you provided does not install as it says it requires perl-Bootloader ftp://ftp.suse.com/pub/projects/kernel/kotd/i386/HEAD/kernel-default.i586.rpm error: Failed dependencies: perl-Bootloader >= 0.2.11 is needed by kernel-default-2.6.16_rc6-20060312164311 I have perl-Bootloader>= 0.2.11 linux:/home/tranceash/OperaDownloads # rpm -qa | grep perl-Bootloader perl-Bootloader-0.2-37.2 so I searched an user provided kernel latest 2.6.16 ftp://ftp.gwdg.de/pub/linux/misc/suser-jengelh/SUSE-10.0/i586/kernel-default-2.6.16-AS24.i586.rpm and installed it as there is no dependency error. I think your SUSE 10.0 and SUSE 10OSS structure is different. error ACPI-0240 produced with the later kernel.
any solution for this bug I have even compiled a custom DSDT after correcting errors in the DSDT. I still get the following errors in the logs Mar 16 15:19:47 linux kernel: ACPI-0240: *** Error: Cannot release Mutex [MUT1], not acquired Mar 16 15:19:47 linux kernel: ACPI-0508: *** Error: Method execution failed [\_TZ_.THZN._TMP] (Node cffda940), AE_AML_MUTEX_NOT_ACQUIRED all 1048 errors removed.
What happens here is: The kernel is in interupt or irq_disabled context. At this point it must not call any sleep functions. Therefore the mutex (can sleep) will not be acquired. Normally the release mutex should also be ignored in this context (maybe it already came out from interupt/irq_disabled context). As this triggers an Error value to be returned this might trigger that important functions are not processed as they recognised an error. Does this machine run well, except these messages? Hmm, it also could be a buggy BIOS (They try to release a mutex in \_TZ_.THZN._TMP and \_SB_.AC__._PSR ASL functions. Could even be more complex and mutex allocation is done over several functions, need acpidump to evaluate). I doubt I can look into this today and tomorrow as I have some other important stuff to do. I hope to be able to look into this on Monday. Can you also attach acpidump output, please.
Created attachment 73664 [details] acpidump output Please find attached acpidump as requested by you
Is there a problem in the acpidump output
any solution about this problem
Sorry for the late reply... DSDT (from acpidump) seems to be OK. I expect the problem is related to that: http://bugzilla.kernel.org/show_bug.cgi?id=5534 and could possibly be fixed with that patch: http://bugzilla.kernel.org/attachment.cgi?id=7812&action=view However, this one is a bit too big and risky to add to 10.0. Is it possible for you to install a 10.1 Beta system? I currently build a kernel rpm with the above patch included. It would be interessting whether it works for you. Tell me if you can install a 10.1 and I point you to the fixed kernel (still building).
I am using my laptop for a project at present and can change the OS only after june 23rd anyaway thanks.
There is an ongoing discussion on some bugs at bugzilla.kernel.org. There are patches but they have been rejected or are not perfect yet. Also see: http://bugzilla.kernel.org/show_bug.cgi?id=6687 this one could also be related: http://bugzilla.kernel.org/show_bug.cgi?id=5534 As all these patches are to intrusive for Code 10 right now (maybe after they have been a while in mainline and can be considered stable), I'd like to close this bug as "Later". I still have an eye on the kernel.org bugs and maybe this can go in in SPx or at least in 10.2.
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED. In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(