From: "Kernel.org Bugbot" <bugbot@kernel.org>
To: shuah@kernel.org, linux-kselftest@vger.kernel.org,
bugs@lists.linux.dev, rdunlap@infradead.org,
skhan@linuxfoundation.org
Subject: Re: Kernel panic, CONFIG_FIPS_SIGNATURE_SELFTEST, missing dependency
Date: Mon, 3 Apr 2023 20:04:19 +0000 (UTC) [thread overview]
Message-ID: <20230403-b217293c2-4b94a5e6478a@bugzilla.kernel.org> (raw)
In-Reply-To: <20230403-b217293c0-1e5391e4b7f5@bugzilla.kernel.org>
o6irnndpcv7 writes via Kernel.org Bugzilla:
Hi Randy!
(In reply to Bugbot from comment #1)
> Randy Dunlap <rdunlap@infradead.org> writes:
>
> Please tell us what the kernel panic message is.
>
There is no message. I'm sorry.
I just get a black screen.
I'm using EFI to boot my machine. And I can get some output if I enable 'earlycon=efifb' via CMDLINE.
The output stops at:
Console: colour dummy device 80x25
printk: console [tty0] enabled
printk: bootconsole [efifb0] disabled
At this point the machine freezes. No error message.
And when I set:
CONFIG_PANIC_ON_OOPS=y
CONFIG_PANIC_ON_OOPS_VALUE=1
CONFIG_PANIC_TIMEOUT=-1
That gives me a reboot loop.
>
> Have you tested this on a mainline kernel, without gentoo patches?
>
> Does gentoo add any patches in this area?
>
Unfortunately I don't know if Gentoo is adding any patches that may affect this.
But I can confirm that the problem persists while using vanilla-sources for kernel 6.2.9.
Thanks,
sephora
>
> Thanks.
View: https://bugzilla.kernel.org/show_bug.cgi?id=217293#c2
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (peebz 0.1)
next prev parent reply other threads:[~2023-04-03 20:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 14:29 Kernel panic, CONFIG_FIPS_SIGNATURE_SELFTEST, missing dependency Kernel.org Bugbot
2023-04-03 16:33 ` Randy Dunlap
2023-04-03 20:04 ` Kernel.org Bugbot [this message]
2023-04-03 20:19 ` Randy Dunlap
2023-04-04 4:43 ` Randy Dunlap
2023-04-04 6:06 ` Kernel.org Bugbot
2023-04-04 6:17 ` Kernel.org Bugbot
2023-04-05 3:15 ` Randy Dunlap
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=20230403-b217293c2-4b94a5e6478a@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=bugs@lists.linux.dev \
--cc=linux-kselftest@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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).