Description of problem: Kernel 3.13.8 is making my system run at over 97C. System load is 10. Eventually system becomes unusable. Version-Release number of selected component (if applicable): Fedora 20 KDE Spin Kernel-3.13.8 How reproducible: Always Steps to Reproduce: 1.Boot into a system running kernel-3.13.8 Actual results: Temperature 97C without any specific program running. Load is 10. Constant soft lock. Expected results: Additional info: System is Thinkpad T420s.
Created attachment 884381 [details] journalctl -b result journalctl -b log after a hard reset.
kernel-3.13.8 and onwards (including kernel-3.13.9) have rendered system unbootable. I am attaching a log after a hard reboot i had to do after kernel-3.13.9 upgrade.
Created attachment 884572 [details] journalctl -b after kernel-3.13.9
To add some details, I'm seeing the same issue on a laptop of my relative. Older 3.11 kernel does not freeze. I'm using XFCE so it is not KDE specific. And it freezes just after I enter login details. Any idea? Could this forum post about PPA be relevant? http://ubuntuforums.org/showthread.php?t=2198375&page=5&p=12897760#post12897760 Any worksarounds you could recommend? How to easily switch to VESA or othe compatible driver?
FYI same issue described also in: http://forums.fedoraforum.org/showthread.php?t=298468 https://lists.fedoraproject.org/pipermail/kde/2014-April/013461.html The system I observe this is an asus laptop, will provide more details when I can because laptop is not mine. It's working fine under windows and older kernel so I would rule out broken hardware. Please advise about possible workarounds and best way to debug.
@Aleksandar Kostadinov When you boot into runlevel 3 do you see the flood of nouveau errors like in this screenshot. http://i.imgur.com/qET8Zxr.jpg To boot into run level 3 use ln -sf /lib/systemd/system/multi-user.target /etc/systemd/system/default.target And to boot back to run level 5 use ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target Source:- http://forums.fedoraforum.org/showpost.php?p=1695620&postcount=10 And why do you think it is a nvclock problem. Shouldn't it be a xorg-x11-drv-nouveau problem? I don't even have nvclock installed.
I have been successfully able to boot into 3.13.10 after omitting Nouveau. sudo mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nouveau.img sudo dracut --omit-drivers nouveau /boot/initramfs-$(uname -r).img $(uname -r) It complained about Nvidia.ko file not present but then I reinstalled bumblebee-nvidia from RPMFusion and rerun those commands I can run the system just fine.
Sudhir, sorry for component change, I intended to leave it as you filed it originally. Now reverting it back. Will try multi-user when I can. Thanks!
*********** 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.14.4-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 experience different issues, please open a new bug report for those.
Yes, the bug exist on following kernel. Linux 3.14.4-200.fc20.x86_64 #1 SMP Tue May 13 13:51:08 UTC 2014 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 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.
F21 Beta is out I am no longer running F20. I won't be able to provide any more info about this bug.