From: Jiri Slaby <jslaby@suse.cz>
To: Shawn Lin <shawn.lin@rock-chips.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>
Subject: Re: [regression] tty console panic for 4.13-rcx
Date: Mon, 7 Aug 2017 08:35:26 +0200 [thread overview]
Message-ID: <7446f7ba-d725-0ad4-2df4-65845494e1a3@suse.cz> (raw)
In-Reply-To: <ad269c73-22c1-464e-d34a-25366d895110@rock-chips.com>
On 08/07/2017, 06:00 AM, Shawn Lin wrote:
> Hi,
>
> I saw the log at the bottom and bisect the issue to the commits of
>
> 065ea0a7afd64d6c ("tty: improve tty_insert_flip_char() slow path")
> 979990c628481461 ("tty: improve tty_insert_flip_char() fast path")
>
> I nearly could 100% reproduce this. Any thought?
Hi,
could you test with:
https://lkml.org/lkml/2017/8/2/326
?
thanks,
--
js
suse labs
next prev parent reply other threads:[~2017-08-07 6:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 4:00 Shawn Lin
2017-08-07 6:35 ` Jiri Slaby [this message]
2017-08-07 7:58 ` Shawn Lin
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=7446f7ba-d725-0ad4-2df4-65845494e1a3@suse.cz \
--to=jslaby@suse.cz \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.lin@rock-chips.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
all inboxes | Powered by JetHome®