From: Conor Dooley <conor.dooley@microchip.com>
To: "Aithal, Srikanth" <sraithal@amd.com>
Cc: <linux-next@vger.kernel.org>
Subject: Re: next-20230803: boot hang with serial console enabled
Date: Thu, 3 Aug 2023 12:54:31 +0100 [thread overview]
Message-ID: <20230803-resisting-crayon-fb965e542698@wendy> (raw)
In-Reply-To: <e0dbf903-b122-4e81-0568-a27e1daa0fb4@amd.com>
[-- Attachment #1: Type: text/plain, Size: 1955 bytes --]
On Thu, Aug 03, 2023 at 04:43:30PM +0530, Aithal, Srikanth wrote:
> Hello all,
>
> linux-next build 20230802 onwards seeing host hang issue when booting with
> serial console enabled.
Should be fixed by
https://lore.kernel.org/all/20230803071034.25571-1-tony@atomide.com/
which Greg seems to have picked up.
>
>
>
> ===============
> Recreation steps
> ===============
> 1. Enable serial console by appending following parameters in grub:
>
> GRUB_CMDLINE_LINUX append with "console=ttyS0,115200n8 earlyprintk"
> GRUB_TERMINAL_OUTPUT="console serial"
> Update grub.
>
> 2. Then try to boot into next-20230802/next-20230803
>
>
> Below is the error seeing when the host kernel boots and then host hangs.
>
> Memory KASLR using RDRAND RDTSC...
> Poking KASLR using RDRAND RDTSC...
> [ 0.004421] __common_interrupt: 96.55 No irq handler for vector
> [ 2.552117] pstore: zlib_inflate() failed, ret = -5!
> [ 2.564770] pstore: zlib_inflate() failed, ret = -5!
> [ 2.577606] pstore: zlib_inflate() failed, ret = -5!
> [ 2.590765] pstore: zlib_inflate() failed, ret = -5!
> [ 2.606677] pstore: zlib_inflate() failed, ret = -5!
> [ 2.635828] pstore: zlib_inflate() failed, ret = -5!
> [ 2.650669] pstore: zlib_inflate() failed, ret = -5!
> [ 2.666176] pstore: zlib_inflate() failed, ret = -5!
> [ 2.682027] pstore: zlib_inflate() failed, ret = -5!
> [ 2.714415] pstore: zlib_inflate() failed, ret = -5!
> [ 2.737626] pstore: zlib_inflate() failed, ret = -5!
> [ 2.768368] pstore: zlib_inflate() failed, ret = -5!
> [ 2.802555] pstore: zlib_inflate() failed, ret = -5!
> [ 2.828769] pstore: zlib_inflate() failed, ret = -5!
> [ 2.849776] pstore: zlib_inflate() failed, ret = -5!
> [ 2.870973] pstore: zlib_inflate() failed, ret = -5!
> [ 2.893790] pstore: zlib_inflate() failed, ret = -5!
> [ 2.913867] pstore: zlib_inflate() failed, ret = -5!
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-08-03 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 11:13 next-20230803: boot hang with serial console enabled Aithal, Srikanth
2023-08-03 11:54 ` Conor Dooley [this message]
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=20230803-resisting-crayon-fb965e542698@wendy \
--to=conor.dooley@microchip.com \
--cc=linux-next@vger.kernel.org \
--cc=sraithal@amd.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;
as well as URLs for NNTP newsgroup(s).