linux-kernel - Only 1 cpu scheduled in 4.2.0

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-next>] [day] [month] [year] [list]

Message-ID: <CAFrnU37Qb4NHNhtEt41QC9pOCo7u59CCRLFoOt=JZAU2a+=t3w@mail.gmail.com>
Date:	Wed, 2 Sep 2015 11:38:48 +0200
From:	Martin van Es <mrvanes@...il.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Only 1 cpu scheduled in 4.2.0

Hi,

I recently compiled 4.2.0 based on my previous 4.1.6 config (make oldconfig).
On 4.1.6 all cores are equally scheduled.

This new 4.2.0 kernel however only schedules cpu0 on my 4 cpu i7-3537U
(which is actually 2 cores x 2HT, as far as I understand the specs).
CPU1 is scheduled for 0.5% now and then, so it's not completely 0.

I tried (re)enabling NUMA support, since that's adviced for 64bit/i7
cpu's according to the help text, but that didn't change anything.

Did I miss a new option for SMP scheduling in 4.2.0?

Best regards,
Martin
--
If 'but' was any useful, it would be a logic operator
--
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/