All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Thorsten Sperber" <lists+debian@aero2k.de>,
	"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: 1111027@bugs.debian.org, "Rafael J. Wysocki" <rafael@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: NMI: IOCK error (debug interrupt?) for reason 71 on CPU 0
Date: Tue, 23 Sep 2025 12:31:23 +0200	[thread overview]
Message-ID: <87bjn14g04.ffs@tglx> (raw)
In-Reply-To: <60c824f2-667f-4957-bfe1-145a79e01ac5@aero2k.de>

On Mon, Sep 22 2025 at 19:33, Thorsten Sperber wrote:
>
> thanks for your help. It's been four days now, I'd say above average
> (last was five days) - and no crash yet. I'm going to wait at least
> until the weekend before naming a winner, but that's already looking
> pretty good.

Thanks for trying.

I suggested to try intel_idle.max_cstate=2 because these unknown NMI
backtraces all originated from a MWAIT(C3).

Can you reboot into the working 6.1.y kernel at some point and check
which idle driver is used there?

    cat /sys/devices/system/cpu/cpuidle/current_driver

and which states are advertised:

    ls /sys/devices/system/cpu/cpu0/cpuidle/state

Thanks,

        tglx

  reply	other threads:[~2025-09-23 10:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-18  8:27 NMI: IOCK error (debug interrupt?) for reason 71 on CPU 0 Uwe Kleine-König
2025-09-18  8:57 ` Uwe Kleine-König
2025-09-22 17:33   ` Thorsten Sperber
2025-09-23 10:31     ` Thomas Gleixner [this message]
2025-09-24 17:20       ` Thorsten Sperber
2025-09-24 22:10         ` Thomas Gleixner
2025-09-25 15:27           ` Thorsten Sperber

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=87bjn14g04.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=1111027@bugs.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists+debian@aero2k.de \
    --cc=rafael@kernel.org \
    --cc=u.kleine-koenig@baylibre.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.