Bug 3717

Summary:	Only 2 out of 4 cpus active. Minor load on the other remaining cores.
Product:	Mageia	Reporter:	Jari S <lihamakaroonilaatikko>
Component:	RPM Packages	Assignee:	D Morgan <dmorganec>
Status:	RESOLVED FIXED	QA Contact:
Severity:	minor
Priority:	Normal	CC:	mageia, marja11, wilcal.int
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	systemd	CVE:
Status comment:
Bug Depends on:
Bug Blocks:	2120

Description Jari S 2011-12-12 11:21:26 CET

Description of problem:
After some update my i5 used only 2 out of 4 cores. Even "make -j5" did not push the other 2 cores, however there was some minor load on those cores.

Version-Release number of selected component (if applicable):


How reproducible:
Always.

Steps to Reproduce:
1. Add "CPUAffinity=1 2" to /etc/systemd/system.conf
2. Reboot
3. run e.g. "make -j5" in kernel source directory
4. use htop to see only cores 1 and 2 to be under load

The problem was that this was quite difficult to debug. I started to search for cgroups and cpuset since that was the obvious choice. No luck there, and the help and tools for debugging cgroups or cpuset problems are virtually non existent. So, the problem was easy to fix when I managed to find the source.

Fix: comment out the line saying "CPUAffinity=1 2" in /etc/systemd/system.conf

This report is just to leave a record, as requested in Mageia forum, on the behaviour if someone else runs into this kind of problem.

William Kenney 2011-12-12 14:40:08 CET

CC: (none) => wilcal.int

Manuel Hiebel 2011-12-12 22:27:43 CET

Blocks: (none) => 2120

Comment 1 Marja Van Waes 2012-01-30 17:14:56 CET

(In reply to comment #0)

> 
> This report is just to leave a record, as requested in Mageia forum, on the
> behaviour if someone else runs into this kind of problem.

Thanks, Jari :)

Assigning anyway, to make certain the maintainers of systemd will know about this issue

Assignee: bugsquad => dmorganec
CC: (none) => mageia, marja11

Comment 2 Colin Guthrie 2012-01-30 18:30:33 CET

Hmm, the man page suggests this is for the init process specifically. Can I ask what Desktop Environment you are using? Perhaps you are using e.g. KDE which does not properly detach it's processes from the init context. Perhaps GNOME behaves better in this case?

Comment 3 Jari S 2012-01-30 19:51:50 CET

I'm using KDE but the problem was that during some update (or user invention) the "CPUAffinity=1 2" was added to /etc/systemd/system.conf file. The reason for this bug is that someone asked to report it here for future reference.

Comment 4 D Morgan 2012-02-11 03:37:38 CET

what about this bug with systemd 40 ?

Comment 5 Jari S 2012-02-11 03:42:30 CET

This was not bug report on mailfunctioning system rather a note for anyone who has same kind of problem so it can be closed.

Comment 6 Marja Van Waes 2012-02-11 11:32:09 CET

(In reply to comment #5)
> This was not bug report on mailfunctioning system rather a note for anyone who
> has same kind of problem so it can be closed

Yes, we know, but please answer anyway.

If you still run cauldron: is the problem still there in fully updated cauldron?

If so, please give the output of:
rpm -qa | grep systemd

Keywords: (none) => NEEDINFO

Comment 7 Jari S 2012-02-11 11:33:45 CET

No, the problem is not there anymore.

Comment 8 Marja Van Waes 2012-02-11 11:34:47 CET

(In reply to comment #7)
> No, the problem is not there anymore.

Thx, so closing

Status: NEW => RESOLVED
Resolution: (none) => FIXED