From: Robert Jarzmik <robert.jarzmik@free.fr>
To: linux-pm@lists.linux-foundation.org
Subject: Acer 6592 TM, suspend to ram and resume freeze
Date: Fri, 23 Jan 2009 23:53:22 +0100 [thread overview]
Message-ID: <87r62tws65.fsf@free.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]
Hello,
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.
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 joined to this mail the little information I had :
- 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
[-- Attachment #2: Kernel log --]
[-- Type: application/octet-stream, Size: 6166 bytes --]
[-- Attachment #3: ACPI table --]
[-- Type: application/octet-stream, Size: 14435 bytes --]
[-- Attachment #4: Kernel configuration --]
[-- Type: application/octet-stream, Size: 22107 bytes --]
[-- Attachment #5: Kernel log of a working suspend --]
[-- Type: application/octet-stream, Size: 5687 bytes --]
[-- Attachment #6: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2009-01-23 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 22:53 Robert Jarzmik [this message]
2009-02-03 11:33 ` Acer 6592 TM, suspend to ram and resume freeze Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2009-02-03 20:36 Robert Jarzmik
2009-02-04 1:52 ` ZhangRui
2009-02-04 2:21 ` yakui_zhao
[not found] ` <1233712347.6643.7.camel@rzhang-desktop>
2009-02-05 19:08 ` Robert Jarzmik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r62tws65.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=linux-pm@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox