Bug#1111027: NMI: IOCK error (debug interrupt?) for reason 71 on CPU 0

[Thomas Gleixner <tglx@linutronix.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