From: Thorsten Sperber <lists+debian@aero2k.de>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: 1111027@bugs.debian.org, Thomas Gleixner <tglx@linutronix.de>,
"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: Mon, 22 Sep 2025 19:33:02 +0200 [thread overview]
Message-ID: <60c824f2-667f-4957-bfe1-145a79e01ac5@aero2k.de> (raw)
In-Reply-To: <2pdp3kq4qebdxizprbnaq6omh4dvxdlktokvr37b7nlkf4po3b@fxzmgmi47wxx>
Hi,
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.
Just to get things right: the machine stopped crashing fatally - I believe with the addition of intel_iommu=off. It starts flashing red, logs those errors in kernel buffer, but stays running. I'd like to backtrack that later on, maybe after the weekend, removing all params and seeing where things go. Unless you'd like me to test something else before that.
Best regards
Thorsten
On 9/18/25 10:57, Uwe Kleine-König wrote:
> Hello Thorsten,
>
> after writing the mail to Rafael Thomas provided the idea on irc to test
> using
>
> intel_idle.max_cstate=2
>
> (or =1 or =0) on the kernel command line given that the splat hints at
> this happening for C3.
>
> Can you please add this (with =2) to your bootloader and if the problem
> happens again, tell us here and reduce the number further?
>
> Best regards
> Uwe
next prev parent reply other threads:[~2025-09-22 17:42 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 [this message]
2025-09-23 10:31 ` Thomas Gleixner
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=60c824f2-667f-4957-bfe1-145a79e01ac5@aero2k.de \
--to=lists+debian@aero2k.de \
--cc=1111027@bugs.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox