configure getty properly on serial consoles using hardware flow control
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
finish-install (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
High
|
Unassigned |
Bug Description
[Impact]
Hardware that uses hardware flow control for the serial console will not run a getty in the correct mode, possibly causing loss of functionality. Canonical would like to enable some such hardware in an upcoming point release.
[Test Case]
Use d-i to install a system booted with hardware flow control enabled (e.g. console=
But, I did test this by using a trusty installer w/ the upstream change on an HP Moonshot system, booted with both "console=
getting configured with the correct parameters in each case.
[Regression Potential]
Assuming the upstream fix is correct, the regression potential would be limited to hardware that reports itself as using hardware flow control, but does not actually work with hardware flow control. Discussion on the upstream list suggested this wasn't an issue: https:/
If the getty hardware flow control is broken, it might leave a system more unusable than it would be if incorrectly configured. The testing I performed (described above) found no such issues.
Of course, if the upstream fix is buggy, it could end up breaking the serial console configuration.
Related branches
Changed in finish-install (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in finish-install (Ubuntu Trusty): | |
status: | New → In Progress |
importance: | Undecided → High |
milestone: | none → trusty-updates |
Upstream fix: anonscm. debian. org/gitweb/ ?p=d-i/ finish- install. git;a=commitdif f;h=af8ac0c8110 0971cd2661f871e 96c88b23aa402d
http://