RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1271465 - 40-redhat.rules: unconditional onlining of new cpus breaks maxcpus=1 and causes problems for kdump
Summary: 40-redhat.rules: unconditional onlining of new cpus breaks maxcpus=1 and caus...
Keywords:
Status: CLOSED DUPLICATE of bug 1266322
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.2
Hardware: ppc64le
OS: Unspecified
unspecified
urgent
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 1270174
TreeView+ depends on / blocked
 
Reported: 2015-10-14 05:36 UTC by David Gibson
Modified: 2016-08-03 10:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-14 05:44:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description David Gibson 2015-10-14 05:36:03 UTC
Description of problem:

The /usr/lib/udev/rules.d/40-redhat.rules included in the normal systemd package includes a rule which brings any offline CPUs online.

SUBSYSTEM=="cpu", ACTION=="add", TEST=="online", ATTR{online}=="0", ENV{CPU_LEAVE_OFFLINE}!="yes", ATTR{online}="1"

It looks like this is intended so that newly hotplugged CPUs will be automatically activated.

However, if any CPUs are present, but offline at boot - such as when the maxcpus kernel command line option is used - then those CPUs will be brought online by udevd, which is not what a user would probably expect.

In particular, this means that kdump setups using maxcpus=1 end up with SMP enabled, which is a complexity we don't want for something supposed to be as simple and reliable as possible.


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

systemd-219-19.el7.ppc64le

How reproducible:

100%


Steps to Reproduce:
1.  Boot up system, with maxcpus=1 on the command line
2.  Once booted, check /proc/cpuinfo

Actual results:

All present CPUs are online.

Expected results:

Only one CPU is online.


Additional info:

  * For kdump on x86, this is addressed by using "nr_cpus=1" instead of "maxcpus=1", which prevents more cpus being added later.  Complexities with cpu threading modes means that nr_cpus=NN doesn't work properly on Power (bug 1222059 has some more information).

 * An alternative approach specific to kdump would be to alter construction of the kdump initramfs to exclude this rule.  However, I can't see a straightforward way of doing that without excluding 40-redhat.rules entirely, which might have other rules which are important during a kdump.

Comment 1 David Gibson 2015-10-14 05:44:01 UTC

*** This bug has been marked as a duplicate of bug 1266322 ***


Note You need to log in before you can comment on or make changes to this bug.