Description of problem: On my Dell Precision M3800 laptop, hibernate often wakes up with the following messages: Message from syslogd@machine name kernel:[38405.042543] do_IRQ: 0.81 No irq handler for vector (irq -1) Not sure about the numbers. Sometimes, the system is unresponsive at this point and needs a hard reboot. Version-Release number of selected component (if applicable): 3.16.3-200 (also had this issue with 3.16.2-20x. How reproducible: Not always, but quite frequently (at least half the wakeups). Steps to Reproduce: 1. hibernate using systemctl 2. resume (wakeup) 3. wakeup happens Actual results: and sometimes is unresponsive but often gives the error. Expected results: Should restore to status at which system was hibernated. Additional info: I have 12GB memory,16GB swap. Please feel free to ask for more information!
I wanted to mention that this last time I woke up from hibernate, I got the message: kernel:do_IRQ: 0.81 No irq handler for vector (irq -1) And there is thick band of flitting black red and blue speckled images aceorss the top lof the lower third of my screen. I can not seem to be able to get rid of this. Please let me know what additional information would be helpful to provide. Thanks again!
I also got the following: kernel:[43026.180173] do_IRQ: 0.81 No irq handler for vector (irq -1) Hibernating and waking up did not have an effect in the sense that these messages did not go away.
*********** 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 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. 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 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.