public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Genes Lists <lists@sapience.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	torvalds@linux-foundation.org, stable@vger.kernel.org,
	linux-media@vger.kernel.org, bingbu.cao@intel.com,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Tvrtko Ursulin <tursulin@ursulin.net>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org
Subject: Re: Linux 6.12.4 - crash dma_alloc_attrs+0x12b via ipu6
Date: Tue, 10 Dec 2024 13:37:11 +0100	[thread overview]
Message-ID: <2024121001-senator-raffle-a371@gregkh> (raw)
In-Reply-To: <87bjxjzpwn.fsf@intel.com>

On Tue, Dec 10, 2024 at 02:24:56PM +0200, Jani Nikula wrote:
> On Tue, 10 Dec 2024, Genes Lists <lists@sapience.com> wrote:
> > On Tue, 2024-12-10 at 10:58 +0200, Jani Nikula wrote:
> >> On Tue, 10 Dec 2024, Sakari Ailus <sakari.ailus@linux.intel.com>
> >> wrote:
> >> > Hi,
> >> > 
> >> > > ...
> >> > > 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.
> >> > 
> >> > Have you read the dmesg further than the IPU6 related warning? The
> >> > IPU6
> >> > driver won't work (maybe not even probe?) but if the system
> >> > crashes, it
> >> > appears unlikely the IPU6 drivers would have something to do with
> >> > that.
> >> > Look for warnings on linked list corruption later, they seem to be
> >> > coming
> >> > from the i915 driver.
> >> 
> >> And the list corruption is actually happening in
> >> cpu_latency_qos_update_request(). I don't see any i915 changes in
> >> 6.12.4
> >> that could cause it.
> >> 
> >> I guess the question is, when did it work? Did 6.12.3 work?
> >> 
> >> 
> >> BR,
> >> Jani.
> >
> >
> >  - 6.12.1 worked
> >
> >  - mainline - works (but only with i915 patch set [1] otherwise there
> > are no graphics at all)
> >
> >     [1] https://patchwork.freedesktop.org/series/141911/
> >
> > - 6.12.3 - crashed (i see i915 not ipu6) and again it has       
> >     cpu_latency_qos_update_request+0x61/0xc0
> 
> Thanks for testing.
> 
> There are no changes to either i915 or kernel/power between 6.12.1 and
> 6.12.4.
> 
> There are some changes to drm core, but none that could explain this.
> 
> Maybe try the same kernels a few more times to see if it's really
> deterministic? Not that I have obvious ideas where to go from there, but
> it's a clue nonetheless.

'git bisect' would be nice to run if possible...

  reply	other threads:[~2024-12-10 12:37 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
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 [this message]
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=2024121001-senator-raffle-a371@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bingbu.cao@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=lists@sapience.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=simona@ffwll.ch \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tursulin@ursulin.net \
    /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