From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97248] [regression] [amdgpu] New regression in 4.8-rc1
Date: Mon, 08 Aug 2016 19:17:30 +0000 [thread overview]
Message-ID: <bug-97248-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2056 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97248
Bug ID: 97248
Summary: [regression] [amdgpu] New regression in 4.8-rc1
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: mike@fireburn.co.uk
Created attachment 125605
--> https://bugs.freedesktop.org/attachment.cgi?id=125605&action=edit
dmesg
I'm seeing a new regression since 4.8-rc1 on Linus's tree, drm-next, agd5f's
4.9-next-wip since 4.8-rc1 was merged. I'm about to start bisecting
[ 12.644973] amdgpu 0000:01:00.0: Refused to change power state, currently in
D3
[ 12.720886] amdgpu 0000:01:00.0: Refused to change power state, currently in
D3
[ 12.733891] amdgpu 0000:01:00.0: Refused to change power state, currently in
D3
[ 12.958093] amdgpu 0000:01:00.0: Wait for MC idle timedout !
[ 13.071062] amdgpu 0000:01:00.0: Wait for MC idle timedout !
[ 13.081607] [ powerplay ] Invalid VramInfo table.Failed to initialize MC reg
table!
[ 13.770954] [drm:gfx_v8_0_ring_test_ring] *ERROR* amdgpu: ring 0 test failed
(scratch(0xC040)=0xFFFFFFFF)
[ 13.772803] [drm:amdgpu_resume] *ERROR* resume of IP block <gfx_v8_0> failed
-22
[ 13.774713] [drm:amdgpu_resume_kms] *ERROR* amdgpu_resume failed (-22).
[ 13.776643] amdgpu 0000:01:00.0: couldn't schedule ib
[ 13.778602] [drm:amdgpu_job_run] *ERROR* Error scheduling IBs (-22)
[ 13.805924] amdgpu 0000:01:00.0: couldn't schedule ib
[ 13.805928] [drm:amdgpu_job_run] *ERROR* Error scheduling IBs (-22)
[ 18.934066] [drm:amdgpu_suspend] *ERROR* suspend of IP block <vce_v3_0>
failed -110
[ 18.943133] [drm:amdgpu_suspend] *ERROR* set_clockgating_state(ungate) of IP
block <uvd_v5_0> failed -16
These are probably the most relevant messages
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3471 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-08-08 19:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 19:17 bugzilla-daemon [this message]
2016-08-08 19:24 ` [Bug 97248] [regression] [amdgpu] New regression in 4.8-rc1 bugzilla-daemon
2016-08-08 19:29 ` bugzilla-daemon
2016-08-08 19:30 ` bugzilla-daemon
2016-08-08 19:30 ` bugzilla-daemon
2016-08-08 19:31 ` bugzilla-daemon
2016-08-08 19:33 ` bugzilla-daemon
2016-08-08 19:35 ` bugzilla-daemon
2016-11-03 13: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-97248-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;
as well as URLs for NNTP newsgroup(s).