From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 151541] New: AMD hybrid graphics: [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume
Date: Fri, 05 Aug 2016 09:51:15 +0000 [thread overview]
Message-ID: <bug-151541-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=151541
Bug ID: 151541
Summary: AMD hybrid graphics: [drm:evergreen_resume [radeon]]
*ERROR* evergreen startup failed on resume
Product: Drivers
Version: 2.5
Kernel Version: 4.7.0
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: pastas4@gmail.com
Regression: No
Created attachment 227711
--> https://bugzilla.kernel.org/attachment.cgi?id=227711&action=edit
dmesg
I am using an Acer Aspire 7560G laptop with muxless AMD-AMD hybrid graphics,
officially 6520G integrated and 6720G dedicated:
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
BeaverCreek [Radeon HD 6520G]
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] (rev ff)
This configuration causes kernel errors whenever the dedicated card gets
touched (usually by either running lspci - which takes a while to run - or
turning the monitor off and back on again). Visually that shows up as
flickering and parts of the screen not refreshing properly.
If in the BIOS I turn off the dedicated card completely, I don't have this
problem any more.
I tested it with kernel 4.7 and 4.1, both had the same results. I'm running
openSUSE Leap 42.1.
Here's the relevant part of dmesg (full dmesg is attached):
[ 668.895509] radeon 0000:01:00.0: Refused to change power state, currently in
D3
[ 668.971201] radeon 0000:01:00.0: Refused to change power state, currently in
D3
[ 668.987293] radeon 0000:01:00.0: Refused to change power state, currently in
D3
[ 668.988397] radeon 0000:01:00.0: GPU softreset: 0x00000BDD
[ 668.988405] radeon 0000:01:00.0: GRBM_STATUS = 0xFFFFFFFF
[ 668.988412] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0xFFFFFFFF
[ 668.988417] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0xFFFFFFFF
[ 668.988423] radeon 0000:01:00.0: SRBM_STATUS = 0xFFFFFFFF
[ 668.988428] radeon 0000:01:00.0: SRBM_STATUS2 = 0xFFFFFFFF
[ 668.988434] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0xFFFFFFFF
[ 668.988439] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0xFFFFFFFF
[ 668.988445] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0xFFFFFFFF
[ 668.988450] radeon 0000:01:00.0: R_008680_CP_STAT = 0xFFFFFFFF
[ 668.988456] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0xFFFFFFFF
[ 670.587759] radeon 0000:01:00.0: Wait for MC idle timedout !
[ 670.587762] radeon 0000:01:00.0: GRBM_SOFT_RESET=0xFFFFFFFF
[ 670.587817] radeon 0000:01:00.0: SRBM_SOFT_RESET=0xFFFFFFFF
[ 670.588971] radeon 0000:01:00.0: GRBM_STATUS = 0xFFFFFFFF
[ 670.588973] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0xFFFFFFFF
[ 670.588976] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0xFFFFFFFF
[ 670.588978] radeon 0000:01:00.0: SRBM_STATUS = 0xFFFFFFFF
[ 670.588981] radeon 0000:01:00.0: SRBM_STATUS2 = 0xFFFFFFFF
[ 670.588983] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0xFFFFFFFF
[ 670.588986] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0xFFFFFFFF
[ 670.588988] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0xFFFFFFFF
[ 670.588991] radeon 0000:01:00.0: R_008680_CP_STAT = 0xFFFFFFFF
[ 670.588993] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0xFFFFFFFF
[ 675.594474] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for
more than 5secs aborting
[ 675.594493] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck
executing CE66 (len 62, WS 0, PS 0) @ 0xCE82
[ 675.594511] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck
executing BB66 (len 1036, WS 4, PS 0) @ 0xBC63
[ 675.594529] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck
executing BAFC (len 76, WS 0, PS 8) @ 0xBB04
[ 675.594653] [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume
failed
[ 677.087926] radeon 0000:01:00.0: Wait for MC idle timedout !
[ 677.274849] radeon 0000:01:00.0: Wait for MC idle timedout !
[ 677.292534] [drm] PCIE GART of 1024M enabled (table at 0x0000000000162000).
[ 677.292646] radeon 0000:01:00.0: WB enabled
[ 677.292651] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x0000000040000c00 and cpu addr 0xffff8800c6e69c00
[ 677.292654] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x0000000040000c0c and cpu addr 0xffff8800c6e69c0c
[ 677.297315] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x0000000000072118 and cpu addr 0xffffc90001c32118
[ 677.510244] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed
(scratch(0x8504)=0xFFFFFFFF)
[ 677.510268] [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed
on resume
[ 677.510433] [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume
failed
[ 682.513984] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for
more than 5secs aborting
[ 682.514002] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck
executing C510 (len 1136, WS 0, PS 0) @ 0xC53A
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-08-05 9:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 9:51 bugzilla-daemon [this message]
2016-08-05 9:51 ` [Bug 151541] AMD hybrid graphics: [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume bugzilla-daemon
2016-08-05 10:05 ` bugzilla-daemon
2016-08-05 13:18 ` bugzilla-daemon
2016-08-05 13:18 ` bugzilla-daemon
2016-08-05 16:08 ` bugzilla-daemon
2016-08-05 18:15 ` bugzilla-daemon
2016-08-05 19:32 ` 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-151541-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.