Created attachment 42824 [details] [review] log for Xorg 1.9.2 Sometime when gxine (xine gui)is started the Xorg server hangs up and FIFO reset message is printed Xorg.log; I am not suspecting the HW because I have tried with two ATI chips RV280 and RV380. The issue was reproduced with Xorg 1.7.7 too; I have faced this issue with earlier than 2.6.36 (guess it was 2.6.29) kernel also. As far as I remember the issue occurs with default Xorg settings (no xorg.conf) too. Here is back trace: [ 77706.941] (II) RADEON(0): Output: S-video, Detected Monitor Type: 0 [ 82188.534] (EE) RADEON(0): FIFO timed out, resetting engine... [ 82189.959] (EE) RADEON(0): FIFO timed out, resetting engine... [ 82191.282] (EE) RADEON(0): FIFO timed out, resetting engine... [ 82192.497] (EE) RADEON(0): FIFO timed out, resetting engine... [ 82193.714] (EE) RADEON(0): FIFO timed out, resetting engine... [ 82194.928] (EE) RADEON(0): FIFO timed out, resetting engine... [ 82196.142] (EE) RADEON(0): FIFO timed out, resetting engine... [ 82197.354] (EE) RADEON(0): FIFO timed out, resetting engine... [ 82198.557] (EE) RADEON(0): FIFO timed out, resetting engine... [ 82199.755] (EE) RADEON(0): FIFO timed out, resetting engine... [ 82200.955] (EE) RADEON(0): FIFO timed out, resetting engine... [ 82201.841] [mi] EQ overflowing. The server is probably stuck in an infinite loop. [ 82201.841] Backtrace: [ 82201.859] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e7abb] [ 82201.859] 1: /usr/bin/X (mieqEnqueue+0x191) [0x80e73d1] [ 82201.859] 2: /usr/bin/X (xf86PostMotionEventP+0xce) [0x80c38fe] [ 82201.876] 3: /usr/lib/xorg/modules/input/evdev_drv.so (0xb7265000+0x34c1) [0xb72684c1] [ 82201.876] 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb7265000+0x37b1) [0xb72687b1] [ 82201.876] 5: /usr/bin/X (0x8048000+0x69c7f) [0x80b1c7f] [ 82201.876] 6: /usr/bin/X (0x8048000+0x11ebf2) [0x8166bf2] [ 82201.876] 7: (vdso) (__kernel_sigreturn+0x0) [0xb780f400] [ 82201.876] 8: /usr/lib/xorg/modules/drivers/radeon_drv.so (0xb72a1000+0x6c786) [0xb730d786] [ 82201.876] 9: /usr/lib/xorg/modules/drivers/radeon_drv.so (0xb72a1000+0x77d19) [0xb7318d19] [ 82201.876] 10: /usr/bin/X (0x8048000+0x132236) [0x817a236] [ 82201.888] 11: /usr/lib/xorg/modules/extensions/libextmod.so (XvdiPutImage+0x18e) [0xb77fed5e] [ 82201.888] 12: /usr/lib/xorg/modules/extensions/libextmod.so (0xb77f4000+0xed7a) [0xb7802d7a] [ 82201.888] 13: /usr/lib/xorg/modules/extensions/libextmod.so (ProcXvDispatch+0x3a) [0xb7803d0a] [ 82201.888] 14: /usr/bin/X (0x8048000+0x28ff7) [0x8070ff7] [ 82201.888] 15: /usr/bin/X (0x8048000+0x1d6fa) [0x80656fa] [ 82201.888] 16: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb7533bb6] [ 82201.888] 17: /usr/bin/X (0x8048000+0x1d2c1) [0x80652c1] [ 82202.209] (EE) RADEON(0): FIFO timed out, resetting engine... [ 82203.410] (EE) RADEON(0): FIFO timed out, resetting engine... [ 82204.614] (EE) RADEON(0): FIFO timed out, resetting engine... [ 82205.812] (EE) RADEON(0): FIFO timed out, resetting engine...
Created attachment 42825 [details] log for Xorg 1.7.7
Created attachment 42826 [details] xorg.conf
Any chance you could test kms?
Working so far. [ 1.917459] [drm] Initialized drm 1.1.0 20060810 [ 1.917620] [drm] radeon defaulting to kernel modesetting. [ 1.917725] [drm] radeon kernel modesetting enabled. [ 1.920351] [drm] initializing kernel modesetting (RV380 0x1002:0x3E50). But it might take some time to reproduce the issue. On Tue, 2011-02-01 at 13:11 -0800, bugzilla-daemon@freedesktop.org wrote: > https://bugs.freedesktop.org/show_bug.cgi?id=33822 > > --- Comment #3 from Alex Deucher <agd5f@yahoo.com> 2011-02-01 13:11:12 PST --- > Any chance you could test kms? >
I think this report may be closed. The kms driver is working well for more than month. Thanks!
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.