All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111399] Freeze after suspend/resume with kernel 5.0
Date: Wed, 14 Aug 2019 09:33:02 +0000	[thread overview]
Message-ID: <bug-111399-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 111399
           Summary: Freeze after suspend/resume with kernel 5.0
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: vl4d1m1r37@gmail.com

Created attachment 145058
  --> https://bugs.freedesktop.org/attachment.cgi?id=145058&action=edit
blackscreen bug log

System: HP 15-bw660ur
GPU: Radeon 520 (Sun XT)

Screen freezes after resuming from suspend. Here is discussion of this bug -
https://bugs.archlinux.org/task/61950.

I made a bisection in branch linux-5.0.y between the tags v5.0-rc1 and 4.20. I
found that there are two bugs with the screen after resuming from suspend. The
first bug is the one that is present in the kernel v.5 now and earlier to
version 5.0-rc1. There is a bug with amdgpu_job_timedout in the log. The second
is the black screen after resuming from suspend and the absence of the
amdgpu_job_timedout error in the log.
The second bug first appears in commit
[262485a50fd4532a8d71165190adc7a0a19bcc9e] drm/amd/display: Expand dc to use
16.16 bit backlight.
The first bug with amdgpu_job_timedout first appears in the commit
[106c7d6148e5aadd394e6701f7e498df49b869d1] drm/amdgpu: abstract the function of
enter/exit safe mode for RLC.
During the bisect searching for the first error, I went through the following
stages sequentially: good (resuming from suspend was successful), error 2,
good, error 2, error 1.

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

[-- Attachment #1.2: Type: text/html, Size: 3257 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-14  9:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-14  9:33 bugzilla-daemon [this message]
2019-08-14  9:34 ` [Bug 111399] Freeze after suspend/resume with kernel 5.0 bugzilla-daemon
2019-08-14 11:31 ` 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-111399-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.