All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 210849] Black screen after resume from long suspend. Open/Close lid. AMDGPU
Date: Fri, 05 Feb 2021 04:35:14 +0000	[thread overview]
Message-ID: <bug-210849-2300-chOq2KGOuR@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210849-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=210849

--- Comment #10 from JerryD (jvdelisle@charter.net) ---
This bug has basically disabled two different machines I have that use AMD
graphics cards.  One, a work station running Fedora 33 will lose the display if
I do not log on right away after a power up.  The defaults that blank the
screen or just a simple lock screen sequence basically causes the monitor to
shutoff to save energy. At this point the display can not be recovered since
the driver loses it self.  It is a real shame as this system was working
perfectly for over a year beofre this happened.  The guilty patch should be
reverted immediately.

I can remote into the system from elsewhere ussing ssh and command a reboot to
bring it back.  The kernel underlying is running and completely functional. The
device driver AMDGPU is 'F'ed up.  In my many many years of using Fedora and
other linux distros, this is by far the worse cluster bug I have ever see.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2021-02-05  4:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22 11:15 [Bug 210849] New: Black screen after resume from long suspend. Open/Close lid. AMDGPU bugzilla-daemon
2020-12-22 11:18 ` [Bug 210849] " bugzilla-daemon
2020-12-22 11:18 ` bugzilla-daemon
2020-12-22 11:20 ` bugzilla-daemon
2020-12-22 11:25 ` bugzilla-daemon
2020-12-22 11:28 ` bugzilla-daemon
2020-12-23 18:36 ` bugzilla-daemon
2020-12-27  3:03 ` bugzilla-daemon
2020-12-27  3:31 ` bugzilla-daemon
2020-12-30 20:53 ` bugzilla-daemon
2021-01-01 18:04 ` bugzilla-daemon
2021-01-05 20:43 ` bugzilla-daemon
2021-02-05  4:35 ` bugzilla-daemon [this message]
2021-02-05 15:40 ` bugzilla-daemon
2021-02-05 17:46 ` bugzilla-daemon
2021-02-05 18:37 ` bugzilla-daemon
2021-02-05 19:01 ` bugzilla-daemon
2021-02-06 16:52 ` bugzilla-daemon
2021-02-09  4:40 ` bugzilla-daemon
2021-02-13  1:30 ` bugzilla-daemon
2021-03-08  3:01 ` 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-210849-2300-chOq2KGOuR@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.