linux-kernel - Re: timer: lockup in run_timer

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130709230316.GB13855@redhat.com>
Date:	Tue, 9 Jul 2013 19:03:16 -0400
From:	Dave Jones <davej@...hat.com>
To:	Sasha Levin <sasha.levin@...cle.com>
Cc:	Tejun Heo <tj@...nel.org>, tglx@...utronix.de,
	Peter Zijlstra <peterz@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>, trinity@...r.kernel.org
Subject: Re: timer: lockup in run_timer_softirq()

On Tue, Jul 09, 2013 at 06:49:29PM -0400, Sasha Levin wrote:
 > On 07/09/2013 06:47 PM, Dave Jones wrote:
 
 > >   > [ 2536.500130] INFO: NMI handler (arch_trigger_all_cpu_backtrace_handler) took too long to run:
 > >   > 697182.008 msecs
 > >
 > > I've been reporting these (and other traces) for a while https://lkml.org/lkml/2013/7/5/185 [1]
 > > on bare-metal.
 > 
 > Interesting. It's the first time I'm seeing these, but I haven't really changed
 > anything in my configuration.
 > 
 > Are you also seeing the "NMI handler took too long" messages?

Now that I look closer, one difference is you're seeing arch_trigger_all_cpu_backtrace_handler
in that message. I'm seeing them from perf_event_nmi_handler.

	Dave


--
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/