From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 105760] [4.17-rc1] RIP:
smu7_populate_single_firmware_entry.isra.6+0x57/0xc0 [amdgpu] RSP:
ffffa17901efb930
Date: Thu, 26 Jul 2018 22:32:31 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2037371902=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id A53076E84F
for ; Thu, 26 Jul 2018 22:32:31 +0000 (UTC)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============2037371902==
Content-Type: multipart/alternative; boundary="15326443512.9f2515.15476"
Content-Transfer-Encoding: 7bit
--15326443512.9f2515.15476
Date: Thu, 26 Jul 2018 22:32:31 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D105760
Thomas Martitz changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #140356|0 |1
is obsolete| |
Attachment #140585|0 |1
is obsolete| |
Attachment #140611|0 |1
is obsolete| |
Attachment #140660|0 |1
is obsolete| |
--- Comment #55 from Thomas Martitz ---
Created attachment 140845
--> https://bugs.freedesktop.org/attachment.cgi?id=3D140845&action=3Dedit
dmesg + Karols hack
No, unfortunately, the GPU is unusable after resume, but the dmesg output is
different now.
FWIW, in this case I have booted with pcie_port_pm=3Doff which I feel impro=
ves
things on my system (but it's nowhere a solution), since I think the GPU is
behind a PCIe bridge to which the TB3 port is also connected, and I found in
the source that bridge pm should be disabled if there are TB3 ports behind =
due
to hotplug.
Without pcie_port_pm the behavior is almost the same, except that dmesg sho=
ws
lots of powerplay error messages that don't occur in the attached output
(again, made with pcie_port_pm=3Doff).
Karol's patch didn't apply cleanly onto drm-next-4.19-wip, so I made some
changes, perhaps you may check if it's still equivalent (will attach with t=
he
next comment.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15326443512.9f2515.15476
Date: Thu, 26 Jul 2018 22:32:31 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
Thomas Martitz
changed
bug 10576=
0
| What |
Removed |
Added |
| Attachment #140356 is obsolete=
td>
|
|
1
|
| Attachment #140585 is obsolete=
td>
|
|
1
|
| Attachment #140611 is obsolete=
td>
|
|
1
|
| Attachment #140660 is obsolete=
td>
|
|
1
|
Comme=
nt # 55
on bug 10576=
0
from Thomas Martitz
Created attachment 140845 [details]
dmesg + Karols hack
No, unfortunately, the GPU is unusable after resume, but the dmesg output is
different now.
FWIW, in this case I have booted with pcie_port_pm=3Doff which I feel impro=
ves
things on my system (but it's nowhere a solution), since I think the GPU is
behind a PCIe bridge to which the TB3 port is also connected, and I found in
the source that bridge pm should be disabled if there are TB3 ports behind =
due
to hotplug.
Without pcie_port_pm the behavior is almost the same, except that dmesg sho=
ws
lots of powerplay error messages that don't occur in the attached output
(again, made with pcie_port_pm=3Doff).
Karol's patch didn't apply cleanly onto drm-next-4.19-wip, so I made some
changes, perhaps you may check if it's still equivalent (will attach with t=
he
next comment.
You are receiving this mail because:
- You are the assignee for the bug.
=
--15326443512.9f2515.15476--
--===============2037371902==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============2037371902==--