From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 78661] New: GPU sometimes locks up after boot and/or resume
Date: Sun, 22 Jun 2014 09:34:26 +0000 [thread overview]
Message-ID: <bug-78661-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=78661
Bug ID: 78661
Summary: GPU sometimes locks up after boot and/or resume
Product: Drivers
Version: 2.5
Kernel Version: 3.15.1
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: madigens@gmail.com
Regression: No
I've been getting these hangs since at least 3.13.x on Ubuntu 14.04, but I
remember getting them before that, too.
It doesn't always happen, mostly the system works as usual. Sometimes though, I
boot up or resume and upon opening an application or moving the mouse, I get a
garbled screen, after a few seconds it goes back to normal, only to hang
shortly thereafter again or hang completely. I can't remember this happening
during normal use, meaning if it doesn't happen shortly after boot or resume,
the system works fine.
I cut some suspicious lines from syslog:
Jun 22 10:31:40 nikolaus-desktop kernel: [ 86.067026] radeon 0000:01:00.0:
ring 5 stalled for more than 81420msec
Jun 22 10:31:40 nikolaus-desktop kernel: [ 86.067034] radeon 0000:01:00.0:
GPU lockup (waiting for 0x0000000000000001 last fence id 0x0000000000000000 on
ring 5)
Jun 22 10:31:41 nikolaus-desktop kernel: [ 86.929541] radeon 0000:01:00.0:
GPU reset succeeded, trying to resume
Jun 22 10:31:41 nikolaus-desktop kernel: [ 86.986723] [drm] PCIE gen 2 link
speeds already enabled
Jun 22 10:31:41 nikolaus-desktop kernel: [ 86.988854] [drm] PCIE GART of
1024M enabled (table at 0x000000000025D000).
Jun 22 10:31:41 nikolaus-desktop kernel: [ 86.988930] radeon 0000:01:00.0: WB
enabled
Jun 22 10:31:41 nikolaus-desktop kernel: [ 86.988932] radeon 0000:01:00.0:
fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr
0xffff8800d9752c00
Jun 22 10:31:41 nikolaus-desktop kernel: [ 86.988933] radeon 0000:01:00.0:
fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr
0xffff8800d9752c0c
Jun 22 10:31:41 nikolaus-desktop kernel: [ 86.989307] radeon 0000:01:00.0:
fence driver on ring 5 use gpu addr 0x000000000005c418 and cpu addr
0xffffc90004f9c418
Jun 22 10:31:41 nikolaus-desktop kernel: [ 87.005388] [drm] ring test on 0
succeeded in 1 usecs
Jun 22 10:31:41 nikolaus-desktop kernel: [ 87.005442] [drm] ring test on 3
succeeded in 1 usecs
Jun 22 10:31:41 nikolaus-desktop kernel: [ 87.200919] [drm] ring test on 5
succeeded in 1 usecs
Jun 22 10:31:41 nikolaus-desktop kernel: [ 87.200923] [drm] UVD initialized
successfully.
Jun 22 10:31:41 nikolaus-desktop kernel: [ 87.200941] [drm] ib test on ring 0
succeeded in 0 usecs
Jun 22 10:31:41 nikolaus-desktop kernel: [ 87.200959] [drm] ib test on ring 3
succeeded in 1 usecs
Jun 22 10:31:42 nikolaus-desktop kernel: [ 87.370683] [drm:uvd_v1_0_ib_test]
*ERROR* radeon: failed to get create msg (-22).
Jun 22 10:31:42 nikolaus-desktop kernel: [ 87.370688]
[drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5 (-22).
Jun 22 10:31:42 nikolaus-desktop kernel: [ 87.370708]
[drm:radeon_pm_resume_dpm] *ERROR* radeon: dpm resume failed
Jun 22 10:31:52 nikolaus-desktop kernel: [ 98.016760] radeon 0000:01:00.0:
ring 5 stalled for more than 10000msec
Jun 22 10:31:52 nikolaus-desktop kernel: [ 98.016768] radeon 0000:01:00.0:
GPU lockup (waiting for 0x0000000000000001 last fence id 0x0000000000000000 on
ring 5)
Jun 22 10:45:27 nikolaus-desktop kernel: [ 912.669107] radeon 0000:01:00.0:
GPU reset succeeded, trying to resume
Jun 22 10:45:27 nikolaus-desktop kernel: [ 912.725911] [drm] PCIE gen 2 link
speeds already enabled
Jun 22 10:45:27 nikolaus-desktop kernel: [ 912.727900] [drm] PCIE GART of
1024M enabled (table at 0x000000000025D000).
Jun 22 10:45:27 nikolaus-desktop kernel: [ 912.727974] radeon 0000:01:00.0: WB
enabled
Jun 22 10:45:27 nikolaus-desktop kernel: [ 912.727976] radeon 0000:01:00.0:
fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr
0xffff8800d9752c00
Jun 22 10:45:27 nikolaus-desktop kernel: [ 912.727977] radeon 0000:01:00.0:
fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr
0xffff8800d9752c0c
Jun 22 10:45:27 nikolaus-desktop kernel: [ 912.728365] radeon 0000:01:00.0:
fence driver on ring 5 use gpu addr 0x000000000005c418 and cpu addr
0xffffc90004f9c418
Jun 22 10:45:27 nikolaus-desktop kernel: [ 912.744428] [drm] ring test on 0
succeeded in 1 usecs
Jun 22 10:45:27 nikolaus-desktop kernel: [ 912.744483] [drm] ring test on 3
succeeded in 1 usecs
Jun 22 10:45:27 nikolaus-desktop kernel: [ 912.940008] [drm] ring test on 5
succeeded in 1 usecs
Jun 22 10:45:27 nikolaus-desktop kernel: [ 912.940012] [drm] UVD initialized
successfully.
Jun 22 10:45:27 nikolaus-desktop kernel: [ 912.940031] [drm] ib test on ring 0
succeeded in 0 usecs
Jun 22 10:45:27 nikolaus-desktop kernel: [ 912.940050] [drm] ib test on ring 3
succeeded in 1 usecs
Jun 22 10:45:27 nikolaus-desktop kernel: [ 913.109743] [drm:uvd_v1_0_ib_test]
*ERROR* radeon: failed to get create msg (-22).
Jun 22 10:45:27 nikolaus-desktop kernel: [ 913.109748]
[drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5 (-22).
Jun 22 10:45:27 nikolaus-desktop kernel: [ 913.109763]
[drm:radeon_pm_resume_dpm] *ERROR* radeon: dpm resume failed
What else do you need from me?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2014-06-22 9:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 9:34 bugzilla-daemon [this message]
2014-06-22 9:38 ` [Bug 78661] GPU sometimes locks up after boot and/or resume bugzilla-daemon
2014-06-23 14:49 ` bugzilla-daemon
2014-06-24 14:35 ` bugzilla-daemon
2014-06-24 14:39 ` bugzilla-daemon
2014-07-01 23:38 ` bugzilla-daemon
2014-07-02 1:06 ` bugzilla-daemon
2014-07-03 15:09 ` bugzilla-daemon
2014-07-08 14:44 ` bugzilla-daemon
2014-07-08 15:23 ` bugzilla-daemon
2014-07-08 18:40 ` bugzilla-daemon
2014-07-09 23:28 ` bugzilla-daemon
2014-07-10 12:59 ` bugzilla-daemon
2014-07-13 14:51 ` bugzilla-daemon
2014-07-21 4:25 ` bugzilla-daemon
2014-08-19 16:47 ` bugzilla-daemon
2015-03-25 18:05 ` 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-78661-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.