| 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
| ||
|
Message-ID: <1366663056.8337.7.camel@laptop> Date: Mon, 22 Apr 2013 22:37:36 +0200 From: Peter Zijlstra <a.p.zijlstra@...llo.nl> To: "Pan, Zhenjie" <zhenjie.pan@...el.com> Cc: Don Zickus <dzickus@...hat.com>, Stephane Eranian <eranian@...gle.com>, "paulus@...ba.org" <paulus@...ba.org>, "mingo@...hat.com" <mingo@...hat.com>, "acme@...stprotocols.net" <acme@...stprotocols.net>, "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>, "tglx@...utronix.de" <tglx@...utronix.de>, "Liu, Chuansheng" <chuansheng.liu@...el.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v2] NMI: fix NMI period is not correct when cpu frequency changes issue. 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@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists