From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 88301] Dota causes GPU fault and kernel hang
Date: Thu, 15 Jan 2015 20:06:38 +0000 [thread overview]
Message-ID: <bug-88301-502-YQ2oe5hMsR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-88301-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2442 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=88301
--- Comment #2 from Tilman Sauerbeck <tilman@code-monkey.de> ---
Sorry about that misinformation.
It's not a hang at all since I'm still able to use sysrq to reboot.
What's happening after the GPU faults is that apparently the driver attempts to
get the card back into working shape, but fails to do so. X doesn't become
usable again after the GPU faults anyway.
Here's the kernel log following the GPU faults:
radeon 0000:01:00.0: ring 0 stalled for more than 10428msec
radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000107f5c last fence
id 0x00000000001080f7 on ring 0)
radeon 0000:01:00.0: failed to get a new IB (-35)
[drm:radeon_cs_ib_fill] *ERROR* Failed to get ib !
radeon 0000:01:00.0: Saved 7977 dwords of commands on ring 0.
radeon 0000:01:00.0: GPU softreset: 0x00000009
[snipped list of registers that were reset (I think)]
[drm] probing gen 2 caps for device 1002:5a16 = 31cd02/0
[drm] PCIE gen 2 link speeds already enabled
[drm] PCIE GART of 1024M enabled (table at 0x000000000078C000).
radeon 0000:01:00.0: WB enabled
radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and
cpu addr 0xffff8800bac4cc00
radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and
cpu addr 0xffff8800bac4cc04
radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and
cpu addr 0xffff8800bac4cc08
radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and
cpu addr 0xffff8800bac4cc0c
radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and
cpu addr 0xffff8800bac4cc10
radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000076c98 and
cpu addr 0xffffc90010c36c98
radeon 0000:01:00.0: fence driver on ring 6 use gpu addr 0x0000000080000c18 and
cpu addr 0xffff8800bac4cc18
radeon 0000:01:00.0: fence driver on ring 7 use gpu addr 0x0000000080000c1c and
cpu addr 0xffff8800bac4cc1c
[drm] ring test on 0 succeeded in 3 usecs
[drm:cik_ring_test] *ERROR* radeon: ring 1 test failed
(scratch(0x3010C)=0xCAFEDEAD)
[drm:cik_ring_test] *ERROR* radeon: ring 2 test failed
(scratch(0x3010C)=0xCAFEDEAD)
[drm:cik_sdma_ring_test] *ERROR* radeon: ring 3 test failed (0xCAFEDEAD)
[drm:cik_resume] *ERROR* cik startup failed on resume
[drm:radeon_pm_resume_dpm] *ERROR* radeon: dpm resume failed
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-01-15 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-11 20:17 [Bug 88301] Dota causes GPU fault and kernel hang bugzilla-daemon
2015-01-15 7:43 ` bugzilla-daemon
2015-01-15 20:06 ` bugzilla-daemon [this message]
2015-01-15 21:45 ` bugzilla-daemon
2015-01-16 6:54 ` bugzilla-daemon
2015-01-30 16:24 ` bugzilla-daemon
2015-01-30 18:26 ` 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-88301-502-YQ2oe5hMsR@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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