From: Willy Tarreau <w@1wt.eu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: David Laight <David.Laight@aculab.com>,
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 14:25:41 +0100 [thread overview]
Message-ID: <20220225132541.GD18720@1wt.eu> (raw)
In-Reply-To: <20220225081719.7710f62e@gandalf.local.home>
On Fri, Feb 25, 2022 at 08:17:19AM -0500, Steven Rostedt wrote:
> On Fri, 25 Feb 2022 13:25:46 +0100
> Willy Tarreau <w@1wt.eu> wrote:
>
> > > TnsTesOT s T sKTesOT sKTvsOTtsTtsKTtsT sKTesTesKT sKTesOT siT stTnsaTvsaTesKTnsOT s
> > > TesKTnsT s TvsKTeslT sOTesT sKTtseTnseTvs_Tts_T sOTes TnsOT s T spTespTesdTesdTeseTtseTeseTt_rTe_rTv_oTes:T s:Tes:TnfwOTvfrKT fwT frTefpuTefpKTefpTvf:TnsOTvsOTnsoTvs Tvs TvsTtssTnsT sKTesTnsTvsTtsoTesmTnsgTesiTeslTtsTvsKTnsTvsOTtsT s_Tnsu
> > >
> > > which really doesn't have enough different characters in it to be a fifo problem.
> > > That looks like a UART struggling to find valid start and stop bits
> > > on a continuous data stream that doesn't match the baud rate.
> > >
> > > It may also be that whatever 'terminal' is being used is masking off the 0x80 bit.
> >
> > That could be one option I thought about but still, that sounds quite
> > suspicious. You don't even get any #!:$/ etc. Or maybe the UART is
> > configured in 6-bit mode (most 16550 support 5-8 bits), and maybe even
> > the stop bit and/or parity participates.
>
> One thing that's not easy to demonstrate here (I could try to video it), is
> that this output is the final result. It shows a bunch of other characters
> as it is displayed but then the cursor goes backwards and writes over it.
>
> But the characters that are deleted still do not make sense. When watching
> it, it reminds me of the Matrix characters, but running horizontal and not
> vertical.
Ah, so 6-bit might definitely make sense.
> > ... and Steven having fun reading our proposals after having made this
> > up entirely in preparation of the next April's fool :-)
>
>
> I was thinking the same thing, but this output being the joke. Someone
> planning on slipping in Matrix characters for printk?
;-)
Willy
next prev parent reply other threads:[~2022-02-25 13:26 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
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 [this message]
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=20220225132541.GD18720@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