Fixed
Created: Oct 25, 2018
Updated: Dec 16, 2018
Resolved Date: Oct 30, 2018
Previous ID: LIN9-7612
Found In Version: 10.17.41.12
Fix Version: 10.17.41.13
Severity: Critical
Applicable for: Wind River Linux LTS 17
Component/s: Userspace
When we uses command line with buad rate of 9600 to boot the target.
“Command line: BOOT_IMAGE=/vmlinuz root=LABEL=jrootp_P ro libata.force=noncq isolcpus=2-255 enforcing=0 pci=resource_alignment=00:1f.3;09:0d.0 rootdelay=5 unknown_nmi_panic=1 ro max_loop=255 console=ttyS0,9600 crashkernel=256M maxcpus=8”
With this, target hangs at getty services initialization during systemd.
WRL9 by default starts getty service in two serial consoles, below are the details from "layers/intel-x86/conf/machine/intel-x86.inc",
SERIAL_CONSOLES = "115200;ttyS0 115200;ttyUSB0"
Is there a way to override WR provided baud rate and use 9600 instead of 115200 for WRL9 with x86 based targets?
The problem was with the baud rate set to 115200 in /lib/systemd/system/serial-getty@.service. changing it to 9600 after comparing with WRL6 on the same target and the console is not hung now. It boots unto the Linux prompt.
NA, reproducible at customer env.
