Bug 720027

Summary:	Upstart chooses wrong primary console
Product:	Red Hat Enterprise Linux 6	Reporter:	Chris Adams <linux>
Component:	plymouth	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED DUPLICATE	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	jkoten, prc
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	747178 (view as bug list)		Environment:
Last Closed:	2011-10-26 18:38:02 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	747178

Description Chris Adams 2011-07-08 19:02:53 UTC

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 2 RHEL 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.

Comment 3 Chris Adams 2011-07-11 15:42:58 UTC

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?

Comment 4 Petr Lautrbach 2011-07-12 11:36:18 UTC

This is most likely plymouth issue. Does it help if you add rd_NO_PLYMOUTH to kernel command line?

Comment 5 Chris Adams 2011-07-12 13:05:13 UTC

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 6 RHEL 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.

Comment 7 Jiri Koten 2011-10-26 18:38:02 UTC

This is probably dupe of bug 719569.

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