[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <11368b7c0b7370aea61b3dda73e462fb70f306a7.camel@xry111.site>
Date: Sun, 22 Sep 2024 14:56:57 +0800
From: Xi Ruoyao <xry111@...111.site>
To: Christoph Hellwig <hch@...radead.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org, iommu@...ts.linux.dev
Subject: Re: [GIT PULL] dma-mapping updates for Linux 6.12
On Sat, 2024-09-21 at 21:58 -0700, Christoph Hellwig wrote:
> On Sun, Sep 22, 2024 at 01:49:35AM +0800, Xi Ruoyao wrote:
> > On Sat, 2024-09-21 at 06:51 -0700, Christoph Hellwig wrote:
> > > On Sat, Sep 21, 2024 at 03:56:11PM +0800, Xi Ruoyao wrote:
> > > > because the laptop has no serial output. And the behavior seems not
> > > > deterministic. I have some transcript of messages I photoed in several
> > > > boot attempts though:
> > >
> > > Can you send me the photos of the messages? Probably best offlist
> > > as the lists don't like attachments.
> >
> > I've got something better: one attempt to boot
> > b5c58b2fdc427e7958412ecb2de2804a1f7c1572 succeeded and I got a dmesg
> > containing some Oops traces.
> >
> > The camera does *not* work. And when I rebooted the system it hung
> > (presumably related to these Oops).
>
> So that oops actually comes from the sounds code and looks unrelated
> to DMA. I suspect that oops is what caused your crashes and thus
> messed up the DMA bisection. Can you try to boot with CONFIG_SND
> disabled and see where the bisection for the video issues lands?
With SND disabled, b5c58b2fdc427e7958412ecb2de2804a1f7c1572 boots fine
(no oops), but the camera does not work.
f69e342eec008e1bab772d3963c3dd9979293e13 boots fine and the camera works
fine.
So the first bad commit is b5c58b2fdc427e7958412ecb2de2804a1f7c1572.
--
Xi Ruoyao <xry111@...111.site>
School of Aerospace Science and Technology, Xidian University
Powered by blists - more mailing lists