"Filing" this bug report on linaro-dev for now, so I don't forget it. I can't figure out how to file a but against linaro-overlay on launchpad. (Any suggestions?)
Cheers ---Dave
--
linaro-overlay: auto-serial-console clobbers bootup serial port configuration
auto-serial-console makes incorrect assumptions about the contents of the kernel console= command-line paramter (compare auto-serial-console with linux/Documentation/kernel-parameters.txt)
This means that booting a kernel with a console= argument which has no explicit speed or which has other unusual settings, auto-serial-console may mess up the serial port when it calls getty, especially if the initial serial port speed is not 115200 baud. The kernel itself does not require all serial port parameters to be specified on the command-line: in that case, the setup done by the bootloader is simply used as-is.
auto-serial-console does not determine the actual port speed if the kernel command-line has no explicit speed; instead it just defaults to 115200.
The simplest fix is simply not to set the relevant serial port communication parameters when initialising the terminal. This should be a more robust solution, and would allow auto-serial-console to be simpified. Unfortunately, util-linux's agetty (the default getty for Ubuntu and linaro filesystems) always sets these parameters explicitly. This is an arguable misfeature and could probably be solved with a simple patch. Alternatively, it would be worth investigating whether one of the other existing getty variants will already do the desired thing.
An alternative workaround could be to use stty to read the current parameters of the serial port, and use this information to pass the appropriate arguments to getty. This may be fragile though, since stty does not produce reliably parseable output; the only options are to produce output which is human-readable, and output which is only readable by stty itself.
This bug does not affect the linaro releases directly, but can affect the use of Linaro filesystems with unsupported boards or custom kernel setups, particularly where the board's boot-time serial port speed is not 115200 such as on vexpress.
Hi,
On Fri, Oct 14, 2011 at 7:52 PM, Dave Martin dave.martin@linaro.org wrote:
"Filing" this bug report on linaro-dev for now, so I don't forget it. I can't figure out how to file a but against linaro-overlay on launchpad. (Any suggestions?)
the overlay ppa is used for our ubuntu LEB effort. Bugs should go here: https://launchpad.net/linaro-ubuntu/+filebug
On Mon, Oct 17, 2011 at 1:47 PM, Alexander Sack asac@linaro.org wrote:
Hi,
On Fri, Oct 14, 2011 at 7:52 PM, Dave Martin dave.martin@linaro.orgwrote:
"Filing" this bug report on linaro-dev for now, so I don't forget it. I can't figure out how to file a but against linaro-overlay on launchpad. (Any suggestions?)
the overlay ppa is used for our ubuntu LEB effort. Bugs should go here: https://launchpad.net/linaro-ubuntu/+filebug
... also poked the overlay ppa description/banner a bit to give better guidance. Check: https://launchpad.net/~linaro-maintainers/+archive/overlay
On Mon, Oct 17, 2011 at 01:47:13PM +0200, Alexander Sack wrote:
Hi,
On Fri, Oct 14, 2011 at 7:52 PM, Dave Martin dave.martin@linaro.org wrote:
"Filing" this bug report on linaro-dev for now, so I don't forget it. I can't figure out how to file a but against linaro-overlay on launchpad. (Any suggestions?)
the overlay ppa is used for our ubuntu LEB effort. Bugs should go here: https://launchpad.net/linaro-ubuntu/+filebug
Does ubuntu-bug know about this (or should we have out own linaro-bug script?) I worry that we mat not get good bug tracking if it's too hard to identify where to file a bug.
Cheers ---Dave
On Tue, Oct 25, 2011 at 12:07 PM, Dave Martin dave.martin@linaro.orgwrote:
On Mon, Oct 17, 2011 at 01:47:13PM +0200, Alexander Sack wrote:
Hi,
On Fri, Oct 14, 2011 at 7:52 PM, Dave Martin dave.martin@linaro.org
wrote:
"Filing" this bug report on linaro-dev for now, so I don't forget it. I can't figure out how to file a but against linaro-overlay on
launchpad.
(Any suggestions?)
the overlay ppa is used for our ubuntu LEB effort. Bugs should go here: https://launchpad.net/linaro-ubuntu/+filebug
Does ubuntu-bug know about this (or should we have out own linaro-bug script?) I worry that we mat not get good bug tracking if it's too hard to identify where to file a bug.
As far as I understand we announce where to file bugs for ubuntu and android in the release announce.
Linaroizing ubuntu-bug sounds like an interesting idea. For our cases we probably want something more suitable for cross-use-cases (ubuntu-bug needs to be run on the target). Anyone wants to pick this up, add a blueprint to backlog and own discussion at connect?