From: John Ogness <john.ogness@linutronix.de>
To: James Wang <jnwang@linux.alibaba.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel hang during reboot when cmdline include a non-exist console device
Date: Tue, 31 Aug 2021 09:40:45 +0206 [thread overview]
Message-ID: <87pmtudq3u.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <YS2fZ1sknFYKtJFi@google.com>
Added the reporter to the discussion...
On 2021-08-31, Sergey Senozhatsky <senozhatsky@chromium.org> wrote:
>> There's a bugzilla for this, but let's just move it to reguilar email,
>> unless some of you want to track it that way.
>>
>> The bugzilla entry says
>>
>> "When reboot， the capslock key of thinkpad x1 starts blinking"
>>
>> which sounds like there's an oops that just isn't showing, quite
>> possibly because the console has already been shut down.
There is no console registered.
>> I didn't test this out, and would sincerely hope that somebody else is
>> willing to follow up on it since I'm in the busiest part of the merge
>> window.
>
> [..]
>
>> > https://bugzilla.kernel.org/show_bug.cgi?id=214201
>
> I think normally wrong/empty console boot argument should not cause
> problems. We have a huge number of devices that use console="", for
> instance. But on some hardware this triggers panic(), very early on.
@James: Is it possible that you can set up a crash kernel to capture the
dump?
If a crash kernel is not possible, another option would be to enable
kgdb+kdb for a serial port. This would allow you to dump the kernel log.
> I have the same symptoms on my laptop, and so far haven't been able to
> figure out how to track it down, but I need to re-start my
> investigation.
A crash kernel or kgdb/kdb on a serial port is the easiest way to debug
this.
John Ogness
next prev parent reply other threads:[~2021-08-31 7:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 2:53 kernel hang during reboot when cmdline include a non-exist console device Linus Torvalds
2021-08-31 3:17 ` Sergey Senozhatsky
2021-08-31 7:34 ` John Ogness [this message]
2021-08-31 8:14 ` Petr Mladek
2021-08-31 8:31 ` James Wang
2021-08-31 8:47 ` Sergey Senozhatsky
2021-08-31 13:45 ` James Wang
2021-08-31 14:33 ` Petr Mladek
2021-08-31 14:38 ` James Wang
2021-08-31 14:52 ` Petr Mladek
2021-09-01 1:52 ` James Wang
2021-09-01 11:48 ` Petr Mladek
2021-09-01 13:53 ` James Wang
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=87pmtudq3u.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=jnwang@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).