Bug 24101 - Backing storage memory corruption
Summary: Backing storage memory corruption
Status: RESOLVED WORKSFORME
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: high normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-22 22:27 UTC by Matti Aarnio
Modified: 2010-10-27 09:46 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Screenshot showing pixel hashes (193.07 KB, image/png)
2009-09-22 22:28 UTC, Matti Aarnio
no flags Details
Xorg.0.log (65.24 KB, text/plain)
2009-09-22 22:29 UTC, Matti Aarnio
no flags Details

Description Matti Aarnio 2009-09-22 22:27:21 UTC
On bleeding edge Fedora 12 beta, the Xorg X server version is called:

  xorg-x11-server-Xorg-1.6.99.902-1.fc12.x86_64

and following behaviour got worse with lattest update on this file without any change on the actual display card driver:

  xorg-x11-drv-ati-6.13.0-0.4.20090908git651fe5a47.fc12.x86_64

This will lead to system hangup after a few hours of mouse activity.


This may be partly due to ati/radeon driver, as with  radeonhd driver this card shows everything in interesting ways of pixel hash, but radeon/ati used not to.

Notable detail is that this PCIe card has 512 MB of video memory, but only 256 MB aperture for mmio.

Screenshot attached now, Xorg.0.log soon.
Comment 1 Matti Aarnio 2009-09-22 22:28:28 UTC
Created attachment 29786 [details]
Screenshot showing pixel hashes
Comment 2 Matti Aarnio 2009-09-22 22:29:18 UTC
Created attachment 29787 [details]
Xorg.0.log
Comment 3 Alex Deucher 2010-10-19 17:55:14 UTC
Is this still an issue with a newer kernel and driver?
Comment 4 Matti Aarnio 2010-10-27 09:46:10 UTC
Apparently not.  I have not seen this issue with this server:

  xorg-x11-server-Xorg-1.9.0-15.fc15.x86_64


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.