<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Kworker using 100% CPU" href="https://bugs.freedesktop.org/show_bug.cgi?id=76732#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Kworker using 100% CPU" href="https://bugs.freedesktop.org/show_bug.cgi?id=76732">bug 76732</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>(In reply to <a href="show_bug.cgi?id=76732#c11">comment #11</a>) > Maybe now I can clarify a little bit. > > > If nouveau loads at boot, the problem is always there, even with > drm_kms_helper.poll=0. > > > If nouveau is blacklisted at boot i have two possible situations: > 1) > - i have gdm on the screen > - through ssh load drm_kms_helper with poll=0 > - load nouveau > - the screen goes black, or sometimes it displays some rubbish > - in dmesg whis appears: > [ 66.938644] pci_pm_runtime_suspend(): > nouveau_pmops_runtime_suspend+0x0/0xd0 [nouveau] returns -22 > - i press ctrl+alt+F1 and nothing happens but this appears in dmesg: > [ 175.868791] detected fb_set_par error, error code: -22 > -> CPU load is normal Yeah, nouveau suspends and is gone forever. You can disable runtime pm with nouveau.runpm=0. A fix for this should be in 3.14-final, I think. > > 2) > - switch to tty1 > - through ssh load drm_kms_helper with poll=0 > - load nouveau > - screen changes resolution and still works, also changing tty works > - CPU load at 100% > > > All the 3 situations are reproducible all the time In one of the cpu load at 100% situations, could you do a perf record -g -a (as root), and attach the resulting perf.data file after like 30s of runtime, along with your kallsyms (which should include nouveau and drm* symbols... grabbing /proc/kallsyms from a running kernel should work).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>