FS#16580 - [kernel26] 2.6.31 system not waking from suspend to ram

Attached to Project: Arch Linux
Opened by Jithin Emmanuel (jithin1987) - Monday, 12 October 2009, 05:30 GMT
Last edited by Paul Mattal (paul) - Monday, 09 November 2009, 12:06 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan de Groot (JGC)
Architecture i686
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
After doing suspend to ram my system is not waking up from sleep

Additional info:
* package version(s)
kernel26 (2.6.31.3-1)
xf86-video-intel (2.8.1-1)
mesa (7.5.1-2)
* config and/or log files etc.

From lscpi
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)

I had the same issue when on kubuntu karmuc alphas. They seems to have fixed this by some patches kernel and mesa.This is the bug report on launchpad for this issue.
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/429241


Steps to reproduce:
Just do a suspend to ram and try to wake up
This task depends upon

Closed by  Paul Mattal (paul)
Monday, 09 November 2009, 12:06 GMT
Reason for closing:  Upstream
Additional comments about closing:  Upstream and fixed at some point in 2.6.32-git.
Comment by A.F.G. (TuxLin) - Monday, 12 October 2009, 09:31 GMT
I confirm this issue.

Yesterday, after suspending to ram, when in the resume cycle, the system show a black screen and I can only to push reset button to reboot.

Architecture: amd64 X2

Version: x86_64

nvidia-185.18.36-2 on G96 GeForce 9400 GT gpu.
kernel26 2.6.31.1
mesalib 7.5.1-2

( This is the first time I try to suspend to Ram or Disk )

Comment by Kirt Lillywhite (kfrance) - Tuesday, 13 October 2009, 17:41 GMT
I have a Asus netbook, 1005ha, and when I upgraded to the latest kernel 2.6.31.3-1, I also started having problems waking up from suspend. I didn't have the problem previously. It appears, though, that it is only a problem when wireless is turned off. If I turn wireless on I can suspend and resume just fine.
Comment by Ramil (gravicappa) - Saturday, 17 October 2009, 06:10 GMT
Same issue on i686 (kernel26 2.6.31.4-1 nvidia 185.18.36-2).
Comment by Jithin Emmanuel (jithin1987) - Saturday, 17 October 2009, 11:14 GMT
I think the fix is with mesa and might be fixed when mesa 1.6 moves to core from testing
Comment by Jithin Emmanuel (jithin1987) - Friday, 30 October 2009, 08:59 GMT
Even mesa 7.6 does not have the fix. I just now updated to testing repo and the bug is still there.

This is the bug report in freedesktop https://bugs.freedesktop.org/show_bug.cgi?id=23932

And this is the commit which fixes it http://cgit.freedesktop.org/mesa/mesa/commit/?id=acfea5c705f383692e661d37c5cd7da2f3db559b

Can we have a patch in our mesa for this?
Comment by Jose Marino (oniram) - Sunday, 01 November 2009, 14:25 GMT
Maybe some people are seeing this kernel bug (regression from 2.6.31.1 to 2.6.31.2):
http://bugzilla.kernel.org/show_bug.cgi?id=14334

An easy way to test would be to unload pcmcia and yenta_socket modules before suspending.
Comment by Jithin Emmanuel (jithin1987) - Monday, 02 November 2009, 01:16 GMT
I had this exact proble in ubuntu 9.10 betas. From the launch pad bug report I posted the fix was on mesa. But updating to latest mesa from testing didnt solve the problem. Not sure if the commit is part of mesa 7.6-2.

But there back in ubuntu I was able to ssh into the box but here I am not able to do that also.
Comment by Jithin Emmanuel (jithin1987) - Monday, 02 November 2009, 01:33 GMT
How to unload these modules its giving error already in use.
Comment by Jose Marino (oniram) - Monday, 02 November 2009, 07:21 GMT
To unload the modules do (as root):
rmmod pcmcia yenta_socket
Comment by Jithin Emmanuel (jithin1987) - Monday, 02 November 2009, 15:42 GMT
I get this error
rmmod pcmcia yenta_socket
ERROR: Module pcmcia is in use by ide_cs,pata_pcmcia
ERROR: Module yenta_socket is in use

Do I have to unload all these modules?
Comment by Jose Marino (oniram) - Monday, 02 November 2009, 16:09 GMT
I guess you must have a hard drive or something connected to the pcmcia. You could try disconnecting it first.
An easier approach would be to add !yenta_socket to MODULES in /etc/rc.conf then reboot and test the suspend.
Comment by Jithin Emmanuel (jithin1987) - Monday, 02 November 2009, 16:26 GMT
I am using a laptop. So disconnecting anything does not seem to be a option. What does yenta_socket do ?
Comment by Jose Marino (oniram) - Monday, 02 November 2009, 23:08 GMT
From the kernel documentation -> yenta_socket:
Enables support for CardBus host bridges. Virtually
all modern PCMCIA bridges are CardBus compatible. A "bridge" is
the hardware inside your computer that PCMCIA cards are plugged into.
Comment by Joel (torpe23) - Friday, 06 November 2009, 20:23 GMT
Isn't it the same bug as http://bugs.archlinux.org/task/15267 ?
Comment by Jithin Emmanuel (jithin1987) - Saturday, 07 November 2009, 01:26 GMT
That is different I was able to successfully suspend with 2.6.30 kernel.
Comment by Jithin Emmanuel (jithin1987) - Saturday, 07 November 2009, 14:03 GMT
Installing 2.6.32-rc6 kernel fixes the issue. 32 kernel also fixes a usb regresseion I had with 31.

Loading...