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.
Created attachment 488516[details]
patch to disable isolcpus with isolated cpu set covers all online cpus
Please try this patch. Its for an upstream kernel, but it should massage into rhel6 just fine. It will, instead of bughalting when the init task is migrated, will cause the non-isocpus set to be expanded, and a warning printed instead.
You're contradicting yourself. Your list says that every kernel you tried failed with the stack trace in comment 0.
At the same time that you said that you can't make this problem occur on anything other than the 5.3 GOLD tree. Which is it?
Also, why are you testing with RHEL5? This problem was reported against RHEL6. Not that it shouldn't fix the problem in RHEL5 as well (assuming its there), but regardless. Is the bz version incorrect?
Created attachment 488516 [details] patch to disable isolcpus with isolated cpu set covers all online cpus Please try this patch. Its for an upstream kernel, but it should massage into rhel6 just fine. It will, instead of bughalting when the init task is migrated, will cause the non-isocpus set to be expanded, and a warning printed instead.