From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93895] GPU lockup on AMD A4-3400 APU when starting X server on opensource drivers. (works fine with fglrx)
Date: Thu, 28 Jan 2016 01:21:28 +0000 [thread overview]
Message-ID: <bug-93895-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 5600 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93895
Bug ID: 93895
Summary: GPU lockup on AMD A4-3400 APU when starting X server
on opensource drivers. (works fine with fglrx)
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: azari4096@gmail.com
I've had this lockup on this machine for the past few years, across several
different kernel versions, different distributions, etc. Booting with KMS works
fine, but the second a graphical environment starts (whether X or
wayland-based), it locks up.
Booting Ubuntu with user-space mode-setting works, and then I can install FGLRX
from there and everything works fine. After speaking with airlied on IRC, they
suggested it could be a workaround that AMD has put into FGLRX that never made
it into the opensource drivers, and that AMD might have to look into it.
CPU/GPU : A4-3400
Motherboard : GA-A75M-D2H (
http://www.gigabyte.com/products/product-page.aspx?pid=3930#ov )
journalctl log of the lockup:
------------------------------------------------------------
Jan 27 18:28:32 miku dbus-daemon[374]: Successfully activated service
'org.freedesktop.systemd1'
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: ring 0 stalled for more
than 10000msec
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GPU lockup (current fence
id 0x0000000000000001 last fence id 0x0000000000000003 on ring 0)
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: Saved 55 dwords of
commands on ring 0.
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GPU softreset: 0x00000009
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS
= 0xB1403828
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS_SE0
= 0x28000007
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS_SE1
= 0x00000007
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: SRBM_STATUS
= 0x20000840
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: SRBM_STATUS2
= 0x00000000
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0:
R_008674_CP_STALLED_STAT1 = 0x00000000
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0:
R_008678_CP_STALLED_STAT2 = 0x40000000
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_00867C_CP_BUSY_STAT
= 0x00008000
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_008680_CP_STAT
= 0x80228643
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_00D034_DMA_STATUS_REG
= 0x44C83D57
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0:
GRBM_SOFT_RESET=0x00007F6B
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0:
SRBM_SOFT_RESET=0x00000100
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS
= 0x00003828
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS_SE0
= 0x00000007
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS_SE1
= 0x00000007
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: SRBM_STATUS
= 0x20000040
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: SRBM_STATUS2
= 0x00000000
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0:
R_008674_CP_STALLED_STAT1 = 0x00000000
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0:
R_008678_CP_STALLED_STAT2 = 0x00000000
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_00867C_CP_BUSY_STAT
= 0x00000000
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_008680_CP_STAT
= 0x00000000
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_00D034_DMA_STATUS_REG
= 0x44C83D57
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GPU reset succeeded,
trying to resume
Jan 27 18:28:42 miku kernel: [drm] Found smc ucode version: 0x00011100
Jan 27 18:28:42 miku kernel: [drm] PCIE GART of 1024M enabled (table at
0x0000000000274000).
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: WB enabled
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: fence driver on ring 0
use gpu addr 0x0000000020000c00 and cpu addr 0xffff8800c613fc00
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: fence driver on ring 3
use gpu addr 0x0000000020000c0c and cpu addr 0xffff8800c613fc0c
Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: fence driver on ring 5
use gpu addr 0x0000000000072118 and cpu addr 0xffffc90002432118
Jan 27 18:28:42 miku kernel: [drm] ring test on 0 succeeded in 1 usecs
Jan 27 18:28:42 miku kernel: [drm] ring test on 3 succeeded in 3 usecs
Jan 27 18:28:42 miku kernel: [drm] ring test on 5 succeeded in 1 usecs
Jan 27 18:28:42 miku kernel: [drm] UVD initialized successfully.
Jan 27 18:28:52 miku kernel: radeon 0000:00:01.0: ring 0 stalled for more
than 10370msec
Jan 27 18:28:52 miku kernel: radeon 0000:00:01.0: GPU lockup (current fence
id 0x0000000000000002 last fence id 0x0000000000000004 on ring 0)
Jan 27 18:28:52 miku kernel: [drm:r600_ib_test [radeon]] *ERROR* radeon:
fence wait failed (-35).
Jan 27 18:28:52 miku kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR*
radeon: failed testing IB on GFX ring (-35).
Jan 27 18:29:22 miku systemd[1]: Started Getty on tty2.
------------------------------------------------------------
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 6936 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 reply other threads:[~2016-01-28 1:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 1:21 bugzilla-daemon [this message]
2016-01-28 3:52 ` [Bug 93895] GPU lockup on AMD A4-3400 APU when starting X server on opensource drivers. (works fine with fglrx) bugzilla-daemon
2016-01-28 3:53 ` bugzilla-daemon
2016-01-28 3:56 ` bugzilla-daemon
2016-01-28 4:45 ` bugzilla-daemon
2016-01-29 3:22 ` bugzilla-daemon
2016-01-31 22:53 ` bugzilla-daemon
2016-01-31 23:17 ` bugzilla-daemon
2016-02-02 1:15 ` bugzilla-daemon
2016-02-02 1:18 ` bugzilla-daemon
2016-02-02 1:24 ` bugzilla-daemon
2019-11-19 9:12 ` 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-93895-502@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