Bug 693686

Summary: [RV515] X partial hang when starting xterm or rxvt
Product: [Fedora] Fedora Reporter: Alexander Boström <abo>
Component: xorg-x11-drv-atiAssignee: Jérôme Glisse <jglisse>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: mcepl, xgl-maint
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 16:28:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
xorg.conf which triggers this bug
none
Xorg log
none
dmesg (redacted...) none

Description Alexander Boström 2011-04-05 10:49:59 UTC
Description of problem:
X hangs partially when xterm or rxvt is started under GNOME Shell. The mouse pointer responds but no other screen content is updated.

Version-Release number of selected component (if applicable):
kernel-2.6.38.2-9.fc15.x86_64
xorg-x11-drv-ati-6.14.0-7.20110316gitcdfc007ec.fc15.x86_64
xorg-x11-drv-evdev-2.6.0-3.fc15.x86_64
xterm-268-1.fc15.x86_64
mutter-2.91.93-1.fc15.x86_64

Using radeon_drv.

How reproducible:
Always.

Steps to Reproduce:
1. Upgrade to F15
2. Login in to GNOME
3. Start xterm
  
Actual results:
Everything except the mouse pointer hangs, the xterm window does not appear.

Expected results:
xterm window should appear.

Additional info:

Other apps does not cause this. Firefox, Pidgin, Nautilus, Evolution etc are all fine.

Graphics card: 01:00.0 VGA compatible controller: ATI Technologies Inc RV516 [Radeon X1300/X1550 Series]

Using dual monitors. (Will try it with only one later.)

"killall -9 Xorg" works, brings back GDM.

xorg.0.log:

[  8754.912] [mi] EQ overflowing. The server is probably stuck in an infinite loop.
[  8754.912] 
Backtrace:
[  8755.016] 0: /usr/bin/Xorg (xorg_backtrace+0x2f) [0x4a116f]
[  8755.016] 1: /usr/bin/Xorg (mieqEnqueue+0x1e9) [0x4a0689]
[  8755.016] 2: /usr/bin/Xorg (xf86PostMotionEventM+0xa3) [0x47d993]
[  8755.016] 3: /usr/bin/Xorg (xf86PostMotionEventP+0x52) [0x47dab2]
[  8755.016] 4: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7fc8dec77000+0x498b) [0x7fc8dec7b98b]
[  8755.016] 5: /usr/bin/Xorg (0x400000+0x6b468) [0x46b468]
[  8755.016] 6: /usr/bin/Xorg (0x400000+0x119a60) [0x519a60]
[  8755.016] 7: /lib64/libpthread.so.0 (0x7fc8e431d000+0xf4e0) [0x7fc8e432c4e0]
[  8755.017] 8: /lib64/libc.so.6 (0x7fc8e3034000+0xed8cb) [0x7fc8e31218cb]
[  8755.017] 9: /lib64/libc.so.6 (0x7fc8e3034000+0x7ea61) [0x7fc8e30b2a61]
[  8755.017] 10: /lib64/libc.so.6 (__libc_malloc+0x67) [0x7fc8e30b0827]
[  8755.017] 11: /lib64/libc.so.6 (0x7fc8e3034000+0x7225d) [0x7fc8e30a625d]
[  8755.017] 12: /lib64/libc.so.6 (0x7fc8e3034000+0x787ba) [0x7fc8e30ac7ba]
[  8755.017] 13: /lib64/libc.so.6 (0x7fc8e3034000+0x7a5db) [0x7fc8e30ae5db]
[  8755.017] 14: /lib64/libc.so.6 (__libc_malloc+0x75) [0x7fc8e30b0835]
[  8755.017] 15: /usr/bin/Xorg (miFillConvexPoly+0xd4) [0x551894]
[  8755.017] 16: /usr/bin/Xorg (0x400000+0xda4c8) [0x4da4c8]
[  8755.017] 17: /usr/bin/Xorg (0x400000+0x2b49d) [0x42b49d]
[  8755.017] 18: /usr/bin/Xorg (0x400000+0x2eb41) [0x42eb41]
[  8755.017] 19: /usr/bin/Xorg (0x400000+0x22dca) [0x422dca]
[  8755.017] 20: /lib64/libc.so.6 (__libc_start_main+0xed) [0x7fc8e305531d]
[  8755.017] 21: /usr/bin/Xorg (0x400000+0x230b1) [0x4230b1]

Comment 1 Matěj Cepl 2011-04-05 12:27:54 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 2 Alexander Boström 2011-04-05 12:36:48 UTC
Ok, I'll do that!

A quick note though:
The problem is not reproducible with only one monitor attached.

Comment 3 Alexander Boström 2011-04-05 14:10:32 UTC
I'm not getting anything in /var/log/messages since the upgrade. (Will try an selinux relabel later.)

I had an old xorg.conf laying around, see attachment.

With it, I get mirrored displays in GDM. Without it, I get login prompt on one and background image on the other.

Without it, this bug is not reproducible.

Comment 4 Alexander Boström 2011-04-05 14:11:26 UTC
Created attachment 489987 [details]
xorg.conf which triggers this bug

Comment 5 Alexander Boström 2011-04-05 14:16:19 UTC
Created attachment 489988 [details]
Xorg log

(I think I copied the log before the infinite loop was detected, so no backtrace at the end.)

Comment 6 Alexander Boström 2011-04-05 14:17:07 UTC
Created attachment 489989 [details]
dmesg (redacted...)

Comment 7 Fedora End Of Life 2012-08-07 16:28:36 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping