linux-kernel - Re: NMI: IOCK error (debug interrupt?) for reason 71 on CPU 0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <60c824f2-667f-4957-bfe1-145a79e01ac5@aero2k.de>
Date: Mon, 22 Sep 2025 19:33:02 +0200
From: Thorsten Sperber <lists+debian@...o2k.de>
To: Uwe Kleine-König <u.kleine-koenig@...libre.com>
Cc: 1111027@...s.debian.org, Thomas Gleixner <tglx@...utronix.de>,
 "Rafael J. Wysocki" <rafael@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: NMI: IOCK error (debug interrupt?) for reason 71 on CPU 0

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