mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: Christoph Hellwig <hch@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: Re: [GIT PULL] dma-mapping updates for Linux 6.12
Date: Fri, 20 Sep 2024 05:41:51 +0800	[thread overview]
Message-ID: <971fbb889da38ca4e60f3dedde29ea43e9338d68.camel@xry111.site> (raw)
In-Reply-To: <ZuvYnXzbM2qfXQPT@infradead.org>

On Thu, 2024-09-19 at 09:54 +0200, Christoph Hellwig wrote:
> The following changes since commit 47ac09b91befbb6a235ab620c32af719f8208399:
> 
>   Linux 6.11-rc4 (2024-08-18 13:17:27 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-6.12-2024-09-19
> 
> for you to fetch changes up to a5fb217f13f74b2af2ab366ffad522bae717f93c:
> 
>   dma-mapping: reflow dma_supported (2024-09-12 16:28:00 +0200)
> 
> ----------------------------------------------------------------
> dma-mapping updates for linux 6.12
> 
>  - support DMA zones for arm64 systems where memory starts at > 4GB
>    (Baruch Siach, Catalin Marinas)
>  - support direct calls into dma-iommu and thus obsolete dma_map_ops for
>    many common configurations (Leon Romanovsky)
>  - add DMA-API tracing (Sean Anderson)
>  - remove the not very useful return value from various dma_set_* APIs
>    (Christoph Hellwig)
>  - misc cleanups and minor optimizations (Chen Y, Yosry Ahmed,
>    Christoph Hellwig)

Hi Christoph and Linus,

This breaks using my laptop camera with gstreamer (with "gst-launch-1.0
v4l2src ! videoconvert ! autovideosink" or GNOME snapshot).

"git bisect" gives:

The first bad commit could be any of:
b5a73bf4d1de95e620bf5f592557b81f71c76f0e
833bd284a45448f04ab9fcd4fdf7ef594d458eed
c42a01264ba1497eb3193c08ff3c2656d98250a6
560a861ab4174b42240157ab5cebe36b8c7bc418
b5c58b2fdc427e7958412ecb2de2804a1f7c1572
334304ac2baca7f3e821c47cf5129d90e7a6b1e6

(I had to use "git bisect skip" several times because I encountered
kernel panic on boot at some revisions.)

Reverting the merge fixes the issue.  I'm not sure if this is related to
the camera model (I can borrow another camera to test tomorrow).

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

  parent reply	other threads:[~2024-09-19 21:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19  7:54 Christoph Hellwig
2024-09-19  9:40 ` pr-tracker-bot
2024-09-19 21:41 ` Xi Ruoyao [this message]
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
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=971fbb889da38ca4e60f3dedde29ea43e9338d68.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

all inboxes | Powered by JetHome®