dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206575] [amdgpu] [drm] No video signal on resume from suspend, R9 380
Date: Fri, 20 Mar 2020 22:03:47 +0000	[thread overview]
Message-ID: <bug-206575-2300-5OaB9R67nN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206575-2300@https.bugzilla.kernel.org/>

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

--- Comment #16 from Joe Ramsey (kernel_bugzilla@joeramsey.com) ---
(In reply to Alex Deucher from comment #15)
> (In reply to Joe Ramsey from comment #14)
> > Looks like this has been corrected in 5.6... is there any intent to include
> > the fix in any 5.5 kernel or will we just have to wait for 5.6?
> 
> Can you identify the fix?

If I understood Noel Maersk's and Thomas Frank's posts reverting
1ea8751bd28d1ec2b36a56ec6bc1ac28903d09b4 resolves the issue.  The Reddit thread
that was referenced
(https://www.reddit.com/r/archlinux/comments/f7oti1/issue_with_resume_from_suspend_black_backlit/)
seems to indicate that it's resolved in 5.6.  Was wondering if whatever fix was
applied to 5.6 would also be applied to 5.5.  Could be I've completely
misunderstood things.

I'm running Slackware and have been using the -current kernel packages
(currently at 5.4.25), but the kernel modules for virtualbox don't seem to be
compiling under that kernel for some reason.  I tried several of the recent 5.5
releases (5.5.8-5.5.10), and can get the virtualbox kernel modules to compile
under them, but they all seem to have this bug.  Was hoping to get one kernel
that would allow my laptop to suspend and also compile the virtualbox modules. 
:^)

-- 
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:[~2020-03-20 22:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 16:28 [Bug 206575] New: [amdgpu] [drm] No video signal on resume from suspend, R9 380 bugzilla-daemon
2020-02-17 16:29 ` [Bug 206575] " bugzilla-daemon
2020-02-17 16:29 ` bugzilla-daemon
2020-02-17 16:30 ` bugzilla-daemon
2020-02-17 16:30 ` bugzilla-daemon
2020-02-17 16:33 ` bugzilla-daemon
2020-02-17 16:38 ` bugzilla-daemon
2020-02-18 17:47 ` bugzilla-daemon
2020-02-18 21:33 ` bugzilla-daemon
2020-02-18 21:44 ` bugzilla-daemon
2020-02-18 22:06 ` bugzilla-daemon
2020-02-19 19:51 ` bugzilla-daemon
2020-02-21  0:42 ` bugzilla-daemon
2020-02-24  2:12 ` bugzilla-daemon
2020-03-16  9:39 ` bugzilla-daemon
2020-03-20 19:54 ` bugzilla-daemon
2020-03-20 20:15 ` bugzilla-daemon
2020-03-20 22:03 ` bugzilla-daemon [this message]
2020-03-23  5:06 ` bugzilla-daemon
2020-03-24 20:11 ` bugzilla-daemon
2020-04-10  8:35 ` bugzilla-daemon
2020-04-11 13:56 ` bugzilla-daemon
2020-04-11 13:59 ` bugzilla-daemon
2020-04-14  9:09 ` bugzilla-daemon
2020-04-14 13:28 ` bugzilla-daemon
2020-04-14 13:31 ` bugzilla-daemon
2020-04-14 14:10 ` bugzilla-daemon
2020-04-15 11:43 ` bugzilla-daemon
2020-04-15 11:44 ` bugzilla-daemon
2020-04-15 11:45 ` 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-206575-2300-5OaB9R67nN@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).