Description of problem: After installing kernel-3.1.5-1 x86_64 I'm no longer able to unsuspended my laptop Lenovo W520 (Using a SSD OCZ Vertex 3). The problem is still in kernel-3.1.5-2 x86_64 also Version-Release number of selected component (if applicable): kernel-3.1.5-2.fc16.x86_64 kernel-3.1.5-1.fc16.x86_64 How reproducible: Install on of the to versions of the kernel above, and you are no longer able to unsuspended your system, and have to hit the power off switch to gain acces to you system. Steps to Reproduce: 1.Update kernel to kernel-3.1.5-1.fc16.x86_64 or kernel-3.1.5-2.fc16.x86_64 2.reboot in to it 3.try to suspend and then unsuspended Actual results: The system keeps being in suspended mode Expected results: The system should come back to life without any problems Additional info:
Can you try some of the steps listed here: https://fedoraproject.org/wiki/KernelCommonProblems#Suspend.2FResume_failure
(In reply to comment #0) > Description of problem: > After installing kernel-3.1.5-1 x86_64 I'm no longer able to unsuspended my > laptop Lenovo W520 (Using a SSD OCZ Vertex 3). The problem is still in > kernel-3.1.5-2 x86_64 also say to me one kernel that works, kernel-3.1.4-1 works ? what is yours graphics chiptset ? what is the output of ? cat /var/log/Xorg.0.log| grep -i chip
Hi Sergio Monteiro BAsto It works fine with kernel-3.1.4-1 My graphic chipset is nVidia Corporation GT216 [Quadro FX 880M] Here is the entire output from my /var/log/Xorg.0.log | http://fpaste.org/Fnb0/ Here is a output of all my Xorg.* log files,
(In reply to comment #3) > Hi Sergio Monteiro BAsto > > It works fine with kernel-3.1.4-1 > My graphic chipset is nVidia Corporation GT216 [Quadro FX 880M] > > Here is the entire output from my /var/log/Xorg.0.log | http://fpaste.org/Fnb0/ > Here is a output of all my Xorg.* log files, Sorry I forgot the link with all my Xorg.*.log output http://fpaste.org/KOTR/
Id recommend including logs here as attachments, and not rely on fpaste (whose content eventually expires)
You're using the proprietary nvidia module. Your logs show that the xorg nvidia module failed to load at some point (there are no date timestamps so we have no idea when), and then nouveau loads but you've blacklisted the kernel driver. What happens if you don't use the nvidia module and don't blacklist nouveau? If you can provide the dmesg and xorg logs from a boot setup like that, please attach.
Created attachment 546287 [details] THis is the log output fromm all my Xorg logs
(In reply to comment #7) > Created attachment 546287 [details] > THis is the log output fromm all my Xorg logs Sorry... I have now attached it... Just a short follow up... the unsuspended freeze the system, I am not able to make my caps lock flash when I try to unsuspended..
(In reply to comment #6) > You're using the proprietary nvidia module. Your logs show that the xorg > nvidia module failed to load at some point (there are no date timestamps so we > have no idea when), and then nouveau loads but you've blacklisted the kernel > driver. > > What happens if you don't use the nvidia module and don't blacklist nouveau? > If you can provide the dmesg and xorg logs from a boot setup like that, please > attach. Yes I use the proprietary nVidia drivers from rpmfusion. I'll try to remove them when I get home from work, and then update this bug rapport...
(In reply to comment #9) > Yes I use the proprietary nVidia drivers from rpmfusion. if you are using rpmfusion for nvidia drives , you should install akmods to rebuild nvidia-kmods, but this don't have nothing to do with this kernel update, in my perspective .
Created attachment 546292 [details] My Xorg all log files without rpmfusion's drivers
(In reply to comment #11) > Created attachment 546292 [details] > My Xorg all log files without rpmfusion's drivers The problem persist without the nVidia drivers
I have to point out, that this error also could have something to do with changes to btrfs in kernel-3.1.5.1, sense I'm running btrfs on all my partitions, this also could cause the problem with unsuspended
Any updates regarding my unsuspended issue ? I still have this problem every time I boot any of these 2 new kernel's: kernel-3.1.5-2.fc16.x86_64 kernel-3.1.5-1.fc16.x86_64 But I don't have the problem in kernel-3.1.4-1.fc16.x86_64 Do I have to expect this issue for any further kernel releases or what ?
(In reply to comment #14) > Any updates regarding my unsuspended issue ? > I still have this problem every time I boot any of these 2 new kernel's: > > kernel-3.1.5-2.fc16.x86_64 > kernel-3.1.5-1.fc16.x86_64 > > But I don't have the problem in kernel-3.1.4-1.fc16.x86_64 > > Do I have to expect this issue for any further kernel releases or what ? Did you try any of the steps on the wiki page in comment #1? With the information this bug has so far, it's fairly hard to narrow down what might be causing the problem. If you can isolate it to a particular driver/device, progress might be made.
(In reply to comment #13) > I have to point out, that this error also could have something to do with > changes to btrfs in kernel-3.1.5.1, sense I'm running btrfs on all my > partitions, this also could cause the problem with unsuspended could be interesting, bisect the patch /pub/linux/kernel/v3.0/incr/patch-3.1.4-5.bz2, and find out what commit break it yours suspend , because is a regression. and upstream the bug .
Created attachment 547941 [details] Last hour where I have shuffled around with pm-suspend Attached is my message log file, for the last hour where I have tried to figure what driver is causing this problem.... Please take a look and see if there is anything to notes
Created attachment 547942 [details] my dmesg out Attached is my dmesg output. please take a look an see if anything can put light on my unsuspended problem...
Created attachment 547943 [details] My pm-suspend output This is my pm-suspend.log file please take a look and see if it helps in any way
I just tried to init 3 and then suspend from there with pm-suspend and I see the same error. I kind of hear mu fan spin and my second ordinary disk spin, but then the laptop just keeps blinking like it was suspended.
(In reply to comment #16) > (In reply to comment #13) > > I have to point out, that this error also could have something to do with > > changes to btrfs in kernel-3.1.5.1, sense I'm running btrfs on all my > > partitions, this also could cause the problem with unsuspended > > could be interesting, bisect the patch > /pub/linux/kernel/v3.0/incr/patch-3.1.4-5.bz2, and find out what commit break > it yours suspend , > because is a regression. and upstream the bug . Yes, but how do I do this in piratical?
Well I have this other Fedora 16 system beside my main system, and I just tried to update it to kernel-3.1.5-2.fc16.x86_64 This system also runs btrfs in all partitions beside /boot and it don't have the problem with unsuspended. So I guess we can leave out my suggestion that it is the btrfs changes. Besides from being a much newer laptop then this spare Lenovo T61P there is not that much differenced between them, beside from the OCZ Vertex 3 SSD I have in my main laptop along side with a bay mounted WD 350 7200RPM disk. If it is the SSD causing this problems from the 3 latest kernel's kernel-3.1.5.1 kernel-3.1.5.2 now running kernel-3.1.5.6 and not in the old kernel-3.1.4-1 where shall I look for an error log entry?
Just some info about my SSD [nielsenda@laptop linux64]$ sudo ./fwupd -log /dev/sda fwupd v2.12.05: update drive firmware /dev/sda: Model Number : OCZ-VERTEX3 Serial Number : OCZ-6SZUK312CSK69SMB Firmware Revision: 2.15 Accessing firmware file... Firmware does not need to be updated It is running the latest firmware
I just found this fellow here having the same issue as me https://bugzilla.redhat.com/show_bug.cgi?id=767416
Any useful stuff in the log files I attached yesterday?
I've the same issue with proprietary NVIDIA driver (xorg-x11-drv-nvidia-1:290.10-1.fc16) + kmod. Graphics Processor: GeForce GTS 240 --- # dmesg | grep "hash matches" [ 1.446920] hash matches drivers/base/power/main.c:509 [ 1.446931] block loop5: hash matches [ 1.446947] pci 0000:01:00.0: hash matches /sys/bus/pci/drivers/nvidia/0000:01:00.0
(In reply to comment #26) > I've the same issue with proprietary NVIDIA driver > (xorg-x11-drv-nvidia-1:290.10-1.fc16) + kmod. > Graphics Processor: GeForce GTS 240 > --- > # dmesg | grep "hash matches" > [ 1.446920] hash matches drivers/base/power/main.c:509 > [ 1.446931] block loop5: hash matches > [ 1.446947] pci 0000:01:00.0: hash matches > > /sys/bus/pci/drivers/nvidia/0000:01:00.0 Hi Roman Spirgi Thanks for the input, but I even tried to remove any kmod-nvidia drivers and the problem persisted
Does booting with pci=nocrs fix the problem?
The Problem persist in latest kernel release 3.1.6-1.fc16.x86_64
I have the same issue with W510 and now kernel 3.1.6-1.fc16.x86_64 (resume not possible, blinking power button, no capslock light), but `dmesg | grep "hash matches"` is empty in my case after a reboot (after `echo 1 > /sys/power/pm_trace` before the suspend). I just tried booting with pci=nocrs, this changed nothing for me, still the same issue. I'll also attach my pm-suspend.log and Xorg.*.logs.
Created attachment 549623 [details] martin.grotzke pm-suspend.log
Created attachment 549624 [details] martin.grotzke Xorg.*.logs (zipped)
Try booting your kernel with hpet=disable it took care of the problem for me. But I don't know what hpet is I'll have to Google for a answer.
I hope people are following http://lkml.org/lkml/2011/12/29/45 Disabling hpet should make it work. I think by default on most modern CPUs, TSC is used anyway. So, explicitly disabling HPET and forcing it to use TSC from the get go is not a bad workaround!
hpet=disable works for me, great!
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.
3.1.7 has been released and it contains the revert i previously mentioned. I'll get a kernel built for testing shortly.
kernel-3.1.7-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/kernel-3.1.7-1.fc16
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
Package kernel-3.1.7-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.1.7-1.fc16' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0145/kernel-3.1.7-1.fc16 then log in and leave karma (feedback).
(In reply to comment #40) > Package kernel-3.1.7-1.fc16: > * should fix your issue, > * was pushed to the Fedora 16 testing repository, > * should be available at your local mirror within two days. > Update it with: > # su -c 'yum update --enablerepo=updates-testing kernel-3.1.7-1.fc16' > as soon as you are able to, then reboot. > Please go to the following url: > https://admin.fedoraproject.org/updates/FEDORA-2012-0145/kernel-3.1.7-1.fc16 > then log in and leave karma (feedback). Well already done that... thanks again, I snatched it before it hit test repo's and Added my Proven tester karma +1 Thanks again...
kernel-3.1.7-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
Running kernel-3.2.3-2.fc16 and I am still getting black screen after suspend. [root@localhost ~]# dmesg | grep "hash matches" [ 1.904344] hash matches drivers/base/power/main.c:576