linux-kernel - Re: Yet more softlockups.

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: <alpine.DEB.2.02.1307101137160.2022@pianoman.cluster.toy>
Date:	Wed, 10 Jul 2013 11:39:50 -0400 (EDT)
From:	Vince Weaver <vince@...ter.net>
To:	Dave Jones <davej@...hat.com>
cc:	Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Peter Anvin <hpa@...or.com>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: Yet more softlockups.

On Wed, 10 Jul 2013, Dave Jones wrote:

> Something is really fucked up in the kernel side of perf.
> I get this right after booting..
> 
> [  114.516619] perf samples too long (4262 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
> 
> That's before I even get a chance to log in, so I'm pretty sure perf isn't even being run.
> 
> And this is just booting up my desktop, not fuzzing.

This is probably related to the problem described in the thread
   perf: fix interrupt handler timing harness
   http://comments.gmane.org/gmane.linux.kernel/1520775
which in theory has a fix.  Not sure why it'd trigger during boot.
NMI watchdog?

Vince

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