From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 77001] Radeon R9 270X GPU lockup and resume failure after all night inactivity [drm,radeonsi]
Date: Fri, 30 May 2014 12:39:41 +0000 [thread overview]
Message-ID: <bug-77001-2300-ccKsSeerQq@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-77001-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=77001
--- Comment #3 from Grzegorz Kowal <custos.mentis@gmail.com> ---
This morning at 6:27am it happened again. The computer was idle during the
whole night, even during the hang. When I touched the keyboard around 8am, the
monitor turned on, but I saw dark flickering screen only. To check if kwin was
responsible for the hang, I logged out from the KDE session yesterday, so only
KDM was running.
This time I could log in through ssh, copy the kernel log and reboot the
machine though.
The kernel log contained:
radeon 0000:01:00.0: GPU lockup CP stall for more than 15500msec
radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000026efd3 last fence id
0x000000000026efd2 on ring 0)
radeon 0000:01:00.0: failed to get a new IB (-35)
radeon 0000:01:00.0: failed to get a new IB (-35)
radeon 0000:01:00.0: failed to get a new IB (-35)
radeon 0000:01:00.0: sa_manager is not empty, clearing anyway
radeon 0000:01:00.0: Saved 2365 dwords of commands on ring 0.
radeon 0000:01:00.0: GPU softreset: 0x0000004D
radeon 0000:01:00.0: GRBM_STATUS = 0xB3507028
radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x28000006
radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x2F000006
radeon 0000:01:00.0: SRBM_STATUS = 0x20000EC0
radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x40000000
radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00408002
radeon 0000:01:00.0: R_008680_CP_STAT = 0x84228647
radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44483146
radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57
radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000
radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
radeon 0000:01:00.0: Wait for MC idle timedout !
radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF
radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00100100
radeon 0000:01:00.0: GRBM_STATUS = 0x00003028
radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006
radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006
radeon 0000:01:00.0: SRBM_STATUS = 0x20000EC0
radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000
radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000
radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000
radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57
radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing C008 (len 254,
WS 0, PS 4) @ 0xC032
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing B67A (len 94,
WS 12, PS 8) @ 0xB6C3
[drm] probing gen 2 caps for device 1002:5a16 = 33ed01/0
radeon 0000:01:00.0: Wait for MC idle timedout !
radeon 0000:01:00.0: Wait for MC idle timedout !
[drm] PCIE GART of 1024M enabled (table at 0x0000000000276000).
radeon 0000:01:00.0: WB enabled
radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and
cpu addr 0xffff8800ba363c00
radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and
cpu addr 0xffff8800ba363c04
radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and
cpu addr 0xffff8800ba363c08
radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and
cpu addr 0xffff8800ba363c0c
radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and
cpu addr 0xffff8800ba363c10
radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and
cpu addr 0xffffc90010335a18
[drm:r600_ring_test] *ERROR* radeon: ring 0 test failed
(scratch(0x850C)=0xCAFEDEAD)
[drm:si_resume] *ERROR* si startup failed on resume
[drm:radeon_pm_resume_dpm] *ERROR* radeon: dpm resume failed
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-05-30 12:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 12:50 [Bug 77001] New: Radeon R9 270X GPU lockup and resume failure after all night inactivity bugzilla-daemon
2014-05-28 15:24 ` [Bug 77001] Radeon R9 270X GPU lockup and resume failure after all night inactivity [drm,radeonsi] bugzilla-daemon
2014-05-28 16:17 ` bugzilla-daemon
2014-05-29 13:37 ` bugzilla-daemon
2014-05-30 12:39 ` bugzilla-daemon [this message]
2014-06-03 11:24 ` bugzilla-daemon
2014-06-03 11:25 ` bugzilla-daemon
2014-07-02 20:49 ` 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-77001-2300-ccKsSeerQq@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