Fedora 17 laptop freezes on resume from suspend - downgrading kernel fixes.

This is really https://bugzilla.redhat.com/show_bug.cgi?id=847479 and the bugzilla really says it all.

Something broke for certain laptops around the time of Kernel 3.5.0-2.fc17.x86_64 in that laptop suspend works just fine but on resume the screen turns a lovely shade of gray and if you manage to get a TTY you are treated to a litany of messages like

Aug 15 01:58:44 tp kernel: [13984.546007] [drm] nouveau 0000:01:00.0: PFIFO: channel 4 unload timeout
Aug 15 01:58:55 tp kernel: [13995.124015] [drm] nouveau 0000:01:00.0: Failed to idle channel 2.
Aug 15 01:58:55 tp kernel: [13995.125006] [drm] nouveau 0000:01:00.0: PFIFO: channel 2 unload timeout
Aug 15 01:59:00 tp kernel: [14000.130020] [drm] nouveau 0000:01:00.0: Failed to idle channel 3.

Again, as stated in the bugzilla, downgrading to an earlier kernel solves the problem. The bugzilla says that 3.4.6-2 (and presumably earlier) works fine, but when I used yum to look for earlier kernels, it was able to find 3.3.4-5.fc17.x86_64 for me which I installed and it works fine and both suspends and resumes without any problems.

There probably is an Nvidia component here - as can be seen I'm running the open source nouveau driver but I have seen reports with this sort of thing happening with the proprietary Nvidia driver.

My smolts profile is this http://www.smolts.org/client/show/pub_248e4572-7c6c-4a85-984b-a224a36c6cc4.

Don't know if this happens in non-Fedora kernels or not.

Addendum: With 3.6.2-4.fc17.x86_64 kernel, the video system still freezes but those messages in the TTY are gone. I went from nouveau driver to the nvidia proprietary driver by following these instructions and now suspend/resume works fine for me.  I did have to add 

                     Option "RegistryDwords" "EnableBrightnessControl=1"

to the "Device" section of /etc/X11/xorg.conf after installing nvidia driver to get the laptop's brightness control to function properly.      
Post a Comment

Popular posts from this blog

Hit failing alternator with a hammer to confirm diagnosis of failing alternator due to bad brushes

alternatives --install gets stuck: failed to read link: No such file or directory

Using SSH, SOCKS, tsocks, and proxy settings to create a simultaneous "dual use" work/home computer