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.
When adding a serial console, the rule has always been that the last console listed on the kernel command line is "primary", so the normal entry is something like "console=tty0 console=ttyS0,115200". Per the comment in /etc/init/serial.conf, a serial console getty will only be started for the last console (if it is serial).
However, it appears that upstart sends init messages only to the _first_ console listed, not the last. If you use the above console config, the init messages go to the VGA TTY. If you reverse the console entries, the init messages go to the serial console (but now you don't get a getty for login).
One or the other of these two should be changed, and since the historical behavior matches the comment in /etc/init/serial.conf, upstart should be changed.
This is also a bug in Fedora 14.
Comment 2RHEL Program Management
2011-07-08 19:38:31 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
This is actually a pretty serious regression in serial console functionality, which is pretty important for servers. Not getting init messages to the designated console is just broken. What if there is a problem starting a service? How do you find out?
You are correct, it does appear to be plymouth related. When I add rd_NO_PLYMOUTH, "console=tty0 console=ttyS0,115200" works as before (kernel messages go both places, init messages to serial, and a getty is started on serial as well).
Comment 6RHEL Program Management
2011-07-12 13:38:29 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.