During the release cycle of v3.17 I've seen sometimes a broken serial console
output
on the parisc platform. Interestingly all kernel messages printed by the kernel
via printk() show
up correctly, but output from userspace (e.g. by the init process during boot)
show
up as random bytes.
Since the printk() output is correct the serial port itself and setup is
probably correct.
Is parisc the only arch which has this problem, or are other architectures
affected as well?
Maybe someone has an idea what could be wrong?
I did not try to bisect it yet.
Thanks,
Helge
Here is a sample output during bootup:
<lots of standard kernel printk output>...
usb 1-2: Manufacturer: SILITEK
rs
og
]f"
s l
random: nonblocking pool is initialized
net eth0: Setting full-duplex based on MII#1 link partner capability of 45e1
tpdsystemd-udevd[744]: starting version 215
.
eg..
vp..
..Adding 1350652k swap on /dev/sdb6. Priority:-1 extents:1
across:1350652k
.
EXT4-fs (sdb5): re-mounted. Opts: (null)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
