From: Dave Airlie <airlied@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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 14:24:26 +1000 [thread overview]
Message-ID: <CAPM=9twUvRoVcWHhBH7yuDDVj8K8aM0APQ8Yx3cx19keLJP8Gg@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=whWcektQzPJgSPa2DC3wMPxgLh8fJVQWeo8i99XMXPjfg@mail.gmail.com>
On Thu, 4 Aug 2022 at 14:02, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Wed, Aug 3, 2022 at 8:53 PM Dave Airlie <airlied@gmail.com> wrote:
> >
> > > It works on my intel laptop, so it's amdgpu somewhere.
> >
> > I'll spin my ryzen up to see if I can reproduce, and test against the
> > drm-next pre-merge tree as well.
>
> So it's not my merge - I've had a bad result in the middle of the DRM
> history too.
>
> On a positive note, my arm64 machine works fine, but that's just using
> fbdev so ...
>
> But another datapoint to say that it's amdgpu-specific. Not that that
> was really in doubt.
I've reproduced it, I'll send you a revert pile when I confirm it is
the buddy allocator.
Dave.
next prev parent reply other threads:[~2022-08-04 4:24 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 [this message]
2022-08-04 4:27 ` Linus Torvalds
2022-08-04 4:46 ` Linus Torvalds
2022-08-04 5:25 ` Dave Airlie
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=9twUvRoVcWHhBH7yuDDVj8K8aM0APQ8Yx3cx19keLJP8Gg@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--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).