Description of problem: On my ThinkPad E440 after waking from suspend, computer restart. I can also notice on waking up fan start spinning faster and after aprox. 10 sec it restarts. It happens with kernel-4.9.13-201.fc25.x86_64 and three earlier versions. I have tried many things to check if it is some of my setting or apps that produce this bug. In the end I have reinstalled my system and let it update. Problem persisted. Then tried to reproduce this bug with starting Fedora kernel-4.8.6-300.fc25.x86_64. With it wake up normaly. p.s. This is my first bug reporting. :) Hope it is good enough. Version-Release number of selected component (if applicable): kernel-4.9.13-201.fc25.x86_64 How reproducible: With this kernel, problem is constant when resuming from suspend. Steps to Reproduce: 1. On resuming from suspend with kernel-4.9.13-201.fc25.x86_64 on Fedora 25, ThinkPad E440 2. 3. Actual results: It resume system, but then restart computer. Also faster fan spinning is noticeable. Expected results: Normal resume (without restart). Additional info: As I said I noticed that fan is spinning faster when this bug is going to occur while resuming.
Still present with these two additional kernels: - kernel-4.10.8-200.fc25.x86_64 - kernel-4.9.14-200.fc25.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 25 kernel bugs. Fedora 25 has now been rebased to 4.10.9-200.fc25. 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 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 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.