dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 85421] New: radeon stalled, GPU lockup, reset and failed on resume; crashed by firefox.
Date: Wed, 01 Oct 2014 23:21:23 +0000	[thread overview]
Message-ID: <bug-85421-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=85421

            Bug ID: 85421
           Summary: radeon stalled, GPU lockup, reset and failed on
                    resume; crashed by firefox.
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.16.3
          Hardware: x86-64
                OS: Linux
              Tree: Fedora
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: htl10@users.sourceforge.net
        Regression: No

Created attachment 152191
  --> https://bugzilla.kernel.org/attachment.cgi?id=152191&action=edit
/var/log/messages from radeon 0000:00:01.0: ring 0 stalled to reboot.

I was away from the computer when the radeon dri driver crashed; I left a fair
number of firefox windows on/tab, some of them may have videos (from BBC news
web site) and animated gifs from another web site on; but it crashed about 5-10
minutes after I was away and I was aware of it because the laptop blipped.

# lspci | grep VGA
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Mullins [Radeon R3 Graphics]

some excerpt from the attached logs are:

...
 [ 8770.250116] radeon 0000:00:01.0: ring 0 stalled for more than 10012msec
 [ 8770.250128] radeon 0000:00:01.0: GPU lockup (waiting for 0x0000000000056034
last fence id 0x0000000000056031 on ring 0)
 [ 8770.298635] radeon 0000:00:01.0: Saved 14196 dwords of commands on ring 0.
 [ 8770.298663] radeon 0000:00:01.0: GPU softreset: 0x0000000C
...
 [ 8770.313299] radeon 0000:00:01.0: GPU reset succeeded, trying to resume
...
 [ 8770.339724] [drm] ring test on 0 succeeded in 3 usecs
 [ 8770.518568] [drm:cik_ring_test] *ERROR* radeon: ring 1 test failed
(scratch(0x3010C)=0xCAFEDEAD)
 [ 8770.752885] [drm:cik_sdma_ring_test] *ERROR* radeon: ring 3 test failed
(0xCAFEDEAD)
 [ 8770.752892] [drm:cik_resume] *ERROR* cik startup failed on resume
 [ 8780.753181] radeon 0000:00:01.0: ring 0 stalled for more than 10001msec
 [ 8780.753193] radeon 0000:00:01.0: GPU lockup (waiting for 0x00000000000560f7
last fence id 0x0000000000056031 on ring 0)
 [ 8780.753199] [drm:cik_ib_test] *ERROR* radeon: fence wait failed (-35).
 [ 8780.753209] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on
GFX ring (-35).
 [ 8780.753215] radeon 0000:00:01.0: ib ring test failed (-35).
 [ 8780.762131] radeon 0000:00:01.0: GPU softreset: 0x0000000C
...


The kernel is a largely fedora 3.16.3-200 one grabbed from the koji srpm but
with the additional patch from
https://bugzilla.kernel.org/show_bug.cgi?id=71051#c8

drv ati 7.4.0 , mesa 10.2.8, glamor from git 347ef4 .

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2014-10-01 23:21 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01 23:21 bugzilla-daemon [this message]
2014-10-07 21:41 ` [Bug 85421] radeon stalled, GPU lockup, reset and failed on resume; crashed by firefox bugzilla-daemon
2014-10-08 12:28 ` bugzilla-daemon
2014-10-13 15:41 ` bugzilla-daemon
2014-10-13 16:09 ` bugzilla-daemon
2014-10-13 16:37 ` bugzilla-daemon
2014-10-13 21:28 ` bugzilla-daemon
2014-10-23 15:50 ` bugzilla-daemon
2014-10-28  9:52 ` bugzilla-daemon
2014-10-29  1:06 ` bugzilla-daemon
2014-11-09  9:48 ` bugzilla-daemon
2014-11-09  9:51 ` bugzilla-daemon
2014-11-21 22:33 ` bugzilla-daemon
2014-11-28 20:30 ` bugzilla-daemon
2014-12-01  2:13 ` bugzilla-daemon
2014-12-01  3:07 ` bugzilla-daemon
2014-12-05  0:35 ` bugzilla-daemon
2014-12-05  7:47 ` bugzilla-daemon
2014-12-10 22:35 ` bugzilla-daemon
2014-12-12  9:54 ` bugzilla-daemon
2014-12-16 17:18 ` bugzilla-daemon
2014-12-17  2:19 ` bugzilla-daemon
2014-12-17 20:07 ` bugzilla-daemon
2014-12-18  6:03 ` bugzilla-daemon
2014-12-18 19:40 ` bugzilla-daemon
2014-12-19  3:23 ` bugzilla-daemon
2015-01-24  1:08 ` bugzilla-daemon
2015-02-09 16:43 ` bugzilla-daemon
2015-02-09 16:48 ` bugzilla-daemon
2015-02-14 15:29 ` bugzilla-daemon
2015-02-24 23:48 ` bugzilla-daemon
2015-03-17  5:16 ` bugzilla-daemon
2015-03-17  5:21 ` bugzilla-daemon
2015-03-23 14:50 ` bugzilla-daemon
2015-03-23 23:08 ` bugzilla-daemon
2015-03-24 14:29 ` bugzilla-daemon
2015-03-24 15:39 ` bugzilla-daemon
2015-03-24 16:19 ` bugzilla-daemon
2015-03-25  3:50 ` bugzilla-daemon
2015-03-25  9:41 ` bugzilla-daemon
2015-04-26  2:11 ` bugzilla-daemon
2021-09-24 18:28 ` bugzilla-daemon

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=bug-85421-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /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