linux-kernel - Re: 4.2.2: NR_CPUS effectively being 1 bug

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: <20151002140033.ef62cd83936263311eb210d8@linux-foundation.org>
Date:	Fri, 2 Oct 2015 14:00:33 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Alexey Dobriyan <adobriyan@...il.com>
Cc:	linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: 4.2.2: NR_CPUS effectively being 1 bug

On Fri, 2 Oct 2015 23:46:59 +0300 Alexey Dobriyan <adobriyan@...il.com> wrote:

> FYI, I've upgraded from 4.1.7 to 4.2.1 (and retested with 4.2.2) and
> everything is scheduled on 1 CPU out of 4 (i5 760).
> 
> 	$ sudo cat /proc/1/status | grep cpu -i
> 	Cpus_allowed:   1
> 	Cpus_allowed_list:      0
> 
> Every process inherits this tiny cpumask.

Sell the other CPUs on ebay?

I haven't seen such a report before - maybe it rings a bell with Peter
& Ingo?

It should be pretty easy to debug.  I'd guess that the problem is in
the area of x86 SMP bringup and there might even be a nasty message in
the dmesg explaining what went wrong?

> #
> # Automatically generated file; DO NOT EDIT.
> # Linux/x86 4.2.2 Kernel Configuration
> #
> CONFIG_64BIT=y
> ...
>
--
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/