From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98505] [radeon, amdgpu] Regression introduced in 4.8-rc3
Date: Sun, 13 Nov 2016 11:24:51 +0000 [thread overview]
Message-ID: <bug-98505-502-YP3Mtdsg9G@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98505-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1088 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98505
--- Comment #25 from Peter Wu <peter@lekensteyn.nl> ---
"Resume" means "runtime resume" as opposed to "resume from system sleep" right
(based on the logs).
When this happens, what is the output of "sudo lspci -s4: -nnvv"? (is the "rev"
field "ff" or something else? Does the Power Management register report D0 or
D3?)
Can you reproduce the problem in this way:
1. Blacklist amdgpu (and radeon if enabled)
2. Boot system
3. Load amdgpu
4. Wait for runtime PM to kick in (5 seconds)
5. Wake up (e.g. "lspci")
If so, can you build your kernel with CONFIG_ACPI_DEBUG=y and either boot with
acpi.trace_state=enable? If that gives too many messages, you can also try
setting the option between step 2 and 3:
echo enable > /sys/module/acpi/parameters/trace_state
What is the dmesg for this? (At this moment it is not clear for me what the
port PM is doing versus what amdgpu is doing, hopefully some logs will clarify
this).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1939 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 prev parent reply other threads:[~2016-11-13 11:24 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 16:48 [Bug 98505] [Topaz] Regression introduces in 4.8-rc3 bugzilla-daemon
2016-10-30 16:53 ` bugzilla-daemon
2016-11-01 13:29 ` bugzilla-daemon
2016-11-01 13:56 ` bugzilla-daemon
2016-11-01 18:26 ` bugzilla-daemon
2016-11-01 20:46 ` bugzilla-daemon
2016-11-01 20:49 ` bugzilla-daemon
2016-11-01 23:31 ` bugzilla-daemon
2016-11-02 6:07 ` bugzilla-daemon
2016-11-02 6:11 ` bugzilla-daemon
2016-11-02 16:35 ` bugzilla-daemon
2016-11-02 16:46 ` bugzilla-daemon
2016-11-02 16:55 ` bugzilla-daemon
2016-11-02 16:56 ` bugzilla-daemon
2016-11-04 0:08 ` bugzilla-daemon
2016-11-04 14:51 ` bugzilla-daemon
2016-11-04 15:04 ` bugzilla-daemon
2016-11-07 18:42 ` bugzilla-daemon
2016-11-11 17:56 ` bugzilla-daemon
2016-11-11 17:58 ` [Bug 98505] [radeon, amdgpu] Regression introduced " bugzilla-daemon
2016-11-11 18:14 ` bugzilla-daemon
2016-11-11 18:17 ` bugzilla-daemon
2016-11-11 18:49 ` bugzilla-daemon
2016-11-11 21:22 ` bugzilla-daemon
2016-11-12 23:40 ` bugzilla-daemon
2016-11-13 6:41 ` bugzilla-daemon
2016-11-13 11:24 ` bugzilla-daemon [this message]
2016-11-13 16:01 ` bugzilla-daemon
2016-11-13 16:02 ` bugzilla-daemon
2016-11-14 10:52 ` bugzilla-daemon
2016-11-14 15:12 ` bugzilla-daemon
2016-11-17 15:03 ` bugzilla-daemon
2016-11-19 0:22 ` bugzilla-daemon
2016-11-19 2:07 ` bugzilla-daemon
2016-11-19 2:08 ` bugzilla-daemon
2016-11-19 17:32 ` bugzilla-daemon
2016-11-19 19:21 ` bugzilla-daemon
2016-11-19 19:23 ` bugzilla-daemon
2016-12-05 13:49 ` bugzilla-daemon
2016-12-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-98505-502-YP3Mtdsg9G@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).