Bug 889872 - GPU lockup (ATI Radeon HD 3650, RV635)
Summary: GPU lockup (ATI Radeon HD 3650, RV635)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 18
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-23 18:32 UTC by Mattia M.
Modified: 2014-02-05 14:09 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 14:09:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
A part of /var/log/messages related to this bug (kernel 3.6.11-3.fc18.x86_64). (5.91 KB, application/octet-stream)
2012-12-23 18:32 UTC, Mattia M.
no flags Details
A part of /var/log/messages related to this bug (kernel-3.7.0-6.fc19.x86_64). (2.76 KB, text/plain)
2012-12-28 07:21 UTC, Mattia M.
no flags Details
Xorg.0.log (case kernel-3.7.0-6.fc19.x86_64). (49.38 KB, text/plain)
2013-01-02 07:41 UTC, Mattia M.
no flags Details

Description Mattia M. 2012-12-23 18:32:49 UTC
Created attachment 668098 [details]
A part of /var/log/messages related to this bug (kernel 3.6.11-3.fc18.x86_64).

Description of problem:
Sometimes, while using GNOME Shell (i.e., switching from the dektop to the "activities overview" screen) and in other circumstances (i.e., a few seconds after starting a match with the game "0 A.D."), the system suddenly becomes unresponsive; then, a few seconds later, the screen turn off and on again in quick sequence. After some seconds, the screen turns off and on again, and so on.
Since I cannot even restart the X server through Ctrl+Alt+Backspace, I can do nothing else than turning down and restarting my computer.
The system logs state that a "GPU lockup" (see attachments) is the reason for the above behaviour.

Version-Release number of selected component (if applicable): 3.6.11-3.fc18.x86_64


How reproducible: 


Steps to Reproduce:
1. Start a match with the game "0 A.D."
2. Wait a few seconds
or
1. Employ GNOME Shell (e.g., switch from the desktop to the "Activities overview" screen)
2. The issue could occur sometime.
  
Actual results:
The system suddenly becomes unresponsive; then, a few seconds later, the screen turn off and on again in quick sequence. After some seconds, the screen turns off and on again, and so on.
Since I cannot even restart the X server through Ctrl+Alt+Backspace, I can do nothing else than turning down and restarting my computer.


Expected results:


Additional info: The attachment is a part of /var/log/messages.

Comment 1 Mattia M. 2012-12-26 09:00:52 UTC
The issue occurs also with kernel 3.6.10-5.fc18.x86_64.
Thus, the above description should be updated as follows:

Version-Release number of selected component (if applicable): 3.6.11-3.fc18.x86_64, 3.6.10-5.fc18.x86_64 (at least)

Comment 2 Mattia M. 2012-12-26 09:06:54 UTC
And, if needed, here's the output of "lspci -nn | grep VGA":

01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV630 [Radeon HD 3600 Series] [1002:9598]

Comment 3 Mattia M. 2012-12-28 07:21:32 UTC
Created attachment 669771 [details]
A part of /var/log/messages related to this bug (kernel-3.7.0-6.fc19.x86_64).

Comment 4 Mattia M. 2012-12-28 07:24:21 UTC
I updated the kernel to version 3.7.0-6.fc19 from the "rawhide" repository, but an issue similar to the on described above still occurs.
The only difference with the above case is that the screen just turns off once and the message "No signal" appears.

Version-Release number of selected component (if applicable): 3.6.11-3.fc18.x86_64, 3.6.10-5.fc18.x86_64, kernel-3.7.0-6.fc19.x86_64

An excerpt of /var/log/messages related to this bug is attached.

Comment 5 Mattia M. 2013-01-02 07:41:35 UTC
Created attachment 671266 [details]
Xorg.0.log (case kernel-3.7.0-6.fc19.x86_64).

Comment 6 plantroon 2013-01-22 16:26:54 UTC
Occurs in fully updated ubuntu 12.10, no custom kernel. GPU lockup when running games. However, when I updated I could run Alien Arena and when finished playing it and opened my browser, I got GPU lockup. I'm using Sapphire Radeon HD 3650 512 MB

Comment 7 Andrea Pasquinucci 2013-03-27 17:09:10 UTC
Happens the same with the following video card (from "lspci -nn | grep VGA")

01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Caicos [Radeon HD 6400M/7400M Series] [1002:6760]

with kernels

kernel-3.8.2-206.fc18.x86_64
kernel-3.8.3-203.fc18.x86_64
kernel-3.8.4-202.fc18.x86_64

works fine instead with kernel-3.7.9-104.fc17.x86_64 (no GPU lockup).

The trigger of the lockup is usually a video game.

Comment 8 Fedora End Of Life 2013-12-21 10:03:50 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is 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  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.

Comment 9 Fedora End Of Life 2014-02-05 14:09:15 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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