Bug 715361 - [abrt] kernel: [524959.447008] WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:248 radeon_fence_wait+0x2a8/0x32b [radeon](): TAINTED Warning Issued
Summary: [abrt] kernel: [524959.447008] WARNING: at drivers/gpu/drm/radeon/radeon_fenc...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jérôme Glisse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:18c9f008092e5f22668d02a8d68...
: 718229 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-22 15:56 UTC by Bryan Quigley
Modified: 2012-08-07 16:30 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 16:30:14 UTC
Type: ---


Attachments (Terms of Use)
20120620-gpu-lockup-dmesg (79.00 KB, text/plain)
2012-06-20 22:42 UTC, collura
no flags Details
20120620-gpu-lockup-messages (146.94 KB, text/plain)
2012-06-20 22:43 UTC, collura
no flags Details
20120620-gpu-lockup-xsession-errors (10.96 KB, text/plain)
2012-06-20 22:43 UTC, collura
no flags Details

Description Bryan Quigley 2011-06-22 15:56:46 UTC
abrt version: 2.0.1
architecture:   x86_64
cmdline:        ro root=UUID=9acfb80e-44ad-40eb-b7ea-b771d428b41b rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
comment:        I was opening up some new tabs in Firefox, (many other apps open) and I may have hit the Windows key to switch appplications.  Running Gnome-Shell.
component:      kernel
kernel:         2.6.38.8-32.fc15.x86_64
kernel_tainted: 512
os_release:     Fedora release 15 (Lovelock)
package:        kernel
reason:         [524959.447008] WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:248 radeon_fence_wait+0x2a8/0x32b [radeon]()
reported_to:    kerneloops: URL=http://submit.kerneloops.org/submitoops.php
time:           Wed Jun 22 11:41:54 2011

backtrace:
:[524959.447008] WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:248 radeon_fence_wait+0x2a8/0x32b [radeon]()
:[524959.447010] Hardware name: OptiPlex 790
:[524959.447011] GPU lockup (waiting for 0x005857CB last fence id 0x005857C9)
:[524959.447012] Modules linked in: vboxnetadp vboxnetflt vboxdrv tcp_lp tun fuse ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat xt_CHECKSUM iptable_mangle bridge 8021q garp stp sunrpc llc cpufreq_ondemand acpi_cpufreq freq_table mperf ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables snd_hda_codec_hdmi i2c_i801 snd_hda_codec_realtek virtio_net microcode kvm_intel kvm snd_hda_intel snd_hda_codec snd_hwdep iTCO_wdt iTCO_vendor_support snd_seq snd_seq_device snd_pcm snd_timer snd soundcore snd_page_alloc dcdbas e1000e serio_raw ipv6 video radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan]
:[524959.447036] Pid: 1353, comm: Xorg Not tainted 2.6.38.8-32.fc15.x86_64 #1
:[524959.447037] Call Trace:
:[524959.447043]  [<ffffffff8105511a>] warn_slowpath_common+0x83/0x9b
:[524959.447045]  [<ffffffff810551d5>] warn_slowpath_fmt+0x46/0x48
:[524959.447060]  [<ffffffffa00d8435>] ? evergreen_gpu_is_lockup+0xba/0xc2 [radeon]
:[524959.447070]  [<ffffffffa009fc74>] radeon_fence_wait+0x2a8/0x32b [radeon]
:[524959.447073]  [<ffffffff8106f26e>] ? autoremove_wake_function+0x0/0x3d
:[524959.447082]  [<ffffffffa00a0239>] radeon_sync_obj_wait+0x11/0x13 [radeon]
:[524959.447086]  [<ffffffffa00655da>] ttm_bo_wait+0xbf/0x17a [ttm]
:[524959.447090]  [<ffffffffa0066002>] ? ttm_bo_list_ref_sub+0x29/0x2b [ttm]
:[524959.447102]  [<ffffffffa00afe6b>] radeon_bo_wait+0x7b/0x9f [radeon]
:[524959.447113]  [<ffffffffa00b03dd>] radeon_gem_wait_idle_ioctl+0x3d/0x74 [radeon]
:[524959.447120]  [<ffffffffa0019861>] drm_ioctl+0x29e/0x37b [drm]
:[524959.447123]  [<ffffffff811eb0eb>] ? inode_has_perm+0x76/0x8c
:[524959.447133]  [<ffffffffa00b03a0>] ? radeon_gem_wait_idle_ioctl+0x0/0x74 [radeon]
:[524959.447137]  [<ffffffff81474408>] ? _cond_resched+0xe/0x22
:[524959.447139]  [<ffffffff8104127e>] ? should_resched+0xe/0x2d
:[524959.447141]  [<ffffffff8104127e>] ? should_resched+0xe/0x2d
:[524959.447143]  [<ffffffff811eb1a5>] ? file_has_perm+0xa4/0xc6
:[524959.447146]  [<ffffffff8112f3a0>] do_vfs_ioctl+0x47e/0x4bf
:[524959.447148]  [<ffffffff8109fc99>] ? audit_syscall_exit+0x12d/0x148
:[524959.447150]  [<ffffffff8112f437>] sys_ioctl+0x56/0x7b
:[524959.447152]  [<ffffffff81009e75>] ? int_check_syscall_exit_work+0x34/0x3d
:[524959.447154]  [<ffffffff81009bc2>] system_call_fastpath+0x16/0x1b

event_log:
:2011-06-22-11:56:32> Submitting oops report to http://submit.kerneloops.org/submitoops.php
:2011-06-22-11:56:42  Kernel oops report was uploaded

Comment 1 Bryan Quigley 2011-06-22 15:58:02 UTC
I forgot to mention that the computer (at least the GUI) locked up, I could switch to VTs.  Gnome-shell was pegging the cpu.

Comment 2 collura 2011-09-05 04:13:19 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 3 Jason Smith 2012-05-28 16:40:57 UTC
*** Bug 718229 has been marked as a duplicate of this bug. ***

Comment 4 Jason Smith 2012-05-28 16:44:26 UTC
Thank you for taking the time to report this bug and apologies for the delayed response. Updates to this package have been released since it was first reported and I wanted to check to see if this error has been resolved with updates.  If not done already, please update the package and re-test and report the results here. You can obtain the updated package by typing 'yum update xorg-x11-drv-ati' or using the graphical updater, Software Update.

If this error is still persistient after completing most recent updates, please respond and attach a dmesg output in plain text format and a copy of the X server log file (/var/log/Xorg.*.log) for us to review this report further.

---
Jason
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 5 collura 2012-06-20 22:41:02 UTC
just had a gpu lockup when opened new firefox tab where 
monitor went black for about a second and then came back 
but looks like different error for me now  
since i have not found the 'radeon_fence.c:248' error this time
or same issue but no error because not as drastic?

Comment 6 collura 2012-06-20 22:42:21 UTC
Created attachment 593320 [details]
20120620-gpu-lockup-dmesg

Comment 7 collura 2012-06-20 22:43:08 UTC
Created attachment 593321 [details]
20120620-gpu-lockup-messages

Comment 8 collura 2012-06-20 22:43:57 UTC
Created attachment 593322 [details]
20120620-gpu-lockup-xsession-errors

Comment 9 collura 2012-06-20 23:07:25 UTC
0) comment#5 was with
   xorg-x11-drv-ati-6.14.3-4.20120201git36c190671.fc16.x86_64
   kernel-3.4.2-1.fc16.x86_64

1) more possible related for the list:

bug reports with radeon_fence.c 248:

rs780:  https://bugzilla.redhat.com/show_bug.cgi?id=712559
          xorg-x11-drv-ati
          kernel-2.6.38.6-26.rc1.fc15.x86_64

2) not saying i belive this or anything but 
these some of the gpu lockup bugs have been around for a bit
is it possible that some of the different line numbers 
might be related by same bug shifting line numbers 
due to varying version of ati driver? 

bug reports with the radeon_fence.c 235:

rs480:  https://bugzilla.redhat.com/show_bug.cgi?id=673740
          xorg-x11-drv-ati-6.13.1-0.4.20100705git37b348059.fc14.x86_64
          kernel-2.6.35.10-74.fc14.x86_64

rs780:  https://bugzilla.redhat.com/show_bug.cgi?id=699512
          xorg-x11-drv-ati
          kernel-2.6.35.12-88.fc14.x86_64
          kernel-3.1.7-1.fc16.x86_64

        (also listed 'gdm-simple-greeter[18959]: Gtk-WARNING: gtkwidget.c:5691: widget not within a GtkWindow'
                    'rtkit-daemon[3295]: Recovering from system lockup, not allowing further RT threads.')

Comment 10 Jason Smith 2012-06-23 14:09:08 UTC
Hello,

Thank you for your update, marking report as Triaged for additional review.

---
Jason
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 11 Fedora End Of Life 2012-08-07 16:30:19 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


Note You need to log in before you can comment on or make changes to this bug.