[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060825110441.GB8538@elf.ucw.cz>
Date: Fri, 25 Aug 2006 13:04:41 +0200
From: Pavel Machek <pavel@....cz>
To: "Michael S. Tsirkin" <mst@...lanox.co.il>
Cc: linux-pm@...l.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: T60 not coming out of suspend to RAM
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?
Yes, disabling stuff is way to go. Just disable everything, and binary
search from there :-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists