Created attachment 452643 [details] lspci output Description of problem: After closing the lid of my laptop, suspend seems to work fine. System powers down, orange 'suspended' LED light is on. When pressing the power button to resume the laptop, the system does not resume, but does a cold boots. I hope it is correct to file this bug against the kernel. Version-Release number of selected component (if applicable): kernel-2.6.35.6-39.fc14.x86_64 How reproducible: Happens always. Steps to Reproduce: 1. shut lid to suspend 2. press 'power' to resume Actual results: cold boot Expected results: resume previous state
Created attachment 452647 [details] /var/log/messages at suspend; show cold boot directly after
After a little poking around, it turns out that this is a generic bug in 2.6.35 as it is also discussed on (at least) the Ubuntu[1] and Arch Linux [2] forums as well. The original upstream bugzilla entry for it is here [3]. Comments #82 through #84 on that bugreport mention a patch for 2.6.36 to blacklist systems that need acpi_sleep=nonvs in acpisleep_dmi_table[]. As I am not a kernel developer, I have no idea whatsoever what the amount of work to do this would be but: would it be possible to incorporate this patch into 2.6.35 for F14? Not having a working suspend option kinda sucks... [1] http://ubuntuforums.org/showpost.php?p=9934814&postcount=42 [2] https://bbs.archlinux.org/viewtopic.php?id=80702 [3] https://bugzilla.kernel.org/show_bug.cgi?id=16396
what laptop is this ? Can you attach the output of dmidecode please ?
Created attachment 528615 [details] Output of dmidecode dmidecode output attached
thanks. I just added a patch for the next build. I've also posted it upstream, so it should get into future releases.
Thanks! What Fedora release did you patch for? I am still having this problem in the F16 betas, so I'd love to see the patch in there, too.
I added the patch to all branches. Should start showing up everywhere soon.
kernel-2.6.35.14-100.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/kernel-2.6.35.14-100.fc14
Package kernel-2.6.35.14-100.fc14: * should fix your issue, * was pushed to the Fedora 14 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-2.6.35.14-100.fc14' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-14747 then log in and leave karma (feedback).
kernel-2.6.40.7-3.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/kernel-2.6.40.7-3.fc15
kernel-2.6.40.8-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/kernel-2.6.40.8-2.fc15
Created attachment 530575 [details] dmidecode from Sony VPCEB17FX Same problem occurs with Sony VPCEB17FX.
kernel-2.6.35.14-100.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
So since this still happens with the Sony VPCEB17FX, should I reopen this bug, or start a new one?
just sent a patch to fix that one upstream. I'll add it to all the fedora trees too. Don't worry about opening another bug. thanks for the debug info.
kernel-2.6.40.8-4.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/kernel-2.6.40.8-4.fc15
kernel-2.6.41.1-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/kernel-2.6.41.1-1.fc15
kernel-2.6.41.1-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
kernel-2.6.35.14-105.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/kernel-2.6.35.14-105.fc14
kernel-2.6.35.14-106.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/kernel-2.6.35.14-106.fc14
kernel-2.6.35.14-106.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.