mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "xuqiang (M)" <xuqiang36@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
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: Tue, 24 Nov 2020 11:22:11 +0800	[thread overview]
Message-ID: <080e8065-c696-eeec-3390-13b4458f67b6@huawei.com> (raw)
In-Reply-To: <20201123115235.74aab2449ac5cf27f10a4cfd@linux-foundation.org>


在 2020/11/24 3:52, Andrew Morton 写道:
> 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?
>
>
> .

The fear that there may be some unexpected abnormal situation,

resulting in the serial port has been occupied without release.


Thanks

         Xu.


  reply	other threads:[~2020-11-24  3:22 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
2020-11-24  3:22   ` xuqiang (M) [this message]
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=080e8065-c696-eeec-3390-13b4458f67b6@huawei.com \
    --to=xuqiang36@huawei.com \
    --cc=aik@ozlabs.ru \
    --cc=akpm@linux-foundation.org \
    --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=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®