Hide Forgot
Created attachment 1218951 [details] /var/log/messages Description of problem: After updating two systems with dnf, both systems became unusable after reboot. The problem is caused by kernel 4.8.6-201.fc24.x86_64. Kernel 4.7.9-200.fc24.x86_64 runs fine. Both systems are vmware guests. Version-Release number of selected component (if applicable): Kernel 4.8.6-201.fc24.x86_64 How reproducible: Start Fedora 24 with kernel 4.8.6-201.fc24.x86_64 under VMWare. Steps to Reproduce: 1. Install latest kernel (4.8.6-201.fc24.x86_64) 2. Reboot 3. Try to login and to use the system Actual results: Both systems are unusable. One system doesn't allow to login or even restart by using "keyboard hotkeys", the other still allows to login (even with ssh), but it's unusable, too. For example, after executing "sudo su -" the terminal hangs. Expected results: The systems should run fine as with kernel 4.7.9-200.fc24.x86_64 and before. Additional info:
Both systems are running under ESXi 5.1.0.
Status?
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are 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 24 kernel bugs. Fedora 25 has now been rebased to 4.10.9-100.fc24. 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.
After the mass bug update we have tested kernel 4.10.13 and 4.10.14 on the two different systems mentioned above. The issue has been resolved. Thanks a lot.