On Thu, Oct 31, 2013 at 9:14 PM, Paulo Zanoni <przanoni@xxxxxxxxx> wrote: > 2013/8/28 Daniel Vetter <daniel.vetter@xxxxxxxx>: >> We already have a big splashing *ERROR* for all the relevant cases of >> hangs, so this one here is redudant. And it results in an unclean >> dmesg when running with simulated hangs. Regression has been >> introduced in > > Bug https://bugs.freedesktop.org/show_bug.cgi?id=69747 has a case > where despite the messages, there's no splashing *ERROR* (except for > an unclaimed-register message which should be ignored in this specific > case since it can be fixed without fixing the GPU hang). As a > consequence, QA reported the bug mentioning just the "unclaimed > regsiter" message, not the real GPU hang, while the unclaimed register > is just a consequence of the real GPU hang. ZZ_check_dmesg wouldn't > catch this specific bug if we didn't have the unclaimed register > problem. If the same bug happens on IVB we'll never know because we > won't have the "unclaimed register" message to point it. This is just a testcase that uses a simulated gpu hang, so the hang message is tuned down from ERROR to the info level. So the only real bug is indeed the unclaimed register writes. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
