Summary: | Hangs with chromium using CVS as of 20040531 | ||
---|---|---|---|
Product: | Mesa | Reporter: | Eric Anholt <eta> |
Component: | Drivers/DRI/r200 | Assignee: | Eric Anholt <eric> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | high | ||
Version: | git | ||
Hardware: | x86 (IA32) | ||
OS: | FreeBSD | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 351, 1065, 1066 |
Description
Eric Anholt
2004-06-20 15:08:32 UTC
multiple GL apps are currently busted on R200. check the dri-devel archives for Roland's thread about this. render probably triggers this as well since it uses the 3d engine. Take this bug as mine, since I've been looking at it. It's a major issue, which anecdotes say sprouted between XFree86 4.3.0 and X.Org 6.7.0. Mark it as a blocker. Keith and I spent tonight debugging this issue. The problem is that we need to make EmitState+LOAD_VBPTR+DRAW_VBUF sets atomic (and other EmitState+something setes, as well, most likely) in terms of not dropping the lock in the middle due to full buffers. We've implemented kludges that have dealt with the problem (testing with ipers) and a more elegant solution will come soon. A fix has been committed to Mesa CVS which fixes the hangs and rendering glitches on R200 with multiple clients (which included Render acceleration) and on rendering glitches on R100 with multiple clients. This should be merged for 6.8.0. (In reply to comment #4) > A fix has been committed to Mesa CVS which fixes the hangs and rendering > glitches on R200 with multiple clients (which included Render acceleration) and > on rendering glitches on R100 with multiple clients. This should be merged for > 6.8.0. This issue was discussed on the release wranglers call this morning and was on the blocker list prior to the code freeze. Please go ahead and merge the changes from Mesa CVS. Changes have been pushed in to X.Org CVS. Mass version move, cvs -> git |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.