On 02/09/2012 06:44 PM, Sven Joachim wrote:
On 2012-02-08 23:55 +0100, Rikard Mustajärvi wrote:
8 feb 2012 kl. 22.58 skrev Sven Joachim:
On 2012-02-08 22:33 +0100, Rikard Mustajärvi wrote:
Thanks for your comment. How far away is the 3.2 kernel in
testing(wheezy?
It should hopefully migrate soon, but I'm not involved in that process.
Or is there another way?
Download the package from
http://packages.debian.org/sid/amd64/linux-image-3.2.0-1-amd64/download,
install it with "dpkg -i" and reboot.
Ok, tried it but no luck.
:-( Looks like the fix is only in 3.3 then. From the commit logs, I
suspect commit f62b27db6b5479efe376b408802a081a834ef50e¹ is the one
containing the fix, but
- The patch does not apply on 3.2, so one or several other commits might
need to be cherry-picked in addition to it.
- I cannot reproduce your problem on my hardware.
If you insist on working hibernation, your best bet is currently to
build 3.3-rc3 yourself. Would you be willing to test that?
Cheers,
Sven
¹
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=f62b27db6b5479efe376b408802a081a834ef50e
I took a quick look at the commit and I think that you're probably correct.
3.3-rc3 is a little bit too much bleeding edge for my taste. Since
suspend to ram works I'm pretty happy. I'll try the 3.3 kernel when the
first stable version is released and report back whether it fixes the
problem or not. Ok?
//Rikard
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
