Comment # 16 on bug 1042933 from Thomas Blume

(In reply to Borislav Petkov from comment #15)
> 
> 	pr_err("%s: NMI raised\n", __func__);
> 
> 	//tblume: suppress NMI
> 	return NMI_HANDLED;
> 
> so that we can see when it hits.

Ok, now I get this:

-->
teviot:~ # /systemd-testsuite/run/test-watchdog 
Hardware watchdo[  356.497530] hpwdt: tblume: reload variable is: 234
[  356.497597] hpwdt: tblume: New timer passed in is 10 seconds
g 'HPE iLO2+ HW [  356.499686] hpwdt: tblume: reload variable is: 78
Watchdog Timer',[  356.499717] hpwdt: tblume: reload variable is: 78
 version 0
Set [  356.500778] hpwdt: tblume: reload variable is: 78
hardware watchdog to 10s.
Pinging...
[  356.501780] hpwdt: tblume: reload variable is: 78
[  357.745055] hpwdt: hpwdt_pretimeout: NMI raised
Pinging...
[  361.502857] hpwdt: tblume: reload variable is: 78
Pinging...
Pinging...
[  366.502937] hpwdt: tblume: reload variable is: 78
[  371.504020] hpwdt: tblume: reload variable is: 78
[  371.508413] systemd-journald[363]: Sent WATCHDOG=1 notification.
Pinging...
[  376.505052] hpwdt: tblume: reload variable is: 78
--<

I also found that the NMI is only raised at the first test run after reboot.
Wen I repeat the test, there is no more NMI and the ping just succeeds - until
the next reboot.