Most recent kernel where this bug did not occur: n/a Distribution: Debian/Unstable Hardware Environment: Asus M6A-B020H notebook Software Environment: Problem Description: When I do S4 suspend/resume and then S3 suspend, machine freezes in endless loop in AML interpreter. Using SYSRQ-P I can see, that endless loop is in: acpi_ps_parse_loop Called sequence is: syscall_call sys_write vfs_write sysfs_write_file state_store enter_state acpi_sleep_prepare acpi_enable_wakeup_device_prep acpi_enter_sleep_state_prep acpi_evaluate_object acpi_ns_evaluate_by_name acpi_ns_evaluate_by_handle acpi_ps_execute_method acpi_ps_execute_pass acpi_ps_parse_aml acpi_ps_parse_loop Other functions get called from acpi_ps_parse_loop are called (EIP changes when several sysrq-p is trigered). S3 suspend without previous S4 is OK. I'm using: echo shutdown > /sys/power/disk echo mem > /sys/power/state for S3 suspend. (I tried platform instead of shutdown, same result).
Please : 1.post acpidump output. 2.boot with acpi_dbg_layer=0x10 acpi_dbg_level=0x10, then post dmesg Thanks, Luming
Created attachment 8197 [details] acpidump
Created attachment 8198 [details] dmesg
Please post dmesg when hang , NOT just boot. Also please enable acpi debug option when building kernel.
Unfortunately, I'm unable to post dmesg when it hangs - any error message is not in log (as syslogd is stopped).
Does serial console works for you? Also you can try to take a picture of the screen, or just write down what you see on the screen. Thanks.
Well, it seems to be fixed in 2.6.17-rc4 and later. So this bug may be closed.
Good news, I'm happy to close it now.