From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
Petr Mladek <pmladek@suse.com>,
John Ogness <john.ogness@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Wander Lairson Costa <wander@redhat.com>,
Willy Tarreau <w@1wt.eu>, David Laight <David.Laight@aculab.com>
Subject: Re: Strange output on the console
Date: Sat, 26 Feb 2022 02:20:57 +0000 [thread overview]
Message-ID: <YhmOifZcbbxVHPr9@google.com> (raw)
In-Reply-To: <20220225084256.071dcf82@gandalf.local.home>
On (22/02/25 08:42), Steven Rostedt wrote:
> On Fri, 25 Feb 2022 08:32:09 -0500
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > On Fri, 25 Feb 2022 14:07:00 +0900
> > Sergey Senozhatsky <senozhatsky@chromium.org> wrote:
> >
> > > > Steven, did you notice this recently?
> > > > May I perhaps suggest git bisect? (sorry)
> > >
> > > On the off chance - do you have this revert in your kernel?
> > >
> > > commit 6a7b9f002eca6788d346c16a6ff0c218b41f8d1d
> > > Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > Date: Wed Jan 26 14:33:58 2022 +0100
> > >
> > > Revert "tty: serial: Use fifo in 8250 console driver"
> > >
> > > This reverts commit 5021d709b31b8a14317998a33cbc78be0de9ab30.
> > >
> > > The patch is still a bit buggy, and this breaks some other hardware
> > > types. It needs to be resubmitted in a non-buggy way, and make sure the
> > > other hardware types also continue to work properly.
> >
> > My tree does not have this.
> >
> > I just applied it and I'm building now. I'll let you know if this fixes the
> > issue or not.
>
> Mystery solved. Thanks Sergey!
Awesome!
next prev parent reply other threads:[~2022-02-26 2:21 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 [this message]
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
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=YhmOifZcbbxVHPr9@google.com \
--to=senozhatsky@chromium.org \
--cc=David.Laight@aculab.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=w@1wt.eu \
--cc=wander@redhat.com \
/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