Re: [PATCH v2] NMI: fix NMI period is not correct when cpufrequency changes issue.

[Peter Zijlstra]

On Mon, 2013-04-22 at 00:50 +0000, Pan, Zhenjie wrote:
> This make watchdog reset happen before hard lockup detect.

Doesn't your watchdog trigger an NMI you can use to print the panic?

ISTR some people (hi Don!) spending quite a lot of time to make this
work for some other platforms.

IIRC those things would fire an NMI at some point and then hard-reset
the machine not much later.. the difficulty was detecting this
'unclaimed' nmi and allowing drivers to register for it.

NMI_UNKNOWN and unknown_nmi_panic are the result of that.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/