Bug 111498

Summary:	[amdgpu, Ryzen 7 Pro 3700U] freeze when suspending shortly after wakeup
Product:	DRI	Reporter:	Rohan Lean <rohan>
Component:	DRM/AMDgpu	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED MOVED	QA Contact:
Severity:	major
Priority:	high
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Rohan Lean 2019-08-27 08:20:35 UTC

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 [amdgpu]] *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 eng 10 on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Aug 27 09:11:39 kernel: amdgpu 0000:05:00.0: ring comp_1.0.0 uses VM inv eng 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

Comment 1 Rohan Lean 2019-08-27 10:45:08 UTC

I should mention: the messages are in reverse chronological order, so "PM: suspend entry (s2idle)" (notably "s2idle" instead of "deep") is the last message logged before reset.

Comment 2 Martin Peres 2019-11-19 09:50:43 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/896.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.