From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Petr Mladek <pmladek@suse.com>, Nigel Croxon <ncroxon@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
dm-devel@redhat.com, linux-serial@vger.kernel.org
Subject: Re: Serial console is causing system lock-up
Date: Thu, 7 Mar 2019 10:56:52 +0900 [thread overview]
Message-ID: <20190307015652.GA4893@jagdpanzerIV> (raw)
In-Reply-To: <alpine.LRH.2.02.1903061031420.16905@file01.intranet.prod.int.rdu2.redhat.com>
On (03/06/19 11:07), Mikulas Patocka wrote:
> This bug only happens if we select large logbuffer (millions of
> characters). With smaller log buffer, there are messages "** X printk
> messages dropped", but there's no lockup.
>
> The kernel apparently puts 2 million characters into a console log buffer,
> then takes some lock and than tries to write all of them to a slow serial
> line.
Do you run a preemtible kernel?
-ss
next prev parent reply other threads:[~2019-03-07 1:56 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 14:27 Serial console is causing system lock-up Mikulas Patocka
2019-03-06 15:22 ` Petr Mladek
2019-03-06 16:07 ` Mikulas Patocka
2019-03-06 16:30 ` Theodore Y. Ts'o
2019-03-06 17:11 ` Mikulas Patocka
2019-03-06 22:19 ` Steven Rostedt
2019-03-06 22:43 ` John Ogness
2019-03-07 2:22 ` Sergey Senozhatsky
2019-03-07 8:17 ` John Ogness
2019-03-07 8:25 ` Sergey Senozhatsky
2019-03-07 8:34 ` John Ogness
2019-03-07 9:17 ` Sergey Senozhatsky
2019-03-07 10:37 ` John Ogness
2019-03-07 12:26 ` Sergey Senozhatsky
2019-03-07 12:54 ` Mikulas Patocka
2019-03-07 14:21 ` John Ogness
2019-03-07 15:35 ` Petr Mladek
2019-03-12 2:32 ` Sergey Senozhatsky
2019-03-12 8:17 ` John Ogness
2019-03-12 8:59 ` Sergey Senozhatsky
2019-03-12 10:05 ` Mikulas Patocka
2019-03-12 13:19 ` John Ogness
2019-03-12 13:44 ` Petr Mladek
2019-03-12 12:08 ` Petr Mladek
2019-03-12 15:19 ` John Ogness
2019-03-13 2:38 ` Sergey Senozhatsky
2019-03-13 8:43 ` John Ogness
2019-03-14 10:30 ` Sergey Senozhatsky
2019-03-07 14:08 ` John Stoffel
2019-03-07 14:26 ` Mikulas Patocka
2019-03-08 1:22 ` Sergey Senozhatsky
2019-03-08 1:39 ` Sergey Senozhatsky
2019-03-08 2:36 ` John Ogness
2019-03-07 15:16 ` Petr Mladek
2019-03-07 1:56 ` Sergey Senozhatsky [this message]
2019-03-07 13:12 ` Mikulas Patocka
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=20190307015652.GA4893@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=dm-devel@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-serial@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=ncroxon@redhat.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.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