From: Dave Airlie <airlied@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
Daniel Wheeler <daniel.wheeler@amd.com>,
Harry Wentland <Harry.Wentland@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm for 5.20/6.0
Date: Thu, 4 Aug 2022 15:25:35 +1000 [thread overview]
Message-ID: <CAPM=9twRb4c62e0mU9CwOTAYMkR6YCRR5=KLTrSKoLbJ7RB9xw@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wih3NEubvTye4URZOmLYu6G+ZT9cngepo0z++ogCWUymQ@mail.gmail.com>
On Thu, 4 Aug 2022 at 14:46, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Wed, Aug 3, 2022 at 9:27 PM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > I'll do a few more. It's close enough already that it should be just
> > four more reboots to pinpoint exactly which commit breaks.
>
> commit 5d945cbcd4b16a29d6470a80dfb19738f9a4319f is the first bad commit.
>
> I think it's supposed to make no semantic changes, but it clearly does.
>
> What a pain to figure out what's wrong in there, and I assume it
> doesn't revert cleanly either.
>
> Bringing in the guilty parties. See
>
> https://lore.kernel.org/all/CAHk-=wj+yzauNXiEwHfCrkbdLSQkizdR1Q3YJLAqPo6AVq2_4Q@mail.gmail.com/
>
> for the beginning of this thread.
I think I've tracked it down, looks like it would only affect GFX8
cards, which might explain why you and I have seen it, and I haven't
seen any other reports.
pretty sure you have an rx580, and I just happen to have a fiji card
in this machine right now.
I'll retest on master and send you a fixup patch.
Dave.
next prev parent reply other threads:[~2022-08-04 5:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 5:37 [git pull] drm for 5.20/6.0 Dave Airlie
2022-08-04 2:46 ` Linus Torvalds
2022-08-04 3:16 ` Linus Torvalds
2022-08-04 3:37 ` Dave Airlie
2022-08-04 3:47 ` Linus Torvalds
2022-08-04 3:52 ` Dave Airlie
2022-08-04 4:02 ` Linus Torvalds
2022-08-04 4:24 ` Dave Airlie
2022-08-04 4:27 ` Linus Torvalds
2022-08-04 4:46 ` Linus Torvalds
2022-08-04 5:25 ` Dave Airlie [this message]
2022-08-04 5:52 ` Dave Airlie
2022-08-04 3:17 ` pr-tracker-bot
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='CAPM=9twRb4c62e0mU9CwOTAYMkR6YCRR5=KLTrSKoLbJ7RB9xw@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=Harry.Wentland@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=alexander.deucher@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.wheeler@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).