Hide Forgot
abrt version: 2.0.1 architecture: i686 cmdline: ro root=/dev/VolGroup00/LogVol00 UUID=14962129-d36d-4c24-91e5-fa4102bd5819 SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us rd_plytheme=charge quiet rhgb comment: This might have caused my machine to crash - perhaps related to suspend/resume component: kernel kernel: 2.6.38.5-24.fc15.i686.PAE kernel_tainted: 512 os_release: Fedora release 15 (Lovelock) package: kernel reason: WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:248 radeon_fence_wait+0x244/0x2d8 [radeon]() reported_to: kerneloops: URL=http://submit.kerneloops.org/submitoops.php time: Wed May 11 00:38:00 2011 backtrace: :WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:248 radeon_fence_wait+0x244/0x2d8 [radeon]() :Hardware name: Latitude D610 :GPU lockup (waiting for 0x00002259 last fence id 0x00002253) :Modules linked in: fuse vfat fat ipw2200 snd_intel8x0 tg3 snd_ac97_codec ac97_bus snd_seq libipw iTCO_wdt snd_seq_device iTCO_vendor_support snd_pcm cfg80211 dell_laptop snd_timer snd rfkill soundcore snd_page_alloc lib80211 dcdbas joydev microcode ipv6 yenta_socket video radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan] :Pid: 903, comm: Xorg Not tainted 2.6.38.5-24.fc15.i686.PAE #1 :Call Trace: : [<c044205d>] warn_slowpath_common+0x7c/0x91 : [<f7bd5ca7>] ? radeon_fence_wait+0x244/0x2d8 [radeon] : [<f7bd5ca7>] ? radeon_fence_wait+0x244/0x2d8 [radeon] : [<c04420fd>] warn_slowpath_fmt+0x33/0x35 : [<f7bd5ca7>] radeon_fence_wait+0x244/0x2d8 [radeon] : [<c0459005>] ? autoremove_wake_function+0x0/0x39 : [<f7bd62d8>] radeon_sync_obj_wait+0x11/0x13 [radeon] : [<f7adf469>] ttm_bo_wait+0xae/0x151 [ttm] : [<f7be5422>] radeon_bo_wait+0x6e/0x8d [radeon] : [<f7be5961>] radeon_gem_wait_idle_ioctl+0x2f/0x59 [radeon] : [<f7a8345f>] drm_ioctl+0x2a4/0x38a [drm] : [<f7be5932>] ? radeon_gem_wait_idle_ioctl+0x0/0x59 [radeon] : [<c05d5868>] ? prio_tree_insert+0x13d/0x1be : [<c04c2f6f>] ? vma_prio_tree_insert+0x1f/0x31 : [<c059ce80>] ? file_has_perm+0x9a/0xb3 : [<f7a831bb>] ? drm_ioctl+0x0/0x38a [drm] : [<c04f9e7d>] do_vfs_ioctl+0x451/0x482 : [<c059d0f1>] ? selinux_file_ioctl+0x39/0x3c : [<c04f9ef6>] sys_ioctl+0x48/0x6a : [<c040969f>] sysenter_do_call+0x12/0x28 event_log: :2011-05-11-00:40:46> Submitting oops report to http://submit.kerneloops.org/submitoops.php :2011-05-11-00:40:48 Kernel oops report was uploaded
/me wonders why the subject says "TAINTED Warning Issued" when the body correctly says "Not tainted".
*** Bug 714371 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > /me wonders why the subject says "TAINTED Warning Issued" when the body > correctly says "Not tainted". Oh nice, abrt is checking the tainted flags *after* the warning is issued. So it will always report the kernel as tainted...
Can we get hw description (gpu, cpu, motherboard) Kernel log + Xorg log
I have only seen this once. I don't have much video memory, so when I attach an external display then gnome shell used to fall back to compatibility mode or mess graphic up so I had to reboot. This crash might be related to these situations. I like gnome shell and have thus stopped using an external display - that might explain why I haven't seen it again. (The latest update to kernel-PAE-2.6.38.8-32.fc15.i686 fixed some strange redraw errors on boot, so everything looks fine now without external display.) http://www.smolts.org/client/show/pub_6ee23250-8a78-44b8-a4ec-9a0b999ebbe1 says M22 [Mobility Radeon X300]
Created attachment 510179 [details] current dmesg
Created attachment 510180 [details] current Xorg.0.log
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. **
Thank you for taking the time to report this bug. Updates to this package have been released since it was first reported. If you have time to update the package and re-test, please do so and report the results here. You can obtain the updated package by typing 'yum update <package>' or using the graphical updater, Software Update. Thank you, --- Jason Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I haven't seen it again.