From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 62721] New: GPU lockup: radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec...
Date: Tue, 08 Oct 2013 13:03:03 +0000 [thread overview]
Message-ID: <bug-62721-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=62721
Bug ID: 62721
Summary: GPU lockup: radeon 0000:01:00.0: GPU lockup CP stall
for more than 10000msec...
Product: Drivers
Version: 2.5
Kernel Version: 3.11.4
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: egorov_egor@bk.ru
Regression: No
After update kernel to 3.11.4 my system randomize hands:
Oct 08 19:09:32 localhost kernel: radeon 0000:01:00.0: GPU lockup CP stall for
more than 10000msec
Oct 08 19:09:32 localhost kernel: radeon 0000:01:00.0: GPU lockup (waiting for
0x000000000000a2f1 last fence id 0x000000000000a2f0)
Oct 08 19:09:32 localhost kernel: Failed to wait GUI idle while programming
pipes. Bad things might happen.
Oct 08 19:09:32 localhost kernel: radeon 0000:01:00.0: Saved 27 dwords of
commands on ring 0.
Oct 08 19:09:33 localhost kernel: radeon 0000:01:00.0: (rs600_asic_reset:401)
RBBM_STATUS=0xD4110140
Oct 08 19:09:33 localhost kernel: radeon 0000:01:00.0: (rs600_asic_reset:421)
RBBM_STATUS=0x90010140
Oct 08 19:09:34 localhost kernel: radeon 0000:01:00.0: (rs600_asic_reset:429)
RBBM_STATUS=0x10000140
Oct 08 19:09:34 localhost kernel: radeon 0000:01:00.0: (rs600_asic_reset:437)
RBBM_STATUS=0x10000140
Oct 08 19:09:34 localhost kernel: radeon 0000:01:00.0: GPU reset succeed
Oct 08 19:09:34 localhost kernel: radeon 0000:01:00.0: GPU reset succeeded,
trying to resume
Oct 08 19:09:34 localhost kernel: radeon 0000:01:00.0: ffff880224f0f800 unpin
not necessary
Oct 08 19:09:39 localhost kernel: [drm:atom_op_jump] *ERROR* atombios stuck in
loop for more than 5secs aborting
Oct 08 19:09:39 localhost kernel: [drm:atom_execute_table_locked] *ERROR*
atombios stuck executing BA17 (len 676, WS 4, PS 0) @ 0xBC1E
Oct 08 19:09:39 localhost kernel: [drm:atom_execute_table_locked] *ERROR*
atombios stuck executing B948 (len 200, WS 0, PS 8) @ 0xB950
Oct 08 19:09:39 localhost kernel: Failed to wait GUI idle while programming
pipes. Bad things might happen.
Oct 08 19:09:39 localhost kernel: [drm] radeon: 3 quad pipes, 1 z pipes
initialized.
Oct 08 19:09:40 localhost kernel: Failed to wait MC idle while programming
pipes. Bad things might happen.
Oct 08 19:09:40 localhost kernel: [drm] PCIE GART of 512M enabled (table at
0x0000000000040000).
Oct 08 19:09:40 localhost kernel: radeon 0000:01:00.0: WB enabled
Oct 08 19:09:40 localhost kernel: radeon 0000:01:00.0: fence driver on ring 0
use gpu addr 0x0000000010000000 and cpu addr 0xffff880224965000
Oct 08 19:09:40 localhost kernel: [drm] radeon: ring at 0x0000000010001000
Oct 08 19:09:40 localhost kernel: [drm:r100_ring_test] *ERROR* radeon: ring
test failed (scratch(0x15E8)=0xCAFEDEAD)
Oct 08 19:09:40 localhost kernel: [drm:r100_cp_init] *ERROR* radeon: cp isn't
working (-22).
Oct 08 19:09:40 localhost kernel: radeon 0000:01:00.0: failed initializing CP
(-22).
after revert commit cb51bb7107aa040f9779be931e3bd6a7b50e0f69 all works fine.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2013-10-08 13:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 13:03 bugzilla-daemon [this message]
2013-10-08 13:03 ` [Bug 62721] GPU lockup: radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec bugzilla-daemon
2013-10-08 17:54 ` bugzilla-daemon
2013-10-09 3:40 ` bugzilla-daemon
2013-10-09 13:15 ` bugzilla-daemon
2013-10-10 17:12 ` bugzilla-daemon
2013-10-10 17:13 ` bugzilla-daemon
2013-10-14 13:52 ` bugzilla-daemon
2014-01-16 4:14 ` bugzilla-daemon
2014-01-16 4:15 ` bugzilla-daemon
2014-01-16 4:15 ` bugzilla-daemon
2014-01-16 4:25 ` bugzilla-daemon
2014-01-18 4:28 ` bugzilla-daemon
2014-10-10 12:06 ` bugzilla-daemon
2014-10-10 12:09 ` bugzilla-daemon
2014-10-21 14:28 ` bugzilla-daemon
2014-10-21 14:32 ` bugzilla-daemon
2015-02-17 18:54 ` bugzilla-daemon
2015-02-20 10:14 ` 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-62721-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.