Bug 23015

Summary:

Display corruption, X-window becomes unusable with radeon driver and Radeon HD 3300: [drm] wait for fifo...

Product:

xorg

Reporter:

Ekimov Alexandr <toekimov>

Component:

Driver/Radeon

Assignee:

xf86-video-ati maintainers <xorg-driver-ati>

Status:

RESOLVED INVALID

QA Contact:

Xorg Project Team <xorg-team>

Severity:

critical

Priority:

medium

Version:

7.3 (2007.09)

Hardware:

x86-64 (AMD64)

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
lspci -vvv for ASUS m4a78t-e	none
xorg.conf	none

Description Ekimov Alexandr 2009-07-29 01:22:52 UTC

While 10-15 minutes working with X-window the whole screen gets corrupted(vertical lines and trash) and machine becomes unusable. Scrolling something (for example: filelist in Krusader) makes it faster. Dmesg says: [drm] wait for fifo failed status : 0xE00014AC 0x00100003.
VideoCard: Radeon HD 3300 Integrated Graphics
This problem was found on 2 machines: MSI 790GX-G65 motherbord and ASUS m4a78t-e (790GX too).

I build on last week radeon and radeonhd from git, but the same result.
But i find next:
If disable onboard video memory(called SIDEPORT) and use ONLY system memory as
video memory(in BIOS called UMA) problem disappeared.  


Post Scriptum: Sorry for my pidgin english.

Comment 1 Ekimov Alexandr 2009-07-29 01:26:50 UTC

Created attachment 28143 [details]
lspci -vvv for ASUS m4a78t-e

Comment 2 Ekimov Alexandr 2009-07-29 01:27:56 UTC

Created attachment 28144 [details]
xorg.conf

Comment 3 Alex Deucher 2009-07-29 01:42:02 UTC

sideport isn't supported at the moment.

Comment 4 Alex Deucher 2010-10-19 17:35:23 UTC

Is this still an issue with KMS or a newer version of the driver?

Comment 5 Adam Jackson 2018-06-12 19:10:25 UTC

Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.

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.