From: Andrew Morton <akpm@linux-foundation.org>
To: Xu Qiang <xuqiang36@huawei.com>
Cc: <keescook@chromium.org>, <mingo@kernel.org>,
<peterz@infradead.org>, <mcgrof@kernel.org>, <huyue2@yulong.com>,
<yangtiezhu@loongson.cn>, <will@kernel.org>, <aquini@redhat.com>,
<gpiccoli@canonical.com>, <aik@ozlabs.ru>,
<linux-kernel@vger.kernel.org>, <rui.xiang@huawei.com>
Subject: Re: [PATCH -next] panic: complete the flush of the hard deadlock log messages to the serial port
Date: Mon, 23 Nov 2020 11:52:35 -0800 [thread overview]
Message-ID: <20201123115235.74aab2449ac5cf27f10a4cfd@linux-foundation.org> (raw)
In-Reply-To: <20201123131359.34600-1-xuqiang36@huawei.com>
On Mon, 23 Nov 2020 13:13:59 +0000 Xu Qiang <xuqiang36@huawei.com> wrote:
> when hardlockup_all_cpu_backtrace is on, and there are
> a large number of cores in the system, it takes
> a long time to output the hard deadlock logs of all cores
> to the serial port. When the console_flush_on_panic function
> in panic is executed, console_locked is still held.
> As a result, garbled characters are displayed in the serial port log.
>
> To solve this problem, wait for a maximum of 10s for the serial port
> to be released before console_flush_on_panic.
Wouldn't it be better to wait until all the printing of all those
backtraces has completed?
next prev parent reply other threads:[~2020-11-23 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 13:13 Xu Qiang
2020-11-23 19:52 ` Andrew Morton [this message]
2020-11-24 3:22 ` xuqiang (M)
2020-12-08 8:34 ` xuqiang (M)
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=20201123115235.74aab2449ac5cf27f10a4cfd@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aik@ozlabs.ru \
--cc=aquini@redhat.com \
--cc=gpiccoli@canonical.com \
--cc=huyue2@yulong.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rui.xiang@huawei.com \
--cc=will@kernel.org \
--cc=xuqiang36@huawei.com \
--cc=yangtiezhu@loongson.cn \
/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®