From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Genes Lists <lists@sapience.com>
Cc: 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 16:18:57 +0100 [thread overview]
Message-ID: <2024120934-wreckage-hazily-166f@gregkh> (raw)
In-Reply-To: <c0e94be466b367f1a3cfdc3cb7b1a4f47e5953ae.camel@sapience.com>
On Mon, Dec 09, 2024 at 09:52:17AM -0500, Genes Lists wrote:
> On Mon, 2024-12-09 at 11:48 +0100, Greg Kroah-Hartman wrote:
> > I'm announcing the release of the 6.12.4 kernel.
> >
> > All users of the 6.12 kernel series must upgrade.
> > ...
> > greg k-h
> >
> >
>
> FYI 6.12.4 got a crash shortly after booting in dma_alloc_attrs - maybe
> triggered in ipu6_probe. Crash only happened on laptop with ipu6. All
> other machines are running fine.
Did older kernels work? Did 6.12.1? If so, can you do 'git bisect' to
find the offending change?
thanks,
greg k-h
next prev parent reply other threads:[~2024-12-09 15:19 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
2024-12-09 18:04 ` Genes Lists
2024-12-09 15:18 ` Greg Kroah-Hartman [this message]
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=2024120934-wreckage-hazily-166f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=bingbu.cao@intel.com \
--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