Hide Forgot
abrt version: 2.0.1 architecture: i686 cmdline: ro root=UUID=0006b7ec-49bd-42b6-bee4-834ca1f492b7 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet component: kernel kernel: 2.6.38.6-27.fc15.i686 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+0x248/0x2bb [radeon]() time: Wed Jun 8 00:29:55 2011 backtrace: :WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:248 radeon_fence_wait+0x248/0x2bb [radeon]() :Hardware name: Aspire 4253 :GPU lockup (waiting for 0x000ABFC8 last fence id 0x000ABFC7) :Modules linked in: vfat fat fuse 8021q garp stp llc cpufreq_ondemand powernow_k8 mperf ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables snd_hda_codec_conexant snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device sparse_keymap snd_pcm rfkill snd_timer microcode uvcvideo joydev serio_raw k10temp sp5100_tco wmi snd videodev soundcore atl1c i2c_piix4 snd_page_alloc ipv6 video radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan] :Pid: 959, comm: Xorg Not tainted 2.6.38.6-27.fc15.i686 #1 :Call Trace: : [<c043aa69>] warn_slowpath_common+0x7c/0x91 : [<f7a17a3f>] ? radeon_fence_wait+0x248/0x2bb [radeon] : [<f7a17a3f>] ? radeon_fence_wait+0x248/0x2bb [radeon] : [<c043ab09>] warn_slowpath_fmt+0x33/0x35 : [<f7a17a3f>] radeon_fence_wait+0x248/0x2bb [radeon] : [<c04515f5>] ? autoremove_wake_function+0x0/0x39 : [<f7a18028>] radeon_sync_obj_wait+0x11/0x13 [radeon] : [<f7921461>] ttm_bo_wait+0xae/0x151 [ttm] : [<c05ce662>] ? put_dec+0x2f/0x6d : [<f7922ee3>] ttm_bo_move_buffer+0x5b/0xf0 [ttm] : [<c05ce7f9>] ? number+0x159/0x249 : [<c0436624>] ? load_balance+0x99/0x5a9 : [<f7923035>] ttm_bo_validate+0xbd/0xf4 [ttm] : [<f7a19029>] radeon_bo_pin+0x7e/0xc9 [radeon] : [<f7a0f03d>] dce4_crtc_do_set_base+0xa1/0x3cf [radeon] : [<f7a0f3ee>] atombios_crtc_set_base+0x37/0x50 [radeon] : [<f7903fcf>] drm_crtc_helper_set_config+0x723/0x831 [drm_kms_helper] : [<f78ce0b9>] ? drm_get_connector_name+0x42/0x49 [drm] : [<f78cfdbc>] drm_mode_setcrtc+0x341/0x367 [drm] : [<c042800f>] ? should_resched+0xd/0x27 : [<f78c53bb>] drm_ioctl+0x2a4/0x38a [drm] : [<c06864a2>] ? proc_scsi_write_proc+0x21/0x7a : [<f78cfa7b>] ? drm_mode_setcrtc+0x0/0x367 [drm] : [<c06864a2>] ? proc_scsi_write_proc+0x21/0x7a : [<f78c5117>] ? drm_ioctl+0x0/0x38a [drm] : [<c04f09ed>] do_vfs_ioctl+0x451/0x482 : [<c06864a2>] ? proc_scsi_write_proc+0x21/0x7a : [<c0593e65>] ? selinux_file_ioctl+0x39/0x3c : [<c06864a2>] ? proc_scsi_write_proc+0x21/0x7a : [<c04f0a66>] sys_ioctl+0x48/0x6a : [<c07d66b4>] syscall_call+0x7/0xb : [<c06864a2>] ? proc_scsi_write_proc+0x21/0x7a : [<c06864a2>] ? proc_scsi_write_proc+0x21/0x7a
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. Also, what desktop environment you use (KDE, Gnome, something else)? We will review this issue again once you've had a chance to attach this information. Thanks in advance.
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. **
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. Thank you. --- Jason Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers