<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Everything using GPU gets stuck after running+killing parallel Media loads (after running 3D benchmarks)" href="https://bugs.freedesktop.org/show_bug.cgi?id=110848#c32">Comment # 32</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Everything using GPU gets stuck after running+killing parallel Media loads (after running 3D benchmarks)" href="https://bugs.freedesktop.org/show_bug.cgi?id=110848">bug 110848</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to David Weinehall from <a href="show_bug.cgi?id=110848#c31">comment #31</a>) > Hmmm, so you're saying that given enough time the machine could/should > recover? > > I left the machine on 4h after the test concluded (hung), but no luck. The > desktop clock of the machine stopped updating at the end of the task, the > machine stopped replying to ping, and when I checked 4h later the machine > still didn't respond to keyboard input. There are a few corner cases where oom just eats itself, but nowadays they usually result in a panic + reboot. (Do you have reboot on panic set?) Give or take a few HW faults, a lockup usually means a panic. I would personally use remote logging (via netconsole) in case it is a panic. If not, and with lockdep and kernel NMI watchdog running, it just quietly hangs, we found ourselves a more "interesting" issue.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>