linux-kernel - Re: x86, nmi: IOCK error

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: <alpine.DEB.2.21.2201082302580.56863@angie.orcam.me.uk>
Date:   Sat, 8 Jan 2022 23:09:45 +0000 (GMT)
From:   "Maciej W. Rozycki" <macro@...am.me.uk>
To:     Muni Sekhar <munisekharrms@...il.com>
cc:     noloader@...il.com, linux-x86_64@...r.kernel.org,
        kernelnewbies <kernelnewbies@...nelnewbies.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: x86, nmi: IOCK error

On Tue, 23 Nov 2021, Muni Sekhar wrote:

> > Red Hat has a good article on the subject at
> > https://access.redhat.com/solutions/42261.
> NMI: IOCK error (debug interrupt?) for reason 60 on CPU 0.
> NMI: IOCK error (debug interrupt?) for reason 70 on CPU 0.
> What's the difference between reason 60 & reason 70? I was not able to
> find it in the above mentioned link.

 For any practical purpose the value of bit #4 in the NMI Status and 
Control Register does not matter as (in a compatible system) it merely 
toggles with every DRAM refresh cycle.

 HTH,

  Maciej