Bug 767416 - kernel-3.1.5-1.fc16.x86_64 breaks resume (from suspend) on Lenovo W510
Summary: kernel-3.1.5-1.fc16.x86_64 breaks resume (from suspend) on Lenovo W510
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-14 00:18 UTC by David Kovalsky
Modified: 2014-03-31 23:46 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-09 15:48:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
tail of /var/log/messages (13.36 KB, text/plain)
2011-12-14 00:18 UTC, David Kovalsky
no flags Details
pm-suspend.log (6.97 KB, text/plain)
2011-12-14 00:19 UTC, David Kovalsky
no flags Details

Description David Kovalsky 2011-12-14 00:18:02 UTC
Created attachment 546479 [details]
tail of /var/log/messages

After upgrading to kernel-3.1.5-1.fc16.x86_64 from updates testing, my notebook is failing to resume from suspend. The power button is flashing and if I press it, the fans start, but seems nothing else happens. 

Attaching last lines from /var/log/messages and whole pm-suspend.log in hope they will be useful.

Comment 1 David Kovalsky 2011-12-14 00:19:03 UTC
Created attachment 546480 [details]
pm-suspend.log

Comment 2 Josh Boyer 2011-12-15 20:15:54 UTC
You have a lot of odd modules loaded for a laptop.  iscsi, infiniband, and parallel ports aren't often found in those machines.

Anyway, you might want to try some of the things here:

https://fedoraproject.org/wiki/KernelCommonProblems#Suspend.2FResume_failure

First on the list would be not using the nvidia module.  You also seem to be having some issues with one of your USB devices in the /var/log/messages you attached, so removing whatever device that is before you suspend might also be worth trying.

Comment 3 Dennis Appelon Nielsen 2011-12-16 21:18:04 UTC
Hi have the same problem with my Lenovo W510 see 

https://bugzilla.redhat.com/show_bug.cgi?id=767248

I'm going crazy looking for an answer

Comment 4 John Gotts 2011-12-26 00:27:58 UTC
Does booting with pci=nocrs fix the problem?

Comment 5 Dennis Appelon Nielsen 2011-12-26 21:14:48 UTC
(In reply to comment #4)
> Does booting with pci=nocrs fix the problem?

Hi John Gotts
Thanks for the input, but no! it don't solve the problem. I presume adding the pci=nocrs is done in grub2 like it was in grub (That was what I did) ?

Comment 6 Dennis Appelon Nielsen 2011-12-26 21:15:51 UTC
The Problem persist in latest kernel release 3.1.6-1.fc16.x86_64

Comment 7 Michael Buchfink 2011-12-28 17:14:25 UTC
Booting with hpet=disable solved the problem for me.

Comment 8 Dennis Appelon Nielsen 2011-12-28 21:07:11 UTC
(In reply to comment #7)
> Booting with hpet=disable solved the problem for me.

Hi Michael Buchfink
Thanks for you input it also solved the problem for me, but what on Earth is "hpet" ? and why do it break the un-suspend  function for Lenovo's W510 ?

Best regards
Dennis Appelon Nielsen

Comment 9 Michael Buchfink 2011-12-29 11:30:40 UTC
> Hi Michael Buchfink
> Thanks for you input it also solved the problem for me, but what on Earth is
> "hpet" ? and why do it break the un-suspend  function for Lenovo's W510 ?

Good question!

This issue with the (H)igh (P)recision (E)vent (T)imer was brought into life with a change for kernel 3.1.5. It seems, that they are working on it

http://lkml.indiana.edu/hypermail/linux/kernel/1112.3/00405.html

Comment 10 Josh Boyer 2012-01-03 12:36:57 UTC
There is an upstream commit that was added to 3.1.5 that seems to have caused a
regression here.  I'll try to provide a scratch kernel with that commit
reverted later today for testing.

Comment 11 Josh Boyer 2012-01-03 22:55:23 UTC
Please try kernel-3.1.7-1.fc16 which will be in the next f16-updates-testing push.

Comment 12 Dennis Appelon Nielsen 2012-01-04 20:51:44 UTC
The latest kernel-3.1.7-1.fc16 have solved my unsuspended problem.

Thanks Josh Boyer and anyone else there have helped me find the root of the sudden unsuspended problem :-)

I'll be sure to send it a tons of positive karma +1

Comment 13 David Kovalsky 2012-01-09 15:21:11 UTC
3.1.7 solved the issue for me, too.

Comment 14 Josh Boyer 2012-01-09 15:48:00 UTC
OK, thanks for the confirmations.


Note You need to log in before you can comment on or make changes to this bug.