All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111848] AMDGPU and display fails after resume from suspend
Date: Sat, 28 Sep 2019 09:30:48 +0000	[thread overview]
Message-ID: <bug-111848-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 111848
           Summary: AMDGPU and display fails after resume from suspend
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: not set
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: mkj@gotu.dk

Sometimes after my machine resumes from suspend my display stays off with no
signal, and USB keyboard (Num lock) and mouse doesn't react.

This time I managed to SSH into the machine and gather some logs after it
failed resuming.

I have experienced this with different kernels and under different Linux
operating systems, like Debian and Gentoo, but it is not happening often enough
for me to sense a pattern.

I will attach log files to the best of my abilities according to:
https://amdgpu-install.readthedocs.io/en/latest/install-bugrep.html

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

[-- Attachment #1.2: Type: text/html, Size: 2500 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-09-28  9:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-28  9:30 bugzilla-daemon [this message]
2019-09-28  9:32 ` [Bug 111848] AMDGPU and display fails after resume from suspend bugzilla-daemon
2019-09-28  9:32 ` bugzilla-daemon
2019-09-28  9:32 ` bugzilla-daemon
2019-09-28  9:33 ` bugzilla-daemon
2019-09-28  9:33 ` bugzilla-daemon
2019-09-28  9:34 ` bugzilla-daemon
2019-09-28  9:34 ` bugzilla-daemon
2019-09-28  9:34 ` bugzilla-daemon
2019-09-28  9:35 ` bugzilla-daemon
2019-09-28  9:35 ` bugzilla-daemon
2019-09-28  9:35 ` bugzilla-daemon
2019-09-28  9:36 ` bugzilla-daemon
2019-10-03 14:20 ` bugzilla-daemon
2019-10-03 14:31 ` bugzilla-daemon
2019-10-03 14:38 ` bugzilla-daemon
2019-10-03 14:40 ` bugzilla-daemon
2019-10-03 14:59 ` bugzilla-daemon
2019-10-04 18:27 ` bugzilla-daemon
2019-10-07 10:14 ` bugzilla-daemon
2019-11-19  9:56 ` 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-111848-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.