All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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	[thread overview]
Message-ID: <bug-111498-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 3163 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=111498

            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 [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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4471 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-08-27  8:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27  8:20 bugzilla-daemon [this message]
2019-08-27 10:45 ` [Bug 111498] [amdgpu, Ryzen 7 Pro 3700U] freeze when suspending shortly after wakeup bugzilla-daemon
2019-11-19  9:50 ` 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-111498-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.