linux-kernel - Re: [ANNOUNCE] 3.6.6-rt17

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]

Date:	Fri, 21 Dec 2012 15:23:57 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Mike Galbraith <bitbucket@...ine.de>
cc:	LKML <linux-kernel@...r.kernel.org>,
	linux-rt-users <linux-rt-users@...r.kernel.org>
Subject: Re: [ANNOUNCE] 3.6.6-rt17

On Fri, 21 Dec 2012, Mike Galbraith wrote:
> On Mon, 2012-11-12 at 22:28 +0100, Thomas Gleixner wrote: 
> > Dear RT Folks,
> > 
> > I'm pleased to announce the 3.6.6-rt17 release. 3.6.6-rt16 is just a
> > not announced update release to 3.6.6.
> > 
> > Changes since 3.6.6-rt16:
> > 
> >    * Finally make the NOHZ softirq pending detection work with the new
> >      softirq scheme.
> 
> Well, almost.  They gripe when rebooting, but I haven't seen one other
> than that.  This is 3.6.11-rt23 on a 64 core DL980 I set up to run some
> latency tests on.

Yeah. It's not fixed completely. I know what it needs but thats major
surgery.
 
> [  318.692463] kvm: exiting hardware virtualization
> [  319.568482] Disabling non-boot CPUs ...
> [  319.647819] NOHZ: local_softirq_pending 80
> [  319.876148] NOHZ: local_softirq_pending 202
> [  319.876172] NOHZ: local_softirq_pending 202
> [  319.988912] NOHZ: local_softirq_pending 282
> [  320.097066] NOHZ: local_softirq_pending 202
> [  320.321428] NOHZ: local_softirq_pending 80
> [  320.662601] NOHZ: local_softirq_pending 202
> [  320.662637] NOHZ: local_softirq_pending 202
> [  323.162636] NOHZ: local_softirq_pending 202
> [  323.162649] NOHZ: local_softirq_pending 202
> [  325.217675] Restarting system.
> 
> Don't suppose you know why LAZY_PREEMPT would make 3.0-rt explode if you
> turn on wakeup_rt tracer do you?

No.
 
> I backported that and your softirq changes to 3.0.  New softirq handling
> scheme work spiffy there, LAZY_PREEMPT works fine too.. until you turn
> tracing on, then it corrupts memory, and makes mushroom cloud.

I guess you are just trying to make up for the canceled apocalypse :)
--
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/