All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 200607] [amdgpu] Polaris10 driver crash with the recent linux-firmware update
Date: Thu, 19 Jul 2018 19:06:53 +0000	[thread overview]
Message-ID: <bug-200607-2300-pFkJy4mcQ5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200607-2300@https.bugzilla.kernel.org/>

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

--- Comment #2 from Parker Reed (parker.l.reed@gmail.com) ---
I'm streaming via Steam in-home streaming and occasionally a fullscreen
application will mess things up. When I reboot, SDDM/Plasma hang because of
that driver crash. Leaving the up to date firmware files in there, it comes
back after a couple reboots (randomly), and continues to work for a while. For
now I have just downgraded back to my distro shipped linux-firmware.

I'm not sure if the fullscreen issue is related but I know it definitely causes
SDDM/Plasma init to freak out. So I'd say that's when it hangs the most for me.

-- 
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:[~2018-07-19 19:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19 18:59 [Bug 200607] New: [amdgpu] Polaris10 driver crash with the recent linux-firmware update bugzilla-daemon
2018-07-19 19:02 ` [Bug 200607] " bugzilla-daemon
2018-07-19 19:06 ` bugzilla-daemon [this message]
2018-07-19 19:15 ` bugzilla-daemon
2018-07-19 19:21 ` bugzilla-daemon
2018-07-19 20:27 ` bugzilla-daemon
2018-07-19 20:27 ` bugzilla-daemon
2018-07-19 20:27 ` bugzilla-daemon
2018-07-19 20:28 ` bugzilla-daemon
2018-07-20  7:52 ` bugzilla-daemon
2018-07-20 12:55 ` [Bug 200607] [amdgpu] Polaris10 driver crash with DC enabled 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-200607-2300-pFkJy4mcQ5@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.