From: John Ogness <john.ogness@linutronix.de>
To: Willy Tarreau <w@1wt.eu>, 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>
Subject: Re: Strange output on the console
Date: Fri, 25 Feb 2022 10:43:40 +0106 [thread overview]
Message-ID: <878rtzwal7.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20220225063637.GA18039@1wt.eu>
Hi Steven,
On 2022-02-25, Willy Tarreau <w@1wt.eu> wrote:
>> > 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? :-/
Your first message says you attached a dmesg. Does this mean you dumped
the kernel log directly into the attached file? ...or was that a screen
capture in the attached file?
It is an important distinction because if garbage is landing in the
kernel buffer, it is not related to serial at all.
John
next prev parent reply other threads:[~2022-02-25 9:37 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 [this message]
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
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=878rtzwal7.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=David.Laight@ACULAB.COM \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=w@1wt.eu \
/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