Bug 714834

Summary: [BARTS] Frequent GPU lockups [@ xf86PostMotionEventM]
Product: [Fedora] Fedora Reporter: Jon Stanley <jonstanley>
Component: xorg-x11-drv-atiAssignee: Jérôme Glisse <jglisse>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: airlied, awilliam, collura, jglisse, mads, mcepl, xgl-maint
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: [cat:modesetting]
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 16:30:03 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
dmesg from system
none
Xorg log
none
Xorg.log.old
none
/var/log/messages from system none

Description Jon Stanley 2011-06-21 00:22:45 UTC 
Hardware: Sandy Bridge Core i7-2600, ATI Radeon HD 6850

01:00.0 0300: 1002:6739 (the exact card is not in the kernel PCI database)

I'm seeing frequent (read: makes the system unusable) GPU softlockups off the F15 livecd. This is a brand new machine, so my first attempt to run Fedora on it. The Other Operating System(TM) works fine, however, so it's not a hardware issue.

The symptom is that the display will become unresponsive, the kernel softresets the GPU, and everything is fine until it happens again. Occassionally though, X becomes completely unresponsive and the only recourse is to ctrl-alt-f2 and do a pkill Xorg and let systemd relaunch it. This may or may not be two separate issues, I'll treat them as one until told otherwise.

I've attached /var/log/messages, where I've captured a sysrq-t when the X server was completely non-responsive. I've also attached the last two Xorg.0.log files, and a dmesg. Let me know what more may be needed.
Comment 1 Jon Stanley 2011-06-21 00:23:55 UTC 
Created attachment 505721 [details]
dmesg from system
Comment 2 Jon Stanley 2011-06-21 00:34:45 UTC 
Created attachment 505723 [details]
Xorg log
Comment 3 Jon Stanley 2011-06-21 00:35:18 UTC 
Created attachment 505724 [details]
Xorg.log.old
Comment 4 Jon Stanley 2011-06-21 00:36:14 UTC 
Created attachment 505725 [details]
/var/log/messages from system
Comment 5 Matěj Cepl 2011-06-21 13:36:45 UTC 
[  3236.462] 0: /usr/bin/Xorg (xorg_backtrace+0x2f) [0x4a13df]
[  3236.462] 1: /usr/bin/Xorg (mieqEnqueue+0x1e9) [0x4a08f9]
[  3236.462] 2: /usr/bin/Xorg (xf86PostMotionEventM+0xa3) [0x47dae3]
[  3236.462] 3: /usr/bin/Xorg (xf86PostMotionEventP+0x52) [0x47dc02]
[  3236.462] 4: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7f542dbf8000+0x498b) [0x7f542dbfc98b]
[  3236.462] 5: /usr/bin/Xorg (0x400000+0x6b538) [0x46b538]
[  3236.463] 6: /usr/bin/Xorg (0x400000+0x119bf0) [0x519bf0]
[  3236.463] 7: /lib64/libpthread.so.0 (0x7f5433aa8000+0xf3c0) [0x7f5433ab73c0]
[  3236.463] 8: /lib64/libc.so.6 (ioctl+0x7) [0x7f5432897af7]
[  3236.463] 9: /usr/lib64/libdrm.so.2 (drmIoctl+0x28) [0x7f5431025338]
[  3236.463] 10: /usr/lib64/libdrm.so.2 (drmCommandWriteRead+0x1c) [0x7f543102749c]
[  3236.463] 11: /usr/lib64/libdrm_radeon.so.1 (0x7f5430708000+0x1bc9) [0x7f5430709bc9]
[  3236.463] 12: /usr/lib64/libdrm_radeon.so.1 (0x7f5430708000+0x1df4) [0x7f5430709df4]
[  3236.463] 13: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7f543090e000+0xc3584) [0x7f54309d1584]
[  3236.463] 14: /usr/lib64/xorg/modules/libexa.so (0x7f542fee1000+0x616e) [0x7f542fee716e]
[  3236.463] 15: /usr/lib64/xorg/modules/libexa.so (0x7f542fee1000+0x8cfd) [0x7f542fee9cfd]
[  3236.463] 16: /usr/lib64/xorg/modules/libexa.so (0x7f542fee1000+0x13c5b) [0x7f542fef4c5b]
[  3236.463] 17: /usr/lib64/xorg/modules/libexa.so (0x7f542fee1000+0xffef) [0x7f542fef0fef]
[  3236.463] 18: /usr/bin/Xorg (0x400000+0xd99cd) [0x4d99cd]
[  3236.464] 19: /usr/bin/Xorg (0x400000+0xd4475) [0x4d4475]
[  3236.464] 20: /usr/bin/Xorg (0x400000+0x2ec11) [0x42ec11]
[  3236.464] 21: /usr/bin/Xorg (0x400000+0x22e1a) [0x422e1a]
[  3236.464] 22: /lib64/libc.so.6 (__libc_start_main+0xed) [0x7f54327e043d]
[  3236.464] 23: /usr/bin/Xorg (0x400000+0x23101) [0x423101]
[  3284.142] (II) AIGLX: Suspending AIGLX clients for VT switch

annotated:

Frame 2: /usr/bin/Xorg (xf86PostMotionEventM+0xa3) [0x47dae3]
	/usr/src/debug/xorg-server-1.10.1/hw/xfree86/common/xf86Xinput.c:1056
	xf86PostMotionEventM
Frame 3: /usr/bin/Xorg (xf86PostMotionEventP+0x52) [0x47dc02]
	/usr/src/debug/xorg-server-1.10.1/hw/xfree86/common/xf86Xinput.c:1008
	xf86PostMotionEventP
Frame 5: /usr/bin/Xorg (0x400000+0x6b538) [0x46b538]
	/usr/src/debug/xorg-server-1.10.1/hw/xfree86/common/xf86Events.c:300
	xf86SigioReadInput
Frame 6: /usr/bin/Xorg (0x400000+0x119bf0) [0x519bf0]
	/usr/src/debug/xorg-server-1.10.1/hw/xfree86/os-support/linux/../shared/sigio.c:106
	xf86SIGIO
Frame 14: /usr/lib64/xorg/modules/libexa.so (0x7f542fee1000+0x616e) [0x7f542fee716e]
	/usr/src/debug/xorg-server-1.10.1/exa/exa_migration_classic.c:220
	exaCopyDirty
Frame 15: /usr/lib64/xorg/modules/libexa.so (0x7f542fee1000+0x8cfd) [0x7f542fee9cfd]
	/usr/src/debug/xorg-server-1.10.1/exa/exa_migration_mixed.c:247
	exaPrepareAccessReg_mixed
Frame 16: /usr/lib64/xorg/modules/libexa.so (0x7f542fee1000+0x13c5b) [0x7f542fef4c5b]
	/usr/src/debug/xorg-server-1.10.1/exa/exa_unaccel.c:580
	ExaPrepareCompositeReg
Frame 17: /usr/lib64/xorg/modules/libexa.so (0x7f542fee1000+0xffef) [0x7f542fef0fef]
	/usr/src/debug/xorg-server-1.10.1/exa/exa_render.c:1070
	exaComposite
Frame 18: /usr/bin/Xorg (0x400000+0xd99cd) [0x4d99cd]
	/usr/src/debug/xorg-server-1.10.1/miext/damage/damage.c:629
	damageComposite
Frame 19: /usr/bin/Xorg (0x400000+0xd4475) [0x4d4475]
	/usr/src/debug/xorg-server-1.10.1/render/render.c:740
	ProcRenderComposite
Frame 20: /usr/bin/Xorg (0x400000+0x2ec11) [0x42ec11]
	/usr/src/debug/xorg-server-1.10.1/dix/dispatch.c:431
	Dispatch
Frame 21: /usr/bin/Xorg (0x400000+0x22e1a) [0x422e1a]
	/usr/src/debug/xorg-server-1.10.1/dix/main.c:289
	main
Comment 6 collura 2011-09-05 04:11:32 UTC 
duplicate bugs?

based on the repeated error:
   'WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:248
    radeon_fence_wait+0x../0x..' 

(where '0x../0x..' varried as listed below)

the following bugs might be duplicates:

   bug#714384 (https://bugzilla.redhat.com/show_bug.cgi?id=714834)
   ('Jun 20 19:30:36 localhost kernel: [    0.000000] 
     Linux version 2.6.38.6-26.rc1.fc15.x86_64
     (mockbuild.fedoraproject.org) 
     (gcc version 4.6.0 20110428 (Red Hat 4.6.0-6) (GCC) ) 
     #1 SMP Mon May 9 20:45:15 UTC 2011
   ')
   attachment '/var/log/messages'  has 
     "Jun 20 19:32:43 localhost kernel: [  156.065768] 
      WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:248 
      radeon_fence_wait+0x2a8/0x32b"
   video amd hd 6850 series :
     'Hardware: Sandy Bridge Core i7-2600, ATI Radeon HD 6850'
     '01:00.0 0300: 1002:6739 (the exact card is not in the kernel 
         PCI database)'


   bug#715361 (https://bugzilla.redhat.com/show_bug.cgi?id=715361)
   ('kernel:         2.6.38.8-32.fc15.x86_64')
     "WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:248
      radeon_fence_wait+0x2a8/0x32b"
   maybe intel 2000 series or amd hd 6350 [512MB] series or 
     amd hd 6450 [1GB] series video? : 
       'Hardware name: OptiPlex 790'


   bug#720016 (https://bugzilla.redhat.com/show_bug.cgi?id=720016)
   ('kernel:         2.6.38.8-32.fc15.x86_64')
     "WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:248
      radeon_fence_wait+0x2a8/0x32b"
   maybe amd hd 6250 or amd hd 6310 series video? : 
       'Hardware name: Satellite C650D' 


and the following bugs seem to be related ('radeon_fence_wait+0x244/0x2d8' instead of '0x2a8/0x32b'):

   bug#703644 (https://bugzilla.redhat.com/show_bug.cgi?id=703644)
   ('kernel:         2.6.38.5-24.fc15.i686.PAE')
     "WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:248 
      radeon_fence_wait+0x244/0x2d8"
   maybe intel 815 series video? : 'Hardware name: Latitude D610'


   bug#712996 (https://bugzilla.redhat.com/show_bug.cgi?id=712996)
   ('kernel:         2.6.38.6-27.fc15.i686')
     "WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:248
      radeon_fence_wait+0x248/0x2bb"
   maybe amd radeon hd 6310 series video? : 'Hardware name: Aspire 4253'


   bug#718229 (https://bugzilla.redhat.com/show_bug.cgi?id=718229)
   ('kernel:         2.6.38.8-32.fc15.x86_64')
     "WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:248 
      radeon_fence_wait+0x2a8/0x32b"
    maybe gforce 8200 series video? : 'Hardware name: GF8200C M2+'



** the video hardware guesses were either 
      pulled from bug report info 
   or 
      guessed by dreamquesting while doing internet search 
      for 'default specs' of the hardware which was listed 
      in the report info
   so take the video hardware guesses accordingly. **
Comment 7 Fedora End Of Life 2012-08-07 16:30:05 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