Acer 6592 TM, suspend to ram and resume freeze

[Robert Jarzmik]

First of all, sorry for the duplicate on linux-pm, but as Pavel suggested, this
topic gains wider audience as acpi and pm are involved.

I have an issue with my laptop with suspend to ram.
My laptop is an Acer Travelmate 6592g :

> [rj@velvet wireshark-1.0.5 (master)]$ sudo s2ram -i
> This machine can be identified by:
>     sys_vendor   = "Acer"
>     sys_product  = "TravelMate 6592"
>     sys_version  = "PSMBOU-1234567"
>     bios_version = "V1.53   "

The kernel running is the last I have : 2.6.29-rc1, but the problem is the same
whatever the kernel version I take (between 2.6.16 and 2.6.29-rc1).

The issue is that even if the laptop enters suspend correctly, it hangs on
comming out of it. After some research, I cornered down the module which changes
the behaviour : acpi_cpufreq.ko.

When I forbid the laptop to load this module, the suspend to ram works like a
charm, in "init" single mode or multi-user mode. When I load the module, the
resume always hangs (fan goes high speed like crazy, no LCD back, hard drive led
stays on, caps_lock key not responsive, ...)

Now, I notice that loading acpi-cpufreq triggers the following message :
> log: Jan 19 18:23:42 velvet kernel: ACPI: EC: non-query interrupt received, switching to interrupt mode

As this is not the part of the kernel I'm most at ease with, I'd like some help
to investigate. I'll gladly make any test or apply patches to my own git tree.

I join to this mail a URL [1] to see the little information I have :
 - kernel messages (/var/log/messages), for single user startup
 - ACPI table
 - my kernel configuration
 - kernel message for a working suspend to ram (ie. without acpi_cpufreq).
 - I suspend using s2ram -f -v -p -s

Best regards.

--
Robert

[1] http://belgarath.hd.free.fr/download/acer6592tm/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/