Hi all, The following message is seen on the console "NMI: IOCK error (debug interrupt?) for reason 60 on CPU 0.", what does it mean? Does this likely confirm the CPU is faulty? If so, how to resolve this? -- Thanks, Sekhar
On Mon, Nov 22, 2021 at 11:03 PM Muni Sekhar <munisekharrms@gmail.com> wrote:
The following message is seen on the console "NMI: IOCK error (debug interrupt?) for reason 60 on CPU 0.", what does it mean?
Red Hat has a good article on the subject at https://access.redhat.com/solutions/42261. Jeff
On Tue, Nov 23, 2021 at 10:44 AM Jeffrey Walton <noloader@gmail.com> wrote:
On Mon, Nov 22, 2021 at 11:03 PM Muni Sekhar <munisekharrms@gmail.com> wrote:
The following message is seen on the console "NMI: IOCK error (debug interrupt?) for reason 60 on CPU 0.", what does it mean?
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.
Jeff
-- Thanks, Sekhar
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
participants (3)
-
Jeffrey Walton -
Maciej W. Rozycki -
Muni Sekhar