public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: Borislav Petkov <bp@alien8.de>, Shuah Khan <shuahkhan@gmail.com>,
	Markus Trippelsdorf <markus@trippelsdorf.de>,
	Andy Furniss <andyqos@ukfsn.org>,
	Alex Deucher <alexdeucher@gmail.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	dri-devel@lists.freedesktop.org,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec
Date: Wed, 02 Jan 2013 19:58:54 +0200	[thread overview]
Message-ID: <50E4755E.7030209@iki.fi> (raw)
In-Reply-To: <CAH3drwYSrfsbKg-BYpMF3Nkxrw1toK=EmcvJfKGzdbT_BK-1HQ@mail.gmail.com>

On 01/02/2013 07:19 PM, Jerome Glisse wrote:
> On Wed, Jan 2, 2013 at 7:02 AM, Borislav Petkov <bp@alien8.de> 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
>>> master.
>>>
>>> 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:
>>
>> http://marc.info/?l=dri-devel&m=135628734704029
>>
>> HTH.
>>
>> --
>> Regards/Gruss,
>> Boris.
>
> How do you trigger the issue ? Does it happens right away on boot ?
>
> Cheers,
> Jerome

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.

regards
Antti

-- 
http://palosaari.fi/

  reply	other threads:[~2013-01-02 17:59 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-22 20:35 radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec Borislav Petkov
2012-12-23  0:01 ` Alex Deucher
2012-12-23  0:25   ` Borislav Petkov
2012-12-23  0:42     ` Alex Deucher
2012-12-23 10:55       ` Borislav Petkov
2012-12-23 11:01         ` Andy Furniss
2012-12-23 11:07           ` Borislav Petkov
2012-12-23 11:19             ` Andy Furniss
2012-12-23 11:31               ` Borislav Petkov
2012-12-23 11:51                 ` Markus Trippelsdorf
2012-12-23 12:22                   ` Borislav Petkov
2012-12-23 13:31                     ` Borislav Petkov
2012-12-25  4:50                       ` Shuah Khan
2012-12-25 10:54                         ` Borislav Petkov
2013-01-02  1:42                         ` Antti Palosaari
2013-01-02 12:02                           ` Borislav Petkov
2013-01-02 17:19                             ` Jerome Glisse
2013-01-02 17:58                               ` Antti Palosaari [this message]
2013-01-02 22:31                                 ` Jerome Glisse
2013-01-02 22:38                                   ` Markus Trippelsdorf
2013-01-02 23:37                                     ` Alex Deucher
2013-01-02 23:58                                       ` Shuah Khan
2013-01-02 23:59                                         ` Alex Deucher
2013-01-03  1:03                                           ` Antti Palosaari
2013-01-03  1:05                                           ` Shuah Khan
2013-01-03  8:33                                       ` Markus Trippelsdorf
2013-01-03 11:37                                       ` Boszormenyi Zoltan
2013-01-03 14:12                                         ` Deucher, Alexander
2013-01-03 15:30                                           ` Shuah Khan
2013-01-04  7:40                                       ` Borislav Petkov
2013-01-04 11:16                                         ` Boszormenyi Zoltan
2013-01-04 14:06                                           ` Alex Deucher
2012-12-23 11:52           ` Joe Perches
  -- strict thread matches above, loose matches on Subject: below --
2013-01-10  9:38 Borislav Petkov
2013-01-10 16:21 ` Alex Deucher
2013-01-10 20:32   ` Borislav Petkov
2013-01-10 20:47     ` Alex Deucher
2013-01-11 11:43       ` Borislav Petkov
2013-01-15 12:19         ` Borislav Petkov
2013-01-15 14:04           ` Alex Deucher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50E4755E.7030209@iki.fi \
    --to=crope@iki.fi \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=andyqos@ukfsn.org \
    --cc=bp@alien8.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=j.glisse@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    --cc=shuahkhan@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox