Bug 60224 - Radeon hd6770 graphics artifacts in team fortress 2 with 3.8 kernel
Summary: Radeon hd6770 graphics artifacts in team fortress 2 with 3.8 kernel
Status: RESOLVED DUPLICATE of bug 58042
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
Depends on:
Reported: 2013-02-03 12:06 UTC by Iaroslav Andrusyak
Modified: 2013-02-13 17:56 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

tf2 (79.57 KB, image/jpeg)
2013-02-03 12:06 UTC, Iaroslav Andrusyak
no flags Details
Test to check if it's async dma (1.07 KB, patch)
2013-02-13 16:42 UTC, Jerome Glisse
no flags Details | Splinter Review

Description Iaroslav Andrusyak 2013-02-03 12:06:01 UTC
Created attachment 74130 [details]

mesa, libdrm, ddx from git
1:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Juniper XT [AMD Radeon HD 6000 Series]

With kernel <3.8 all looks fine.
Comment 1 Michel Dänzer 2013-02-04 10:23:16 UTC
Could be related to bug 60236. If that's not it, can you bisect which kernel change introduced the problem?
Comment 2 Iaroslav Andrusyak 2013-02-04 12:23:45 UTC
I know that the problem appeared after upgrading to 3.8-rc1-drm-next, and continues to exist in the 3.8-rc5-vanilla.
async dma is a likely cause.
Comment 3 Jerome Glisse 2013-02-13 16:42:04 UTC
Created attachment 74766 [details] [review]
Test to check if it's async dma

Please test with this mesa patch (either against mesa 9.1git or mesa master git).

If it fix the issue then please test making sure you a have kernel with this kernel patch :

Comment 4 Jerome Glisse 2013-02-13 16:42:55 UTC
Test kernel without the mesa patch.
Comment 5 Laurent carlier 2013-02-13 17:55:47 UTC
reverting 1eedebc65b02130ef7a27062a1ed67972a317a08 fixed the issue
Comment 6 Laurent carlier 2013-02-13 17:56:55 UTC

*** This bug has been marked as a duplicate of bug 58042 ***

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.