Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionLuiz Capitulino
2016-07-14 20:42:51 UTC
Description of problem:
Starting with kernel-rt-3.10.0-439.rt56.327.el7, we now have CONFIG_RCU_NOCB_CPU_NONE=y (instead of CONFIG_RCU_NOCB_CPU_ALL=y). This means that we're required to specify no-CBs CPUs with rcu_nocbs=. Otherwise we'll run into spikes.
The [bootloader] section in both guest and host tuned.conf must have the following option:
rcu_nocbs=${isolated_cores}
Version-Release number of selected component (if applicable): tuned-2.5.1-7.el7.noarch
Two additional notes:
- I'm not sure if the realtime profile should get this option too (probably yes)
- There seems to be a bug with CONFIG_RCU_NOCB_CPU_NONE=y where processes get stuck in D state during system boot. This issue is workarounded by rcu_nocbs=
Comment 2Jaroslav Škarvada
2016-07-15 14:39:35 UTC
I guess this is dupe of bug 1334479. If not, please reopen.
*** This bug has been marked as a duplicate of bug 1334479 ***
Description of problem: Starting with kernel-rt-3.10.0-439.rt56.327.el7, we now have CONFIG_RCU_NOCB_CPU_NONE=y (instead of CONFIG_RCU_NOCB_CPU_ALL=y). This means that we're required to specify no-CBs CPUs with rcu_nocbs=. Otherwise we'll run into spikes. The [bootloader] section in both guest and host tuned.conf must have the following option: rcu_nocbs=${isolated_cores} Version-Release number of selected component (if applicable): tuned-2.5.1-7.el7.noarch