From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 62721] GPU lockup: radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec...
Date: Tue, 17 Feb 2015 18:54:22 +0000 [thread overview]
Message-ID: <bug-62721-2300-8qYxeYh0QE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-62721-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=62721
info@maciejgluszek.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |info@maciejgluszek.com
--- Comment #17 from info@maciejgluszek.com ---
Same thing happens for me with Ubuntu 14.04.2 and ATI HD3650 GPU, ctrl+alt+fx
works fine. Switching back to desktop alt+7 also works but screen is flickering
and not responding.
Hardware: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
RV635/M86 [Mobility Radeon HD 3650]
Output from syslog when it happens:
Feb 17 19:36:14 lapek kernel: [ 8190.168340] radeon 0000:01:00.0: GPU lockup CP
stall for more than 10048msec
Feb 17 19:36:14 lapek kernel: [ 8190.168355] radeon 0000:01:00.0: GPU lockup
(waiting for 0x0000000000086146 last fence id 0x000000000008611b on ring 0)
Feb 17 19:36:14 lapek kernel: [ 8190.634404] [drm] Disabling audio 0 support
Feb 17 19:36:14 lapek kernel: [ 8190.635449] radeon 0000:01:00.0: Saved 1817
dwords of commands on ring 0.
Feb 17 19:36:14 lapek kernel: [ 8190.635461] radeon 0000:01:00.0: GPU
softreset: 0x00000008
Feb 17 19:36:14 lapek kernel: [ 8190.635463] radeon 0000:01:00.0:
R_008010_GRBM_STATUS = 0xA0003030
Feb 17 19:36:14 lapek kernel: [ 8190.635465] radeon 0000:01:00.0:
R_008014_GRBM_STATUS2 = 0x00000003
Feb 17 19:36:14 lapek kernel: [ 8190.635468] radeon 0000:01:00.0:
R_000E50_SRBM_STATUS = 0x200000C0
Feb 17 19:36:14 lapek kernel: [ 8190.635470] radeon 0000:01:00.0:
R_008674_CP_STALLED_STAT1 = 0x00000000
Feb 17 19:36:14 lapek kernel: [ 8190.635472] radeon 0000:01:00.0:
R_008678_CP_STALLED_STAT2 = 0x00000000
Feb 17 19:36:14 lapek kernel: [ 8190.635474] radeon 0000:01:00.0:
R_00867C_CP_BUSY_STAT = 0x00000002
Feb 17 19:36:14 lapek kernel: [ 8190.635476] radeon 0000:01:00.0:
R_008680_CP_STAT = 0x80000645
Feb 17 19:36:14 lapek kernel: [ 8190.635478] radeon 0000:01:00.0:
R_00D034_DMA_STATUS_REG = 0x44C83D57
Feb 17 19:36:14 lapek kernel: [ 8190.700159] radeon 0000:01:00.0:
R_008020_GRBM_SOFT_RESET=0x00004001
Feb 17 19:36:14 lapek kernel: [ 8190.700213] radeon 0000:01:00.0:
SRBM_SOFT_RESET=0x00000100
Feb 17 19:36:14 lapek kernel: [ 8190.702304] radeon 0000:01:00.0:
R_008010_GRBM_STATUS = 0xA0003030
Feb 17 19:36:14 lapek kernel: [ 8190.702306] radeon 0000:01:00.0:
R_008014_GRBM_STATUS2 = 0x00000003
Feb 17 19:36:14 lapek kernel: [ 8190.702308] radeon 0000:01:00.0:
R_000E50_SRBM_STATUS = 0x200080C0
Feb 17 19:36:14 lapek kernel: [ 8190.702310] radeon 0000:01:00.0:
R_008674_CP_STALLED_STAT1 = 0x00000000
Feb 17 19:36:14 lapek kernel: [ 8190.702312] radeon 0000:01:00.0:
R_008678_CP_STALLED_STAT2 = 0x00000000
Feb 17 19:36:14 lapek kernel: [ 8190.702314] radeon 0000:01:00.0:
R_00867C_CP_BUSY_STAT = 0x00000000
Feb 17 19:36:14 lapek kernel: [ 8190.702316] radeon 0000:01:00.0:
R_008680_CP_STAT = 0x80100000
Feb 17 19:36:14 lapek kernel: [ 8190.702319] radeon 0000:01:00.0:
R_00D034_DMA_STATUS_REG = 0x44C83D57
Feb 17 19:36:14 lapek kernel: [ 8190.702325] radeon 0000:01:00.0: GPU reset
succeeded, trying to resume
Feb 17 19:36:14 lapek kernel: [ 8190.722194] [drm] PCIE GART of 512M enabled
(table at 0x0000000000040000).
Feb 17 19:36:14 lapek kernel: [ 8190.722245] radeon 0000:01:00.0: WB enabled
Feb 17 19:36:14 lapek kernel: [ 8190.722254] radeon 0000:01:00.0: fence driver
on ring 0 use gpu addr 0x0000000010000c00 and cpu addr 0xffff8800bb7cac00
Feb 17 19:36:14 lapek kernel: [ 8190.722261] radeon 0000:01:00.0: fence driver
on ring 3 use gpu addr 0x0000000010000c0c and cpu addr 0xffff8800bb7cac0c
Feb 17 19:36:14 lapek kernel: [ 8190.754017] [drm] ring test on 0 succeeded in
0 usecs
Feb 17 19:36:15 lapek kernel: [ 8190.861611] [drm:r600_dma_ring_test] *ERROR*
radeon: ring 3 test failed (0xCAFEDEAD)
Feb 17 19:36:15 lapek kernel: [ 8190.861618] [drm:r600_resume] *ERROR* r600
startup failed on resume
Feb 17 19:36:18 lapek kernel: [ 8194.054967] Watchdog[2719]: segfault at 0 ip
00007f597fff1756 sp 00007f596f75b770 error 6 in chrome[7f597c302000+510c000]
Feb 17 19:36:25 lapek kernel: [ 8200.860357] radeon 0000:01:00.0: GPU lockup CP
stall for more than 10000msec
Feb 17 19:36:25 lapek kernel: [ 8200.860371] radeon 0000:01:00.0: GPU lockup
(waiting for 0x0000000000086155 last fence id 0x000000000008611c on ring 0)
Feb 17 19:36:25 lapek kernel: [ 8200.860379] [drm:r600_ib_test] *ERROR* radeon:
fence wait failed (-35).
Feb 17 19:36:25 lapek kernel: [ 8200.860390] [drm:radeon_ib_ring_tests] *ERROR*
radeon: failed testing IB on GFX ring (-35).
Feb 17 19:36:25 lapek kernel: [ 8200.860396] radeon 0000:01:00.0: ib ring test
failed (-35).
Feb 17 19:36:25 lapek kernel: [ 8200.861458] radeon 0000:01:00.0: GPU
softreset: 0x00000019
Feb 17 19:36:25 lapek kernel: [ 8200.861465] radeon 0000:01:00.0:
R_008010_GRBM_STATUS = 0xA22034E0
Feb 17 19:36:25 lapek kernel: [ 8200.861471] radeon 0000:01:00.0:
R_008014_GRBM_STATUS2 = 0x00000003
Feb 17 19:36:25 lapek kernel: [ 8200.861476] radeon 0000:01:00.0:
R_000E50_SRBM_STATUS = 0x200000C0
Feb 17 19:36:25 lapek kernel: [ 8200.861482] radeon 0000:01:00.0:
R_008674_CP_STALLED_STAT1 = 0x01000000
Feb 17 19:36:25 lapek kernel: [ 8200.861487] radeon 0000:01:00.0:
R_008678_CP_STALLED_STAT2 = 0x00001002
Feb 17 19:36:25 lapek kernel: [ 8200.861493] radeon 0000:01:00.0:
R_00867C_CP_BUSY_STAT = 0x00028486
Feb 17 19:36:25 lapek kernel: [ 8200.861499] radeon 0000:01:00.0:
R_008680_CP_STAT = 0x80838645
Feb 17 19:36:25 lapek kernel: [ 8200.861504] radeon 0000:01:00.0:
R_00D034_DMA_STATUS_REG = 0x44C83D57
Feb 17 19:36:25 lapek kernel: [ 8200.911232] radeon 0000:01:00.0:
R_008020_GRBM_SOFT_RESET=0x00007FEF
Feb 17 19:36:25 lapek kernel: [ 8200.911290] radeon 0000:01:00.0:
SRBM_SOFT_RESET=0x00000100
Feb 17 19:36:25 lapek kernel: [ 8200.913381] radeon 0000:01:00.0:
R_008010_GRBM_STATUS = 0xA0003030
Feb 17 19:36:25 lapek kernel: [ 8200.913388] radeon 0000:01:00.0:
R_008014_GRBM_STATUS2 = 0x00000003
Feb 17 19:36:25 lapek kernel: [ 8200.913393] radeon 0000:01:00.0:
R_000E50_SRBM_STATUS = 0x200080C0
Feb 17 19:36:25 lapek kernel: [ 8200.913398] radeon 0000:01:00.0:
R_008674_CP_STALLED_STAT1 = 0x00000000
Feb 17 19:36:25 lapek kernel: [ 8200.913404] radeon 0000:01:00.0:
R_008678_CP_STALLED_STAT2 = 0x00000000
Feb 17 19:36:25 lapek kernel: [ 8200.913409] radeon 0000:01:00.0:
R_00867C_CP_BUSY_STAT = 0x00000000
Feb 17 19:36:25 lapek kernel: [ 8200.913415] radeon 0000:01:00.0:
R_008680_CP_STAT = 0x80100000
Feb 17 19:36:25 lapek kernel: [ 8200.913420] radeon 0000:01:00.0:
R_00D034_DMA_STATUS_REG = 0x44C83D57
Feb 17 19:36:25 lapek kernel: [ 8200.913429] radeon 0000:01:00.0: GPU reset
succeeded, trying to resume
Feb 17 19:36:25 lapek kernel: [ 8200.918279] [drm] PCIE GART of 512M enabled
(table at 0x0000000000040000).
Feb 17 19:36:25 lapek kernel: [ 8200.918329] radeon 0000:01:00.0: WB enabled
Feb 17 19:36:25 lapek kernel: [ 8200.918338] radeon 0000:01:00.0: fence driver
on ring 0 use gpu addr 0x0000000010000c00 and cpu addr 0xffff8800bb7cac00
Feb 17 19:36:25 lapek kernel: [ 8200.918345] radeon 0000:01:00.0: fence driver
on ring 3 use gpu addr 0x0000000010000c0c and cpu addr 0xffff8800bb7cac0c
Feb 17 19:36:25 lapek kernel: [ 8200.950104] [drm] ring test on 0 succeeded in
1 usecs
Feb 17 19:36:25 lapek kernel: [ 8201.054176] [drm:r600_dma_ring_test] *ERROR*
radeon: ring 3 test failed (0xCAFEDEAD)
Feb 17 19:36:25 lapek kernel: [ 8201.054181] [drm:r600_resume] *ERROR* r600
startup failed on resume
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-02-17 18:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 13:03 [Bug 62721] New: GPU lockup: radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec bugzilla-daemon
2013-10-08 13:03 ` [Bug 62721] " 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 [this message]
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-8qYxeYh0QE@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