Bug 1781
Summary: | AE_AML_MUTEX_NOT_ACQUIRED error messages followed by hang | ||
---|---|---|---|
Product: | ACPI | Reporter: | Mitch (mitch) |
Component: | Power-Other | Assignee: | Robert Moore (Robert.Moore) |
Status: | REJECTED UNREPRODUCIBLE | ||
Severity: | high | CC: | acpi-bugzilla, bunk |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.0 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: |
kernel boot messages
asl file from the compaq evo n600c Luming's global lock mutex patch an update a proposal update version |
Description
Mitch
2004-01-02 17:42:21 UTC
Created attachment 1784 [details]
kernel boot messages
Created attachment 1785 [details]
asl file from the compaq evo n600c
Hi Luming, I tried both the patches in those bugs to no avail. I get exactly the same behavior as before with the hang and the AE_AML_MUTEX_NOT_ACQUIRED messages. Please let me know what you'd like me to try next. The first error is an obvious BIOS bug. 1. ACPI-1120: *** Error: Method execution failed [\_SB_.C03E.C053.C0D1.C12E] (Node c7f64320), AE_AML_UNINITIALIZED_LOCAL C12E return Local0 which will not be initialized in all execution path. 2. try to release mutex which was not acquired. Please try patch filed at bug 1669 With patch from bug 1669 i get a panic on boot. Copied by hand Unable to hande kernel NULL pointer dereferenced at virtual address 99999999 printing eip: c019fa93 *pde = 00000000 Oops: 0002 [#1] CPU:0 EIP: 0060:[<c019fa93>] Not tainted EIP is at acpi_ev_acquire_global_lock:0x3f/0x6c eax: 00000000 ebx: d7fcdf60 ecx: 0000ffff edx:000000002 esi: c13edc00 edi: d7eedaa0 ebp: 00000005 esp: d7f79d8c ds: 007b es: 007b ss: 0068 Proces swapper (pid:1, threadinfo=d7f7800 task=d7f6f900) Call Trace: acpi_ex_system_acquire_mutex+0x2d/0x48 acpi_ex_acquire_mutex+0xb2/0xec acpi_ex_opcide_2A_0T_1R+0xa8/0x140 acpi_ds_exec_end_op+0xb1/0x260 acpi_ps_parse_loop+0x57c/0x890 acpi_ut_release_mutex+0x7f/0x88 acpi_ut_release_mutex+0x7f/0x88 acpi_ut_acquire_from_cache+0x45/0xa4 acpi_create_generic_state+0x7/0x14 acpi_ps_parse_aml+0x36/0x1a8 acpi_ps_parse_aml+0x53/0x1a8 acpi_psx_execute+0x15c/0x1c0 ... Next suggestion ? This may be related to the global lock code problems reported earlier Hi Luming, with the patch you sent me privately when bugzilla was down, i don't get a panic, but unfortunately i get a complete system hard hang and the bootup never completes. Not even sysrq key working. This happens with or without the acpi-20031203-2.6.1 patch. The hang is quite early in the boot process - probably a mutex deadlock. The last messages seen on the console is ACPI: Subsystem revision 20031203 ACPI: IRQ SCI: Edge Trigger ACPI: IRQ 9 SCI: Edge set to Level Triggerd (p.s. there's a typo in "Triggerd" in the kernel) I also tried boot option pci=noacpi to disable acpi routing but no luck. Created attachment 1895 [details]
Luming's global lock mutex patch
Created attachment 1903 [details]
an update
If use m operand constraint, the gcc seems to like :
c01fbfa0: a1 1c 5a 4f c0 mov 0xc04f5a1c,%eax
c01fbfa5: 89 c2 mov %eax,%edx
rather than:
c01fbfa0: a1 1c 5a 4f c0 mov 0xc04f5a1c,%eax
c01fbfa5: 89 c2 mov (%eax),%edx
But I guess the global lock mutex patch could not solve Mutex release error. Because I didn't find any error mesage related to failure of acquiring _GL . Luming, do you still wnat me to try the patch in comment 10 ? Yes, you can have it a try. And post testing result. Thanks, Luming Luming, i tried the new patch in comment 10 and although i don't get the hang at boot, i do get the subsequent hang with the AE_AML_MUTEX_NOT_ACQUIRED messages. Hmm, currect ACPI CA has bug on handling \_GL as global mutex in AML method. It could be acquired by different thread, that is different with other mutex which only can be acquired by one thread. Created attachment 2089 [details]
a proposal
this is a quick fix, please have it a try!
Created attachment 2090 [details]
update version
a proposal
Since there is still no answer, I'll add a 'me too' here. I have an evo N620C laptop, which suffers the same problem. Luming using your latest patch (id=2090) with vanilla 2.6.2 seems to solve the AE_AML_MUTEX_NOT_ACQUIRED problem (no hang, no message), but there remains another important problem: fans are not working at all (so acpi is for the moment unusable). Please have a look at bug 2083 Thanks Implemented for version 20040311: Global Lock Support: Now allows multiple acquires and releases with any internal thread. Removed concept of "owning thread" for this special mutex. Confirm Pierre's findings. With the new patch installed, no more hangs and ACPI appears to all be working except that the fans don't come on automatically. I can manually switch the fan on with echo on >/proc/acpi/fan/C1F?/state can't switch them off however with "echo off" So still basically unuseable. Back to apm. Please post the acpidump for this machine, or tell me what format the ASL attachment is in. I would like to look a little closer at the exact cause of the problem. This bug was logged 2 years ago. I no longer have the laptop. Sorry. |