| 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: <alpine.DEB.2.02.1307051802070.32106@ionos.tec.linutronix.de> Date: Fri, 5 Jul 2013 18:02:41 +0200 (CEST) From: Thomas Gleixner <tglx@...utronix.de> To: Dave Jones <davej@...hat.com> cc: Linus Torvalds <torvalds@...ux-foundation.org>, Linux Kernel <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...nel.org>, Peter Anvin <hpa@...or.com>, Peter Zijlstra <peterz@...radead.org> Subject: Re: Yet more softlockups. On Fri, 5 Jul 2013, Dave Jones wrote: > On Fri, Jul 05, 2013 at 05:15:07PM +0200, Thomas Gleixner wrote: > > On Fri, 5 Jul 2013, Dave Jones wrote: > > > > > BUG: soft lockup - CPU#3 stuck for 23s! [trinity-child1:14565] > > > perf samples too long (2519 > 2500), lowering kernel.perf_event_max_sample_rate to 50000 > > > INFO: NMI handler (perf_event_nmi_handler) took too long to run: 238147.002 msecs > > > > So we see a softlockup of 23 seconds and the perf_event_nmi_handler > > claims it did run 23.8 seconds. > > > > Are there more instances of NMI handler messages ? > > [ 2552.006181] perf samples too long (2511 > 2500), lowering kernel.perf_event_max_sample_rate to 50000 > [ 2552.008680] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 500392.002 msecs Yuck. Spending 50 seconds in NMI context surely explains a softlockup :) -- 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