https://bugs.freedesktop.org/show_bug.cgi?id=29020 --- Comment #3 from Pavel Ondračka <drakkk@xxxxxxxxxx> 2010-07-12 16:51:05 PDT --- Created an attachment (id=36975) --> (https://bugs.freedesktop.org/attachment.cgi?id=36975) make test output with mesa 0864851e2763291ff1ea2ceaa3c6f16b14abd362 (In reply to comment #1) > Does it help if you go before the commit > 78e8a8765f435bf0902d62afbcb3b8d68a0b716f? Hm, it helps a little bit... With mesa 0864851e2763291ff1ea2ceaa3c6f16b14abd362 it doesn't hardlock, just X is frozen. This is probably different test which is failing now. Not sure if it fails earlier or later, but when it freezes the test picture is different that when it hardlocks. dmesg is full of: [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB ! [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(0). [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB ! [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(1). ... repeating with numbers from 0 to 15. Attaching whole terminal output, there are many failed tests, probably many other problems, some of them may be a wine issue, but they should just fail not take system or X down with them... (In reply to comment #2) > I've committed some fixes, is it any better now? No -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
