public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: David Laight <David.Laight@ACULAB.COM>
Cc: "'Steven Rostedt'" <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Petr Mladek <pmladek@suse.com>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	John Ogness <john.ogness@linutronix.de>
Subject: Re: Strange output on the console
Date: Fri, 25 Feb 2022 11:32:39 +0100	[thread overview]
Message-ID: <20220225103239.GA18720@1wt.eu> (raw)
In-Reply-To: <1dcb185901f04a5ea2476a449e371167@AcuMS.aculab.com>

On Fri, Feb 25, 2022 at 10:11:43AM +0000, David Laight wrote:
> From: Willy Tarreau
> > Sent: 25 February 2022 06:37
> > 
> > On Fri, Feb 25, 2022 at 06:12:35AM +0000, David Laight wrote:
> > > From: Steven Rostedt
> > > > Sent: 25 February 2022 04:01
> > > >
> > > > I've been noticing that my tests have been spitting out strange output on
> > > > the console. It would happen at boot up and then clear up. It looks like
> > > > something screwed up with the serial timing.
> > > >
> > > > Attached is a dmesg of one of my test runs as an example.
> > > >
> > > > I've noticed this on both 32 bit and 64 bit x86.
> > > >
> > > > I haven't had time to look deeper into this, but I figured I let you know
> > > > about it.
> > > >
> > > > And it always seems to happen right after:
> > > >
> > > >   Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> > > >
> > > > Maybe this is a serial issue and not a printk one? :-/
> > >
> > > Looks very much like the serial baud rate is being reset.
> > 
> > I don't think it's the baud rate, characters are still readable, it
> > looks more like a fifo being too short and causing lots of chars to
> > be dropped.
> 
> Just before it recovers there is this output:
>     ATaitoscic nitahi tuPiet mfba Ae:   aD nCt AH0 nP0
> That is probably 'fifo not enabled'.
> 
> But the earlier output doesn't have many different characters in it.
> Which is typical of the baud rate being wrong.

I don't think so, here's the beginning of the capture:

  Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
  0SI 15Nto
  LgtAsri[dnei00ieC nm
  i:0eom:Soce
  [ad000Ade s:ii SSLtbueludAis002h00 1)ASrPn
  Ars004h00 7ARrPn

All of these chars are within the printable set, so there's a probability
of ~37% per char, so even for a short string of 9 chars like the first
line, that's a 0.01% chance of it respecting the set. That's why for me
it definitely doesn't correspond to a baud rate issue. With wrong baud
rates you get lots of garbage in the full 8-bit range.

In addition there are even upper case at the beginning of the lines which
probably correspond to the ones that are printed on these lines.

Willy

  reply	other threads:[~2022-02-25 10:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25  4:00 Strange output on the console Steven Rostedt
2022-02-25  4:58 ` Sergey Senozhatsky
2022-02-25  5:07   ` Sergey Senozhatsky
2022-02-25 13:32     ` Steven Rostedt
2022-02-25 13:42       ` Steven Rostedt
2022-02-26  2:20         ` Sergey Senozhatsky
2022-02-26 11:49           ` Wander Costa
2022-02-28 16:05             ` Steven Rostedt
2022-03-02 18:49               ` Wander Costa
2022-02-25  6:12 ` David Laight
2022-02-25  6:36   ` Willy Tarreau
2022-02-25  9:37     ` John Ogness
2022-02-25  9:42       ` John Ogness
2022-02-25 10:11     ` David Laight
2022-02-25 10:32       ` Willy Tarreau [this message]
2022-02-25 11:11         ` David Laight
2022-02-25 12:25           ` Willy Tarreau
2022-02-25 13:03             ` David Laight
2022-02-25 13:17             ` Steven Rostedt
2022-02-25 13:25               ` Willy Tarreau
2022-02-25 13:28             ` Steven Rostedt
2022-02-25 13:40               ` Willy Tarreau
2022-02-25 13:44                 ` Steven Rostedt
2022-02-25 13:57                   ` Willy Tarreau
2022-02-25 13:53           ` Steven Rostedt

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=20220225103239.GA18720@1wt.eu \
    --to=w@1wt.eu \
    --cc=David.Laight@ACULAB.COM \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.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