dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108644] driver/card crashes with latest polaris11 firmware
Date: Mon, 05 Nov 2018 16:45:43 +0000	[thread overview]
Message-ID: <bug-108644-502-1vLmZ8wpGB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108644-502@http.bugs.freedesktop.org/>


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

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

--- Comment #2 from Alex Deucher <alexdeucher@gmail.com> ---
Does this patch help?
https://patchwork.freedesktop.org/patch/259364/

Can you bisect which firmware commit
(https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git)
caused the regression and then narrow down which firmware updated causes the
issue?  I'd start with the smc firmware and they try the rlc, followed by the
CP (mec, me, pfp, ce).

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

[-- Attachment #1.2: Type: text/html, Size: 1506 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-11-05 16:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-03 15:32 [Bug 108644] driver/card crashes with latest polaris11 firmware bugzilla-daemon
2018-11-05 16:31 ` bugzilla-daemon
2018-11-05 16:45 ` bugzilla-daemon [this message]
2018-11-05 17:26 ` bugzilla-daemon
2018-11-15 12:35 ` bugzilla-daemon
2018-11-15 12:37 ` bugzilla-daemon
2019-11-19  9: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-108644-502-1vLmZ8wpGB@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox