Bug 5385 - Xorg drops errors about (EE) RADEON(0): FIFO timed out, resetting engine...
Summary: Xorg drops errors about (EE) RADEON(0): FIFO timed out, resetting engine...
Status: RESOLVED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/other (show other bugs)
Version: XOrg git
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-20 01:51 UTC by Florian Manschwetus
Modified: 2010-12-02 19:57 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments
xorg.conf (14.59 KB, text/plain)
2005-12-20 01:53 UTC, Florian Manschwetus
no flags Details
Xorg.0.log (49.65 KB, text/plain)
2005-12-20 01:53 UTC, Florian Manschwetus
no flags Details
modified xorg.conf using 7.0 version of xorg (15.16 KB, text/plain)
2006-01-13 01:50 UTC, Florian Manschwetus
no flags Details
the according Xorg.0.log using 7.0 version of xorg (50.74 KB, text/plain)
2006-01-13 01:50 UTC, Florian Manschwetus
no flags Details
radeon driver with radeonfb 2.6.17-rc6 (47.59 KB, text/plain)
2006-06-16 20:08 UTC, Jory A. Pratt
no flags Details

Description Florian Manschwetus 2005-12-20 01:51:32 UTC
My Xorg gets very slow, so slow that it is impossible to work or open windows
I used the 6.8.99.15-r4 xorg in gentoo-portage
It is an PCI-E based M 300
drm and mesa are from CVS according to:
http://dri.freedesktop.org/wiki/Building
i'll attach my xorg.conf and the log

Using Gentoo with Suspend2-Source 2.6.24-r7 and gcc 3.4.4 (-march=pentium-m)

(for intrested its an IBM TP R52 
Details:
http://www.pro-com.org/nofost.de/Pages/ArticleDetails.aspx?ArticleNumber=1847W62-H
)
Comment 1 Florian Manschwetus 2005-12-20 01:53:21 UTC
Created attachment 4129 [details]
xorg.conf
Comment 2 Florian Manschwetus 2005-12-20 01:53:42 UTC
Created attachment 4130 [details]
Xorg.0.log
Comment 3 Florian Manschwetus 2006-01-12 23:53:54 UTC
using now xorg7.0 doesn't work (x hangs)
Comment 4 Florian Manschwetus 2006-01-13 01:50:15 UTC
Created attachment 4331 [details]
modified xorg.conf using 7.0 version of xorg
Comment 5 Florian Manschwetus 2006-01-13 01:50:54 UTC
Created attachment 4332 [details]
the according Xorg.0.log using 7.0 version of xorg
Comment 6 Florian Manschwetus 2006-01-13 01:56:23 UTC
ok a moved on to xorg-x11-7.0 and build it up like it should be, but with the
dri enabled config (look latest xorg.conf attachment) the x hangs at 99,9% cpu
usage with the nixe gray/black background and the mouse in front of it
(moveable) but i can't kill it or switch back to console (using ssh for
diagnostic and later reboot)

x works fine using vesa instead of radeon

regards
Florian

p.s. some minor system updates were made (e.g. suspend2-2.6.15-r1 kernel and
some other little changes minor upgrades of glibc and gcc and so on, nothing havy)
Comment 7 Alex Deucher 2006-01-13 04:24:10 UTC
(In reply to comment #6)
> ok a moved on to xorg-x11-7.0 and build it up like it should be, but with the
> dri enabled config (look latest xorg.conf attachment) the x hangs at 99,9% cpu
> usage with the nixe gray/black background and the mouse in front of it
> (moveable) but i can't kill it or switch back to console (using ssh for
> diagnostic and later reboot)

Does it work without the DRI loaded?  what does your kernel log or dmesg show
about the drm?
Comment 8 Jory A. Pratt 2006-06-16 20:08:59 UTC
Created attachment 5948 [details]
radeon driver with radeonfb 2.6.17-rc6

Still an issue but causes complete desktop to halt in an unusable state.
Comment 9 Jory A. Pratt 2006-06-16 20:10:35 UTC
As this does prevent the X server from being used this would be a blocker as far
as I am aware.
Comment 10 Daniel Stone 2006-06-17 00:17:38 UTC
no, blocker is 'OMG X IS COMPLETELY USELESS TO EVERYONE, WE CANNOT RELEASE WITH
THIS AT ALL' or security bugs, if that.  usually just critical for those two. 
bugs about not functioning on certain hardware are normal; we have lots of those.
Comment 11 Matt Turner 2010-12-02 19:57:17 UTC
Closing due to inactivity. Reopen if this is still a bug.


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.