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.
Please
- run kernel, systemd and plymouth with full debug logging (use appropriate parameters on the kernel command line),
- when the hang hits, exercise various Magic SysRq keys; for example:
'd' - Shows all locks that are held.
'l' - Shows a stack backtrace for all active CPUs.
't' - Will dump a list of current tasks and their information to
your console.
'w' - Dumps tasks that are in uninterruptable (blocked) state.
If the above doesn't enable the anaconda / systemd / plymouth developers to determine the cause, we can look in a vmcore, saved with "virsh dump --memory-only" (exact package versions will be necessary).
For example, I have no clue why netcat runs at all.
Closing it because it happened once during the development of RHEL7 and couldn't be repdroduced with a more recent image. If you ever reproduce it again with the GA, please reopen.