Red Hat Bugzilla – Bug 1020068
100% CPU usage after suspend
Last modified: 2014-02-11 09:39:11 EST
Description of problem: I have an Asus X201E with Fedora 19 and Cinnamon. After suspending the computer, NetworkManager sucessfully reconnects to the network, but CPU usage keeps at 100% until I reboot, rendering the computer unusable. Version-Release number of selected component (if applicable): kernel 3.11.4-201.fc19 NetworkManager 1:0.9.8.2-9.git20130709.fc19 How reproducible: always Steps to Reproduce: 1.Suspend 2.Resume Actual results: The CPU usage shoots up to 100% Expected results: Back to idle Additional info:
Is it really NetworkManager process that eats the CPU? You can run 'top' to see the processes. If it is NetworkManager and the computer is responding (a bit at least), could you attach to the running NetworkManager to get backtrace? $ sudo gdb -p <PID of NM> ... then inside gdb (gdb) t a a bt
I assumed it was NetworkManager because it happened at the same time the network connections pops up. The process using the 100% CPU is actually kworker/0:1 I tried to get a backtrace by that method and but it doesn't work ptrace: Operation not permitted I tried with an older kernel kernel 3.9.5-301.fc19 and the problem goes away. That was the only kernel I found with yum, how can I get a more recent one?
I just tested my other PC with kernel 3.11.4-201.fc19 and it has no problem suspending. It has mostly the same software, but it's a Toshiba Qosmio F60.
After some more testing I'm pretty sure NetworkManager is originating this problem. I had network connections in range, suspended the PC and when resumed NetworkManager still notified about disconnecting from the network.
I can confirm the problem persists in the new kernel 3.11.6-200.fc19.i686 It's definitively on NetworkManager
Can we get some journal logs showing NetworkManager output from a bit before this problem occurs?
Created attachment 828274 [details] Result fo journalctl around the bug Sorry for taking so long, only got around checking this. I appended the result of $ journalctl -f > journal.log I started before I lowered the screen and kept for about a minute.
The latest NetworkManager version (0.9.8.8) fixed this for me. I can now suspend my PC. Thanks, whoever fixed it.
(In reply to Simão Afonso from comment #8) > The latest NetworkManager version (0.9.8.8) fixed this for me. I can now > suspend my PC. Thanks, whoever fixed it. Closing per the last comment. Feel free to re-open should the problem occur again.