http://bugzilla.kernel.org/show_bug.cgi?id=6431
------- Additional Comments From [EMAIL PROTECTED] 2006-12-04 02:29 ------- On ubuntu dapper (which uses 2.6.15) > * Will now halt > md: stopping all md devices > Shutdown: hdb > ACPI-0517: *** Error: Method parse/execution failed [\_SB_PCI0.IDE0.GTM_] (node dffe6f60), AE_AML_PACKAGE_LIMIT > ACPI-0517: *** Error: Method parse/execution failed [\_SB_PCI0.IDE0.CHN0._GTM] (node dffe6380), AE_AML_PACKAGE_LIMIT > Shutdown: hda > ACPI-0517: *** Error: Method parse/execution failed [\_SB_PCI0.IDE0.GTM_] (node dffe6f60), AE_AML_PACKAGE_LIMIT > ACPI-0517: *** Error: Method parse/execution failed [\_SB_PCI0.IDE0.CHN0._GTM] (node dffe6380), AE_AML_PACKAGE_LIMIT Not sure whether this is an ACPI bug. I saw something similar when disk got set up. But this was a libata code problem invoking _STM and _GTM in wrong order: https://bugzilla.novell.com/show_bug.cgi?id=216853 AFAIK the ide and ata ACPI patches are not mainline but are like in SUSE kernels included in Ubuntu. You should be able to workaround above disk ACPI errors with: ide=noacpi libata.ata_acpi=0 Best use both, not sure whether ide or ata ACPI patches are affected (latter probably is even not included in 2.6.15 kernel, parameter just gets ignored then). You shouldn't see above errors any more then? But probably still cannot shutdown because it's another unrelated problem to the shutdown issue? About the ACPI debug error log: hwsleep-0283 [4B40] [01] enter_sleep_state : Entering sleep state [S5] hwregs-0614 [4B40] [02] hw_register_write : ----Entry hwregs-0854 [4B40] [02] hw_low_level_write : Wrote: 00001C01 width 16 to 0000000000000804 (SystemIO) hwregs-0713 [4B40] [02] hw_register_write : ----Exit- AE_OK hwregs-0614 [4B40] [02] hw_register_write : ----Entry hwregs-0713 [4B40] [02] hw_register_write : ----Exit- AE_OK hwregs-0614 [4B40] [02] hw_register_write : ----Entry Not sure, I also have a shutdown problem and looked at these code parts. Mine was always spinning at reading WAK_STS, the endless loop, when the machine should already have shut down. It looks like your's does not come that far and shortly before stops. IIRC there should come some other ACPI reads/writes to some registers, but the Intel ACPI people know better about that..., just guesses from my side. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
