<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [NV43] hangs with direct rendering since 3.7 rework" href="https://bugs.freedesktop.org/show_bug.cgi?id=58615#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [NV43] hangs with direct rendering since 3.7 rework" href="https://bugs.freedesktop.org/show_bug.cgi?id=58615">bug 58615</a> from <a class="email" href="mailto:randrik@mail.ru" title="Andrew Randrianasulu <randrik@mail.ru>"> Andrew Randrianasulu</a> <pre>I seems I can avoid (workaround) this bug by simply changing in my .config CONFIG_PREEMPT_NONE=y to CONFIG_PREEMPT_VOLUNTARY=y . I made this discovery while trying official Slackware kernel from Slackware-current. May be this bug has something in common with bug described in <a href="https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.3">https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.3</a> as "mm, vmscan: prevent kswapd livelock due to pfmemalloc-throttled process being killed' . Bug seems to hit only nv40 (and less?) codepath, because my nv50 works fine without preemption. Should I leave this bugreport open, or resolve it as WORKSFORME? (currently I'm compiling additional test kernel based on nouveau/linux-2.6 linux-3.19 branch , just to test my workaround one more time.) Reclocking still seems to work only partially (lost display and another kind of hang after just few seconds of glxgears on highest perf level, lost display after I switch clocks back to lower frequencies), but this is another issue</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>