Bug 701015 - [BARTS] GPU lockup
Summary: [BARTS] GPU lockup
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 15
Hardware: x86_64
OS: Unspecified
medium
low
Target Milestone: ---
Assignee: Jérôme Glisse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:241946d074b10fa09a6981059f9...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-30 12:06 UTC by Francois-Xavier GSELL
Modified: 2018-04-11 09:21 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 19:19:42 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (2.12 KB, text/plain)
2011-04-30 12:06 UTC, Francois-Xavier GSELL
no flags Details
dmesg (70.34 KB, text/plain)
2011-05-11 14:56 UTC, Yuta Kobayashi
no flags Details
Xorg.0.log (68.02 KB, text/plain)
2011-05-11 14:58 UTC, Yuta Kobayashi
no flags Details

Description Francois-Xavier GSELL 2011-04-30 12:06:01 UTC
abrt version: 2.0.1
cmdline: ro root=/dev/mapper/vg_keskonrix-lv_root rd_LVM_LV=vg_keskonrix/lv_root rd_LVM_LV=vg_keskonrix/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
component: kernel
kernel: 2.6.38.4-20.fc15.x86_64
kernel_tainted: 512
reason: WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:248 radeon_fence_wait+0x2a8/0x32b [radeon]()
architecture: x86_64
package: kernel
os_release: Fedora release 15 (Lovelock)
time: 1304164838

Text file: backtrace, 2175 bytes

Comment 1 Francois-Xavier GSELL 2011-04-30 12:06:04 UTC
Created attachment 495947 [details]
File: backtrace

Comment 2 Jérôme Glisse 2011-05-09 18:47:34 UTC
It's just a GPU lockup, please attach full dmesg and give description of what kind of activities trigger this message (if any).

Comment 3 Matěj Cepl 2011-05-10 20:47:40 UTC
/var/log/Xorg.0.log would be helpful as well, please.

Thank you

Comment 4 Yuta Kobayashi 2011-05-11 14:56:45 UTC
Created attachment 498312 [details]
dmesg

And he has the same symptoms too.
The reporter, but attached for reference.
If you have any other information required, please let me know.
(because English is not good, I'm using the automatic translation. I'm sorry)

Comment 5 Yuta Kobayashi 2011-05-11 14:58:10 UTC
Created attachment 498314 [details]
Xorg.0.log

this is Xorg.0.log
Thank you.

Comment 6 Jason Smith 2012-05-12 14:10:03 UTC
Upon review of attached logs, marked bug as triaged for further review.  Our thanks for these logs for review of this bug.



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

Comment 7 Fedora End Of Life 2012-08-07 19:19:45 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.