Re: radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec
From: Antti Palosaari
Date: Wed Jan 02 2013 - 12:59:29 EST
On 01/02/2013 07:19 PM, Jerome Glisse wrote:
On Wed, Jan 2, 2013 at 7:02 AM, Borislav Petkov <bp@xxxxxxxxx> wrote:
On Wed, Jan 02, 2013 at 03:42:20AM +0200, Antti Palosaari wrote:
I ended up also that same commit after bisecting from current 3.8
01:05.0 VGA compatible controller: ATI Technologies Inc 760G [Radeon
3000] It is ASUS M5A78L-M/USB3 with integrated GPU.
I cannot even boot unless graphical boot is removed from Fedora 17
boot options (rhgb quiet). Random GPU crashes still.
You could try the temporary R600-only fix although I can't see whether
your GPU is also an R600 ASIC or something different by staring at the
model string above:
How do you trigger the issue ? Does it happens right away on boot ?
Sorry for utterly unclear description. I meant it randomly crashes
desktop in case I got it booting by removing graphical boot option. In
that case Cinnamon desktop "freezes", I was able to move mouse cursor
but clicking buttons or moving windows etc. didn't worked at all. Only
mouse cursor moves. It was possible to switch to console by ctrl+alt+fN.
When Fedora graphical boot was enabled (options rhgb quiet) and I
selected Kernel from the grub, it makes just blank screen and after
10sec or so monitor switches off saying "no signal". Nothing happened
after that, boot was forced. I use dm-crypt and normally about the first
thing is to show is graphical lock screen asking passphrase.
I did some grepping from the syslog and that same message is seen:
Jan 2 03:35:34 localhost kernel: [ 1164.433117] radeon 0000:01:05.0:
GPU lockup CP stall for more than 10000msec
Jan 2 03:35:34 localhost kernel: [ 1164.433121] radeon 0000:01:05.0:
GPU lockup (waiting for 0x0000000000000003 last fence id 0x0000000000000002)
After I reverted bisected patch it has been working just fine. I has
been running whole day without problems.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/