Description of problem: On my desktop, which has ethernet and wireless capability, the monitor (and maybe mouse and keyboard) won't wake up after hibernation if wireless has been disabled in bios and Network Manager setting for ethernet is "connect automatically". Version-Release number of selected component (if applicable): NetworkManager-0.9.6.4-3.fc17.x86_64 How reproducible: make sure ethernet connects automatically, wireless is disabled in bios. Hibernate, and try to wake system up. Steps to Reproduce: 1. In bios, disable wireless 2. boot up into fedora 17 with ethernet connecting automatically 3. hibernate, wait, wake up machine Actual results: black screen Expected results: normal screen--whatever was there before hibernation. Additional info: This happens on my desktop, which uses the e1000e driver for ethernet and the ath9k driver for wireless. It does not happen on my laptops, one of which has no capability to disable wireless in bios, and the other of which uses the atl1c ethernet driver and brcmsmac wireless driver. Hibernation succeeds when I don't have internet connectivity. It has also not failed when I have wireless connectivity. I wasn't sure which component to file this bug against, but since it does not occur when I don't have internet connectivity, I thought Network Management might be involved in this problem.
THis sounds more like a kernel issue; like the drivers panic on resume or something.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Bug still exists in Fedora 19. Kernel tested is 3.10.3-300.fc19.x86_64.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.11.1-200.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
The bug is still present with kernel 3.11.1-200.fc19.x86_64.
This bug seems to have expanded a bit. Even when wireless is enabled in bios, the monitor does not always wake up after hibernation. The current situation seems to be that the bug shows up consistently when wireless is disabled in bios, and shows up a lot of the time, but not all the time, when wireless is enabled in bios.
Greta: Can you upload a dmesg log of this time period?
Created attachment 801947 [details] output from dmesg command before hibernation I wanted to provide output from dmesg before and after hibernation. Since the monitor/keyboard aren't active after hibernation, I decided to add a root cron job. Every five minutes it would look for dmesg.new, and if not present, create it by running dmesg. Unfortunately, after hibernation, the file was not created. So, it seems that more than just the monitor has failed to start after hibernation. The attached dmesg file was created before hibernation.
You should be able to get /var/log/messages, as root. That should have it, I hope!
Created attachment 801983 [details] /var/log/messages from time of disabling wifi in boot until reboot after failed hibernation Timeline: prior to 18:17, shutdown the system. 18:17 booted up again, entering bios to disable wifi, and then continued booting. 18:19 after having signed in as a normal user, started hibernation. 18:20 hit the power button to resume from hibernation. resume from hibernation failed. 18:21 held down the power button until the machine powered off. 18:22 powered on the machine, ..., signed in as normal user. The portion of /var/log/messages provided covers the timeline.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.12.6-200.fc19. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20. If you experience different issues, please open a new bug report for those.
Three times hibernation has succeeded using kernel 3.12.6-200.fc19.x86_64, with wifi disabled in bios and ethernet connected automatically. So, it seems that this bug no longer occurs in this configuration.
Hi Greta, ok to close this one then? Thanks, Michele
Yes, as far as I'm concerned it is fine to close.
Hi Greta, thanks for the feedback. I am closing this one then regards, Michele