Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Suspend/Hibernate with nvidia [m/b] chipsets in Jessie

Share your HowTo, Documentation, Tips and Tricks. Not for support questions!.
Post Reply
Message
Author
PeterB
Posts: 123
Joined: 2010-10-03 16:53
Has thanked: 1 time
Been thanked: 2 times

Suspend/Hibernate with nvidia [m/b] chipsets in Jessie

#1 Post by PeterB »

.
The change of kernel from Wheezy to Jessie introduces this WILL_NOT_FIX {sic} kernel regression, that for users of some nvidia chipset motherboards can break suspend & hibernate. Please note, this has nothing to do with nvidia graphics cards!
https://bugzilla.kernel.org/show_bug.cgi?id=48951

Its claimed to be an nvidia bug, but kernels prior to 3.3 were unaffected. Happily comment 20 in the thread contains a simple workaround.
https://bugzilla.kernel.org/show_bug.cgi?id=48951#c20

If the command

Code: Select all

lspci | grep MCP5
returns some output then you may well be affected. Aaron's fix is as follows;-

Create a file (name is unimportant I think, I called mine 50-async.rules), and place it in /etc/udev/rules.d/
The contents should be-

Code: Select all

ACTION=="add", SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_target", ATTR{power/async}="disabled"
A blank line at the end of the file is probably a good idea.



Resuming from a suspend/hibernate with USB devices attached may also fail with these motherboards. Possible fix is this udev rule;-

Code: Select all

ACTION=="add", SUBSYSTEM=="usb", TEST=="power/control", ATTR{power/control}="on"
Apply as the async rule above. I called mine 55-usbcore.rules

Hope this helps someone, it took me many hours of searching to find these fixes.


PB.

Post Reply