Description of problem: A similar problem: https://bugs.gentoo.org/show_bug.cgi?id=394487 lspci: 00:00.0 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a3) 00:01.0 ISA bridge: nVidia Corporation MCP65 LPC Bridge (rev a3) 00:01.1 SMBus: nVidia Corporation MCP65 SMBus (rev a1) 00:01.2 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a1) 00:02.0 USB controller: nVidia Corporation MCP65 USB Controller (rev a3) 00:02.1 USB controller: nVidia Corporation MCP65 USB Controller (rev a3) 00:06.0 Ethernet controller: nVidia Corporation MCP65 Ethernet (rev a3) 00:07.0 Audio device: nVidia Corporation MCP65 High Definition Audio (rev a1) 00:08.0 PCI bridge: nVidia Corporation MCP65 PCI bridge (rev a1) 00:09.0 IDE interface: nVidia Corporation MCP65 IDE (rev a1) 00:0a.0 IDE interface: nVidia Corporation MCP65 SATA Controller (rev a3) 00:0d.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) 02:00.0 VGA compatible controller: nVidia Corporation G73 [GeForce 7300 GT] (rev a1) CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ cpufreq-info: analyzing CPU 0: driver: powernow-k8 CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 0 1 maximum transition latency: 109 us. hardware limits: 1000 MHz - 2.30 GHz available frequency steps: 2.30 GHz, 2.20 GHz, 2.00 GHz, 1.80 GHz, 1000 MHz available cpufreq governors: ondemand, conservative, powersave, userspace, performance current policy: frequency should be within 1000 MHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 2.30 GHz. analyzing CPU 1: driver: powernow-k8 CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 0 1 maximum transition latency: 109 us. hardware limits: 1000 MHz - 2.30 GHz available frequency steps: 2.30 GHz, 2.20 GHz, 2.00 GHz, 1.80 GHz, 1000 MHz available cpufreq governors: ondemand, conservative, powersave, userspace, performance current policy: frequency should be within 1000 MHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 2.30 GHz. How reproducible: Always Steps to Reproduce: 1. Boot normally Mga2 x86_64 with kernel 3.3.6 (the same problem is on kernel 3.3.8- updates testing) 2. Run top or htop: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND ... 6 root RT 0 0 0 0 S 0 0.0 0:00.00 migration/0 7 root RT 0 0 0 0 S 0 0.0 0:00.00 migration/1 ... 2. Wait 2-3 hour 3. Run top or htop: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND ... root 6 68.9 0.0 0 0 ? S 21:59 26:08 [migration/0] root 7 0.0 0.0 0 0 ? S 21:59 0:00 [migration/1] ... There are mouse freezing and help only hard reset. It wasn't the problem on Mageia 1.
Hi Marcin, Thanks for your report. Sorry that we didn't reply to it before, we are short on active bugsquad members. :-( Mageia is made by volunteers, if you're interested in participating (it is mostly great fun :-) ), then have a look here: https://wiki.mageia.org/en/Contributing Do you still have this problem in current Mageia 2 and/or 3 and/or cauldron ? I'll cc the kernel maintainer, so he'll see it when you reply here.
Keywords: (none) => NEEDINFOCC: (none) => marja11, tmb
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 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