From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105021] suspend / rx550 / extremely slow after 2nd thaw
Date: Wed, 14 Feb 2018 18:14:21 +0000 [thread overview]
Message-ID: <bug-105021-502-8VxO2h5e8W@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105021-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1142 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105021
--- Comment #18 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to arne_woerner from comment #17)
> yup:
> i mean: i did not test, which one is necessary...
> so i cannot say, if all three r necessary, or if just one/two of them
> suffice...
>
> tomorrow i will test "amdgpu.audio=0 amdgpu.msi=0"...
> with the stable linux-firmware package... right?
>
> or do u mean just "amdgpu.msi=0"?
> maybe hdmi audio works already, if amdgpu.msi is 0?
I doubt the audio parameter would affect anything in this regard, but you said
it was required for the board to work properly? Is that the case or am I
misinterpreting you? For audio on your board, you need to enable DC which is
only available on kernel 4.15 and newer. You can boot with amdgpu.dc=1 to
enable DC. The msi option may help narrow down the interrupt issue. If it
helps, it seems MSIs are not working properly on your system after resume.
This would probably be something outside of the driver if it's a regression.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2043 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:[~2018-02-14 18:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-105021-502@http.bugs.freedesktop.org/>
2018-02-09 9:17 ` [Bug 105021] suspend / rx550 / extremely slow after 2nd thaw bugzilla-daemon
2018-02-09 15:37 ` bugzilla-daemon
2018-02-12 6:02 ` bugzilla-daemon
2018-02-12 11:08 ` bugzilla-daemon
2018-02-13 7:32 ` bugzilla-daemon
2018-02-13 9:08 ` bugzilla-daemon
2018-02-13 18:55 ` bugzilla-daemon
2018-02-13 20:47 ` bugzilla-daemon
2018-02-13 21:26 ` bugzilla-daemon
2018-02-13 22:10 ` bugzilla-daemon
2018-02-14 7:06 ` bugzilla-daemon
2018-02-14 8:11 ` bugzilla-daemon
2018-02-14 14:11 ` bugzilla-daemon
2018-02-14 14:12 ` bugzilla-daemon
2018-02-14 17:57 ` bugzilla-daemon
2018-02-14 18:14 ` bugzilla-daemon [this message]
2018-02-14 21:45 ` bugzilla-daemon
2018-02-14 21:56 ` bugzilla-daemon
2018-02-14 22:01 ` bugzilla-daemon
2018-02-15 6:51 ` bugzilla-daemon
2018-02-17 7:55 ` bugzilla-daemon
2018-02-20 20:09 ` bugzilla-daemon
2018-02-20 21:03 ` bugzilla-daemon
2018-02-21 5:49 ` bugzilla-daemon
2018-02-21 5:58 ` bugzilla-daemon
2018-03-06 8:15 ` bugzilla-daemon
2018-03-06 16:15 ` bugzilla-daemon
2018-03-07 19:09 ` 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-105021-502-8VxO2h5e8W@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