linux-kernel - Re: nohz fail (was: perf related boot hang.)

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: <CAFTL4hxJ2roTB3tZBmXU3HRetgFSUT0LNVWfX-Y2hbpyXSo2pg@mail.gmail.com>
Date:	Thu, 21 Aug 2014 16:56:06 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Catalin Iacob <iacobcatalin@...il.com>
Cc:	Dave Jones <davej@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: nohz fail (was: perf related boot hang.)

2014-08-20 22:31 GMT+02:00 Catalin Iacob <iacobcatalin@...il.com>:
> I've also just hit what seems to be the same panic in 3.17-rc1 (ignore the 1
> local patch, it's an unrelated change in a comment) twice in less than 1
> hour. Hitting this twice in a short amount of time seems to be proof that the
> 3.17 merge window made it trigger more often. Both times I was running a grep
> over a Firefox build tree which was taking a long time.
>
> The stacktraces are slightly different but both have the "cancel timer from a
> timer, followed by nmi" pattern. Pictures of the 2 stacktraces:
> https://drive.google.com/file/d/0B_fRjDygGZSNY0RIc2dyYTExTjg/edit?usp=sharing
> https://drive.google.com/file/d/0B_fRjDygGZSNS1pSWFkteURrOTQ/edit?usp=sharing

Hi Catalin, Dave,

Can you please test the series I just posted: "[RFC PATCH 0/9] nohz:
Nohz full kick fixes"?
It should fix the issues.

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