Linux IOMMU Development
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	 linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: Re: [GIT PULL] dma-mapping updates for Linux 6.12
Date: Sun, 22 Sep 2024 14:56:57 +0800	[thread overview]
Message-ID: <11368b7c0b7370aea61b3dda73e462fb70f306a7.camel@xry111.site> (raw)
In-Reply-To: <Zu-kCdMau6127_vM@infradead.org>

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@xry111.site>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2024-09-22  6:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19  7:54 [GIT PULL] dma-mapping updates for Linux 6.12 Christoph Hellwig
2024-09-19  9:40 ` pr-tracker-bot
2024-09-19 21:41 ` Xi Ruoyao
2024-09-20 11:26   ` Christoph Hellwig
2024-09-20 14:06     ` Christoph Hellwig
2024-09-20 17:15       ` Xi Ruoyao
2024-09-20 17:48         ` Xi Ruoyao
2024-09-21  5:12         ` Christoph Hellwig
2024-09-21  7:56           ` Xi Ruoyao
2024-09-21 13:51             ` Christoph Hellwig
2024-09-21 17:49               ` Xi Ruoyao
2024-09-22  4:58                 ` Christoph Hellwig
2024-09-22  6:56                   ` Xi Ruoyao [this message]
2024-09-22  7:19                     ` Christoph Hellwig
2024-09-22 10:32                       ` Leon Romanovsky
2024-09-22 14:03                         ` Christoph Hellwig
2024-09-22 12:40                       ` Xi Ruoyao

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=11368b7c0b7370aea61b3dda73e462fb70f306a7.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=hch@infradead.org \
    --cc=iommu@lists.linux.dev \
    --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