[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPM=9tzDWmYBKQGB0ybDzhYHkg0p98_6PJA8OuPahRep8+QPvQ@mail.gmail.com>
Date: Thu, 31 Jul 2025 14:36:11 +1000
From: Dave Airlie <airlied@...il.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Simona Vetter <simona@...ll.ch>, dri-devel <dri-devel@...ts.freedesktop.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] drm for 6.17-rc1
On Thu, 31 Jul 2025 at 14:32, Dave Airlie <airlied@...il.com> wrote:
>
> On Thu, 31 Jul 2025 at 14:27, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
> >
> > On Wed, 30 Jul 2025 at 21:21, Dave Airlie <airlied@...il.com> wrote:
> > >
> > > Okay I don't have an rx580, but I have an rx480 which is pretty close,
> > > but it is booting fine with your tree at least, DP and HDMI connected,
> > > so it's not widespread AMD breakage, anything in journalctl/dmesg?
> >
> > The machine doesn't come up far enough to mount a filesystem - my
> > disks are all encrypted, I never even get to the "type your password"
> > thing.
> >
> > So no logs.
> >
> > The good news is that it's bisecting without any ambiguity. So nowhere
> > near as painful as last merge window.
> >
>
> You can boot with modprobe.blacklist=amdgpu and then modprobe amdgpu
> once it boots and see if dmesg
>
> But hopefully bisect lands somewhere good,
>
> Just seeing if there's been any NULL ptrs on old GPU reported.
https://lore.kernel.org/dri-devel/20250717204819.731936-1-mustela@erminea.space/
is the only thing I can see that might not be in the merge.
Dave.
Powered by blists - more mailing lists