From: "Michael S. Tsirkin" <mst@mellanox.co.il>
To: pavel@suse.cz, linux-pm@osdl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: T60 not coming out of suspend to RAM
Date: Tue, 22 Aug 2006 13:37:31 +0300 [thread overview]
Message-ID: <20060822103731.GC13782@mellanox.co.il> (raw)
Hi!
I'm running Linus' git tree on my thinkpad T60.
It generally seems to work fine after suspend to disk.
However, the system does not come out of suspend to ram,
with screen staying blank. I'm looking for hints for debugging this.
If I set suspend/resume event tracing, I see this in dmesg
after reboot:
dmesg -s 1000000 | grep 'hash matches'
hash matches drivers/base/power/resume.c:42
hash matches device serio2
serio2 seems to be the psmouse device:
ls /sys/bus/serio/drivers/psmouse/
bind bind_mode description serio0 serio2 unbind
Does this mean the mouse driver blocks the resume?
I've rebuilt psmouse as a module, unloaded it before suspend, and now
I see the same behaviour but after reboot:
dmesg -s 1000000 | grep 'hash matches'
hash matches drivers/base/power/resume.c:42
hash matches device i2c-9191
Which is somewhat weird because
ls /sys/bus/i2c/devices
does not list any i2c devices
I could continue disabling stuff - but I am looking in the
correct place even? How do you debug resume issues?
Thanks,
--
MST
next reply other threads:[~2006-08-22 10:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 10:37 Michael S. Tsirkin [this message]
2006-08-25 11:04 ` Pavel Machek
2006-08-28 13:53 ` Michael S. Tsirkin
2006-08-28 15:42 ` Pavel Machek
2006-08-28 17:19 ` Michael S. Tsirkin
2006-08-28 19:25 ` Andrew Morton
2006-08-28 20:19 ` Michael S. Tsirkin
2006-08-30 14:46 ` Pavel Machek
2006-08-30 15:05 ` Michael S. Tsirkin
2006-10-04 21:53 ` T60 ACPI events on 78b656b8 Michael S. Tsirkin
2006-08-25 11:55 T60 not coming out of suspend to RAM Thomas Glanzmann
2006-08-25 11:58 ` Thomas Glanzmann
2006-08-26 20:33 ` Michael S. Tsirkin
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=20060822103731.GC13782@mellanox.co.il \
--to=mst@mellanox.co.il \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.org \
--cc=pavel@suse.cz \
/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
all inboxes | Powered by JetHome®