From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 111498] [amdgpu, Ryzen 7 Pro 3700U] freeze when suspending
shortly after wakeup
Date: Tue, 27 Aug 2019 08:20:35 +0000
Message-ID:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0820342655=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[IPv6:2610:10:20:722:a800:ff:fe98:4b55])
by gabe.freedesktop.org (Postfix) with ESMTP id 852A5899B7
for ; Tue, 27 Aug 2019 08:20:35 +0000 (UTC)
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
--===============0820342655==
Content-Type: multipart/alternative; boundary="15668940350.EDE00cA.22102"
Content-Transfer-Encoding: 7bit
--15668940350.EDE00cA.22102
Date: Tue, 27 Aug 2019 08:20:35 +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=3D111498
Bug ID: 111498
Summary: [amdgpu, Ryzen 7 Pro 3700U] freeze when suspending
shortly after wakeup
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: not set
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: rohan@rohanlean.de
Linux version: 5.2.9
Hardware: Ryzen 7 Pro 3700U
When I try to suspend the system while it is waking up from s3, the system =
does
not properly suspend again, but instead freezes with a blank screen, and the
fans ramp up after a while.
I have chosen severity "major", because this can cause overheating when a
laptop that is thought to be suspended is put into a bag.
Possibly relevant kernel messages before the hard reset:
Aug 27 09:11:39 kernel: PM: suspend entry (s2idle)
Aug 27 09:11:39 kernel: PM: suspend exit
Aug 27 09:11:39 kernel: Restarting tasks ... done.
Aug 27 09:11:39 kernel: OOM killer enabled.
Aug 27 09:11:39 kernel: acpi LNXPOWER:00: Turning OFF
Aug 27 09:11:39 kernel: PM: resume devices took 1.529 seconds
Aug 27 09:11:39 kernel: [drm:amdgpu_device_ip_late_init_func_handler [amdgp=
u]]
*ERROR* ib ring test failed (-110).
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: [drm:amdgpu_ib_ring_tests
[amdgpu]] *ERROR* IB test failed on gfx (-110).
Aug 27 09:11:39 kernel: [drm] Fence fallback timer expired on ring sdma0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring vcn_jpeg uses VM inv eng =
6 on
hub 1
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring vcn_enc1 uses VM inv eng =
5 on
hub 1
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring vcn_enc0 uses VM inv eng =
4 on
hub 1
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring vcn_dec uses VM inv eng 1=
on
hub 1
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring sdma0 uses VM inv eng 0 on
hub 1
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring kiq_2.1.0 uses VM inv eng=
11
on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.3.1 uses VM inv en=
g 10
on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.2.1 uses VM inv en=
g 9
on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.1.1 uses VM inv en=
g 8
on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.0.1 uses VM inv en=
g 7
on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.3.0 uses VM inv en=
g 6
on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.2.0 uses VM inv en=
g 5
on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.1.0 uses VM inv en=
g 4
on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.0.0 uses VM inv en=
g 1
on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring gfx uses VM inv eng 0 on =
hub
0
Aug 27 09:11:39 kernel: [drm] VCN decode and encode initialized
successfully(under DPG Mode).
Aug 27 09:11:39 kernel: amdgpu: [powerplay] dpm has been enabled
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15668940350.EDE00cA.22102
Date: Tue, 27 Aug 2019 08:20:35 +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
| Bug ID |
111498
|
| Summary |
[amdgpu, Ryzen 7 Pro 3700U] freeze when suspending shortly af=
ter wakeup
|
| Product |
DRI
|
| Version |
unspecified
|
| Hardware |
x86-64 (AMD64)
|
| OS |
Linux (All)
|
| Status |
NEW
|
| Severity |
major
|
| Priority |
not set
|
| Component |
DRM/AMDgpu
|
| Assignee |
dri-devel@lists.freedesktop.org
|
| Reporter |
rohan@rohanlean.de
|
Linux version: 5.2.9
Hardware: Ryzen 7 Pro 3700U
When I try to suspend the system while it is waking up from s3, the system =
does
not properly suspend again, but instead freezes with a blank screen, and the
fans ramp up after a while.
I have chosen severity "major", because this can cause overheatin=
g when a
laptop that is thought to be suspended is put into a bag.
Possibly relevant kernel messages before the hard reset:
Aug 27 09:11:39 kernel: PM: suspend entry (s2idle)
Aug 27 09:11:39 kernel: PM: suspend exit
Aug 27 09:11:39 kernel: Restarting tasks ... done.
Aug 27 09:11:39 kernel: OOM killer enabled.
Aug 27 09:11:39 kernel: acpi LNXPOWER:00: Turning OFF
Aug 27 09:11:39 kernel: PM: resume devices took 1.529 seconds
Aug 27 09:11:39 kernel: [drm:amdgpu_device_ip_late_init_func_handler [amdgp=
u]]
*ERROR* ib ring test failed (-110).
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: [drm:amdgpu_ib_ring_tests
[amdgpu]] *ERROR* IB test failed on gfx (-110).
Aug 27 09:11:39 kernel: [drm] Fence fallback timer expired on ring sdma0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring vcn_jpeg uses VM inv eng =
6 on
hub 1
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring vcn_enc1 uses VM inv eng =
5 on
hub 1
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring vcn_enc0 uses VM inv eng =
4 on
hub 1
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring vcn_dec uses VM inv eng 1=
on
hub 1
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring sdma0 uses VM inv eng 0 on
hub 1
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring kiq_2.1.0 uses VM inv eng=
11
on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.3.1 uses VM inv en=
g 10
on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.2.1 uses VM inv en=
g 9
on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.1.1 uses VM inv en=
g 8
on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.0.1 uses VM inv en=
g 7
on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.3.0 uses VM inv en=
g 6
on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.2.0 uses VM inv en=
g 5
on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.1.0 uses VM inv en=
g 4
on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.0.0 uses VM inv en=
g 1
on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring gfx uses VM inv eng 0 on =
hub
0
Aug 27 09:11:39 kernel: [drm] VCN decode and encode initialized
successfully(under DPG Mode).
Aug 27 09:11:39 kernel: amdgpu: [powerplay] dpm has been enabled
You are receiving this mail because:
- You are the assignee for the bug.
=
--15668940350.EDE00cA.22102--
--===============0820342655==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs
--===============0820342655==--