diff options
author | H. Peter Anvin <hpa@linux.intel.com> | 2014-03-07 15:05:20 -0800 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-03-23 21:38:15 -0700 |
commit | a56c57c055ecc75f4375d60c783a0b578edd763c (patch) | |
tree | 052089d136175229dbe54728c1c12d4e32db76b2 /scripts/setlocalversion | |
parent | 783d444c6dbca17d2b15918ef6b30add2ba586b8 (diff) | |
download | linux-3.10-a56c57c055ecc75f4375d60c783a0b578edd763c.tar.gz linux-3.10-a56c57c055ecc75f4375d60c783a0b578edd763c.tar.bz2 linux-3.10-a56c57c055ecc75f4375d60c783a0b578edd763c.zip |
x86: Ignore NMIs that come in during early boot
commit 5fa10196bdb5f190f595ebd048490ee52dddea0f upstream.
Don Zickus reports:
A customer generated an external NMI using their iLO to test kdump
worked. Unfortunately, the machine hung. Disabling the nmi_watchdog
made things work.
I speculated the external NMI fired, caused the machine to panic (as
expected) and the perf NMI from the watchdog came in and was latched.
My guess was this somehow caused the hang.
----
It appears that the latched NMI stays latched until the early page
table generation on 64 bits, which causes exceptions to happen which
end in IRET, which re-enable NMI. Therefore, ignore NMIs that come in
during early execution, until we have proper exception handling.
Reported-and-tested-by: Don Zickus <dzickus@redhat.com>
Link: http://lkml.kernel.org/r/1394221143-29713-1-git-send-email-dzickus@redhat.com
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'scripts/setlocalversion')
0 files changed, 0 insertions, 0 deletions