From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111792] [AMD tahiti xt] amd-staging-drm-next broken since linux 5.3.0-rc3 rebase
Date: Wed, 25 Sep 2019 02:24:43 +0000 [thread overview]
Message-ID: <bug-111792-502-cV5BBbqu0P@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111792-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1014 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111792
--- Comment #3 from Sylvain BERTRAND <sylvain.bertrand@gmail.com> ---
This bisection is kind of a pain, as usual on the 'rebase breakage'. I had to
start manually to find a "segment" with good enough good/bad data for bisect.
On this bisected segment, amd-staging-drm-next branch, the first bad commit is:
commit 1929059893022a3bbed43934c7313e66aad7346b
Author: Prike Liang <Prike.Liang@amd.com>
Date: Mon May 27 16:05:50 2019 +0800
drm/amd/amdgpu: add RLC firmware to support raven1 refresh
Use SMU firmware version to indentify the raven1 refresh device and
then load homologous RLC FW.
Signed-off-by: Prike Liang <Prike.Liang@amd.com>
Suggested-by: Huang Rui<Ray.Huang@amd.com>
Reviewed-by: Huang Rui <ray.huang@amd.com>
Reviewed-by: Evan Quan <evan.quan@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2194 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
next prev parent reply other threads:[~2019-09-25 2:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 21:11 [Bug 111792] [AMD tahiti xt] amd-staging-drm-next broken since linux 5.3.0-rc3 rebase bugzilla-daemon
2019-09-23 21:11 ` bugzilla-daemon
2019-09-23 21:13 ` bugzilla-daemon
2019-09-25 2:24 ` bugzilla-daemon [this message]
2019-09-25 2:52 ` bugzilla-daemon
2019-09-25 12:04 ` bugzilla-daemon
2019-09-25 12:06 ` bugzilla-daemon
2019-09-25 14:04 ` bugzilla-daemon
2019-09-25 15:10 ` bugzilla-daemon
2019-09-25 15:14 ` bugzilla-daemon
2019-09-25 15:31 ` bugzilla-daemon
2019-09-25 15:52 ` bugzilla-daemon
2019-09-25 19:43 ` bugzilla-daemon
2019-09-25 19:54 ` bugzilla-daemon
2019-09-25 20:22 ` bugzilla-daemon
2019-11-19 9:52 ` 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-111792-502-cV5BBbqu0P@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