From: Genes Lists <lists@sapience.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org
Cc: 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, 09 Dec 2024 10:11:17 -0500 [thread overview]
Message-ID: <5321021d929cebf7268fc163ddb92cb740c09c82.camel@sapience.com> (raw)
In-Reply-To: <c0e94be466b367f1a3cfdc3cb7b1a4f47e5953ae.camel@sapience.com>
[-- Attachment #1.1: Type: text/plain, Size: 391 bytes --]
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
drm patches [1] without which there are no graphics).
gene
[1] drm fixes required with mainline:
https://patchwork.freedesktop.org/series/141911/
--
Gene
[-- Attachment #1.2: Type: text/html, Size: 1279 bytes --]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-12-09 15:11 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 [this message]
2024-12-09 17:40 ` Stanislaw Gruszka
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=5321021d929cebf7268fc163ddb92cb740c09c82.camel@sapience.com \
--to=lists@sapience.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=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
all inboxes | Powered by JetHome®