<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HAWAII] Get acceleration working" href="https://bugs.freedesktop.org/show_bug.cgi?id=78453#c43">Comment # 43</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HAWAII] Get acceleration working" href="https://bugs.freedesktop.org/show_bug.cgi?id=78453">bug 78453</a> from <a class="email" href="mailto:deathsimple@vodafone.de" title="Christian König <deathsimple@vodafone.de>"> Christian König</a> <pre>The hang caused by eglinfo is probably just because we try to clear a buffer on init using hw accel or something like this. Here are a couple of tips how to further narrow it down: 1. Don't work on the system you are trying to debug. Use another system and access the box with the hardware over the network or even better with a serial cable. 2. Add radeon.lockup_timeout=0 to the kernel commandline. This will disable recovery after the first lockup. It doesn't make sense to try to debug all lockups at the same time, we probably got more than one problem to solve. 3. After the system crashed take a look at the debugfs files under /sys/kernel/debug/dri/0/, especially radeon_fence_info. If you lockup the GPU does this always happen at the same command submitted? E.g. if you try twice do you always get the same fence value? Or is this random?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>