From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: Genes Lists <lists@sapience.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org,
linux-media@vger.kernel.org, sakari.ailus@linux.intel.com,
bingbu.cao@intel.com
Subject: Re: Linux 6.12.4 - crash dma_alloc_attrs+0x12b via ipu6
Date: Mon, 9 Dec 2024 18:40:09 +0100 [thread overview]
Message-ID: <Z1creSb6XVWtpyUl@linux.intel.com> (raw)
In-Reply-To: <5321021d929cebf7268fc163ddb92cb740c09c82.camel@sapience.com>
On Mon, Dec 09, 2024 at 10:11:17AM -0500, Genes Lists wrote:
> On Mon, 2024-12-09 at 09:52 -0500, Genes Lists wrote:
> > ortly after booting in dma_alloc_attrs - maybe
> > triggered in ipu6_probe.
>
> >
> Mainline v6.13-rc2 works fine on same hardware (i did need to add the
This upstream commit is missing.
commit 1d4a000289979cc7f2887c8407b1bfe2a0918354
Author: Bingbu Cao <bingbu.cao@intel.com>
Date: Wed Oct 16 15:53:02 2024 +0800
media: ipu6: use the IPU6 DMA mapping APIs to do mapping
It does not apply cleanly on 6.12.4, I'll post backport shortly.
Regards
Stanislaw
next prev parent reply other threads:[~2024-12-09 17:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 10:48 Linux 6.12.4 Greg Kroah-Hartman
2024-12-09 10:48 ` Greg Kroah-Hartman
2024-12-09 14:52 ` Linux 6.12.4 - crash dma_alloc_attrs+0x12b via ipu6 Genes Lists
2024-12-09 15:11 ` Genes Lists
2024-12-09 17:40 ` Stanislaw Gruszka [this message]
2024-12-09 18:04 ` Genes Lists
2024-12-09 15:18 ` Greg Kroah-Hartman
2024-12-09 16:12 ` Genes Lists
2024-12-10 7:15 ` Sakari Ailus
2024-12-10 8:58 ` Jani Nikula
2024-12-10 11:16 ` Genes Lists
2024-12-10 12:24 ` Jani Nikula
2024-12-10 12:37 ` Greg Kroah-Hartman
2024-12-10 15:18 ` Stanislaw Gruszka
2024-12-10 16:00 ` Genes Lists
2024-12-10 16:53 ` Genes Lists
2024-12-10 15:40 ` Genes Lists
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=Z1creSb6XVWtpyUl@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=bingbu.cao@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lists@sapience.com \
--cc=sakari.ailus@linux.intel.com \
--cc=stable@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