Hi,

while I haven't conducted as many tests as Denis has, I can say that my
T500 hibernated nicely up until 2.6.32 last version before -36 (I can't
currently confirm for 2.6.32-36), and breaks for every later kernel.
I can also say that, for the even more recent kernels, the machine does
not even suspend-to-ram.

I'm running the -686 variant of things, not the amd64 stuff.


Feel free to ask any questions.


Kind regards,
--Toni++



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4E7702F3.5090109@oeko.net">http://lists.debian.org/4E7702F3.5090109@oeko.net

Hi Toni,

Toni Müller wrote:

> while I haven't conducted as many tests as Denis has, I can say that my
> T500 hibernated nicely up until 2.6.32 last version before -36 (I can't
> currently confirm for 2.6.32-36), and breaks for every later kernel.
> I can also say that, for the even more recent kernels, the machine does
> not even suspend-to-ram.

That doesn't necessarily sound like the same bug (Denis was testing
with 3.0.0-1 and had no trouble suspending iirc). The narrow
regression range is good news from the point of view of being able to
find a fix. Could you file a new bug listing kernels you've tested
and results for each? The upgrade history of the kernel image
packages can be found at /var/log/dpkg.log*.

If the symptoms turn out to have the same cause, we can merge the bugs
later.

Thank you,
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110919155708.GA2861@elie">http://lists.debian.org/20110919155708.GA2861@elie