From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
rcu@vger.kernel.org
Subject: Re: [rt-devel:linux-6.6.y-rt] [printk] 78f4b59c6f: BUG:kernel_failed_in_early-boot_stage,last_printk:early_console_in_setup_code
Date: Mon, 20 Nov 2023 15:30:39 +0100 [thread overview]
Message-ID: <20231120143039.HvK0o_uj@linutronix.de> (raw)
In-Reply-To: <202311161555.3ee16fc9-oliver.sang@intel.com>
On 2023-11-16 15:43:38 [+0800], kernel test robot wrote:
> Hello,
Hi,
> kernel test robot noticed "BUG:kernel_failed_in_early-boot_stage,last_printk:early_console_in_setup_code" on:
>
> commit: 78f4b59c6faa7afe24b973210151d4a82b5669eb ("printk: Update the printk series.")
> https://git.kernel.org/cgit/linux/kernel/git/rt/linux-rt-devel.git linux-6.6.y-rt
as in the previous report, it is the 32bit printk issue. Will be fixed
in next update.
Thank you.
Sebastian
prev parent reply other threads:[~2023-11-20 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 7:43 [rt-devel:linux-6.6.y-rt] [printk] 78f4b59c6f: BUG:kernel_failed_in_early-boot_stage,last_printk:early_console_in_setup_code kernel test robot
2023-11-20 14:30 ` Sebastian Andrzej Siewior [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=20231120143039.HvK0o_uj@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=rcu@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).