Bug 16346 - Commit: "radeon: r345xx fixe hard lockup" causes massive screen corruption.
Summary: Commit: "radeon: r345xx fixe hard lockup" causes massive screen corruption.
Status: RESOLVED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/other (show other bugs)
Version: unspecified
Hardware: Other All
: medium major
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
: 16348 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-06-13 14:48 UTC by Lukasz Krotowski
Modified: 2008-06-15 11:30 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Corrupted gitk. (112.51 KB, image/png)
2008-06-13 14:48 UTC, Lukasz Krotowski
no flags Details
xorg.conf (1.82 KB, text/plain)
2008-06-15 10:43 UTC, Lukasz Krotowski
no flags Details

Description Lukasz Krotowski 2008-06-13 14:48:22 UTC
Created attachment 17107 [details]
Corrupted gitk.

With commit: 1aafbb83d97ccc78b78d5cbd311f1239a3dad11e every non-text-based app is corrupted (see attached screenshot). Reverting that commit solves problem. Card is RV410 Radeon X700 AGP (one of those with AGP-PCIE bridge).
Comment 1 Tormod Volden 2008-06-14 03:24:59 UTC
FWIW, I see this in text-based applications (gnome-terminal, pidgin) as well, on my X700 Mobility PCIE.
Comment 2 Michel Dänzer 2008-06-14 15:08:09 UTC
*** Bug 16348 has been marked as a duplicate of this bug. ***
Comment 3 Jerome Glisse 2008-06-15 09:52:26 UTC
commit 9dd58d6568702358bfb3d6d1b6459092cf77ae91 should fix this
Comment 4 Lukasz Krotowski 2008-06-15 10:25:59 UTC
Nope, screen is still corrupted with that commit.
Comment 5 Jerome Glisse 2008-06-15 10:32:55 UTC
commit 6f8cc957034a887a9cbd576c1af9922862f6a7a7 ?
Comment 6 Lukasz Krotowski 2008-06-15 10:43:27 UTC
Created attachment 17124 [details]
xorg.conf

Plus:
xf86-video-ati: git master,
xserver: git master.
Comment 7 Lukasz Krotowski 2008-06-15 11:30:01 UTC
Ok, bug fixed in git with: 59112c9e521d1543e8b76635ef223e7f29d35e6a, closing.


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.