From: Peter Hurley <peter@hurleysoftware.com>
To: Helge Deller <deller@gmx.de>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: serial console broken in v3.17-rc6 ?
Date: Tue, 23 Sep 2014 17:08:54 -0400 [thread overview]
Message-ID: <5421E166.7060206@hurleysoftware.com> (raw)
In-Reply-To: <5421D3E3.6080805@gmx.de>
Hi Helge,
On 09/23/2014 04:11 PM, Helge Deller wrote:
> 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)
Thanks for the bug report.
1. What serial driver is this?
2. Regression since when?
3. Full dmesg please
4. Output of setserial -a [serial device]
5. Output of stty -a [serial device]
Regards,
Peter Hurley
next prev parent reply other threads:[~2014-09-23 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 20:11 serial console broken in v3.17-rc6 ? Helge Deller
2014-09-23 21:08 ` Peter Hurley [this message]
2014-09-24 18:48 ` Helge Deller
2014-09-30 19:59 ` Peter Hurley
2014-10-01 14:46 ` Aw: " Helge Deller
2014-10-01 15:35 ` Peter Hurley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5421E166.7060206@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=deller@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).