Description of problem: Fresh install of Mageia 3, some time after the system start the KDE desktop becomes unresponsive and freezes for a quite long time with short periods when the responsiveness is somewhat back. Command top showed very high cpu load for processes "migration/x" (where x is a number). This applies when booted with the kernel-server-3.8.13-1.mga3 (I have 4 GB RAM) that was installed by default. I tried also the kernel-tmb-laptop-3.8.13-1.mga3 - then the process "kworker/u:x" is causing the very high cpu load, but the desktop does not freeze completely. Hardware: Lenovo Thinkpad X200 (http://www.thinkwiki.org/wiki/Category:X200), with mainly Intel components. Version-Release number of selected component (if applicable):kernel-server-3.8.13-1.mga3; kernel-tmb-laptop-3.8.13-1.mga3 How reproducible: After every system start Steps to Reproduce: 1. Start or reboot Mageia 3 2. Wait or use the system for some time 3. Watch the output of "top" command (at the moments, when the screen is not frozen) Reproducible: Steps to Reproduce:
isn't akonadi or something like that running ?
Component: Release (media or process) => RPM Packages
No. As I use Thunderbird, I removed as much kdepim as possible including akonadi, nepomuk etc...
Can you try with x86_64?
CC: (none) => sander.lepikAssignee: bugsquad => tmb
I guess the reason is described here: http://souriguha.wordpress.com/2011/03/08/how-to-solve-problem-with-thinkpadkslowd-kworker-on-linux-kernel-2-35-2-36/ In Mageia 2 I booted with the kernel parameter drm_kms_helper.poll=N, but in Mageia 3 it did not help any more - probably due to the reason described in the above webpage...
Looks like the fix was included in kernel 3.10: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b543fb0464ddf30a5b554957fd212eb7a2acac65 Some details on the fix in 3.10, quoting Intels Daniel Vetter: âOnce we detect a storm we kill the hotplug interrupt. Note that since on many systems these storms only happen in certain conditions (e.g. specific battery charger state) weâll re-enable the interrupts every 2 minutes to check whether the storm has passedâ. Any chance to get the fix backported to Mageia 3 kernel?
As the situation got untolerable (had to do some presentations at workshop and no way to wait until the desktop gets resposive again) and before downgrade to Mageia 2 decided to test the 3.10 kernel from Cauldron. Tried kernel 3.10.9-tmb-laptop-1.mga4 (with cauldron's kernel-firmware as dependency) and can report, that the problem is gone. The processes kworker/uX:X could go up to some tens of % of CPU use, but are killed thereafter and the system is all time responsive... Shouldn't this bug being listed in Mageia 3 release errata?
Well, mga3 will be updated to use kernel-3.10 series soon
Switched to kernel-tmb-laptop-3.10.15-1.mga3 (and kernel-firmware-20130624-1.mga3) which are currently at Mageia 3 core/updates/testing. On the basis of testing so far (several hours) I can report that the bug 10490 seems to be fixed also in Mageia 3 kernel.
As Mageia 3 switched to kernel 3.10 series (and my laptop is running Mageia 4 already), should we change this bug status to fixed...
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD