From: Randy Dunlap <rdunlap@infradead.org>
To: "Kernel.org Bugbot" <bugbot@kernel.org>,
shuah@kernel.org, linux-kselftest@vger.kernel.org,
bugs@lists.linux.dev, skhan@linuxfoundation.org
Subject: Re: Kernel panic, CONFIG_FIPS_SIGNATURE_SELFTEST, missing dependency
Date: Mon, 3 Apr 2023 21:43:37 -0700 [thread overview]
Message-ID: <1c880cd5-b3f1-46b9-fc66-f7743e068c7a@infradead.org> (raw)
In-Reply-To: <1d7e238b-7e8f-9ce0-1ecb-68e2b80b6d92@infradead.org>
Hi again,
On 4/3/23 13:19, Randy Dunlap wrote:
>
>
> On 4/3/23 13:04, Kernel.org Bugbot wrote:
>> 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.
>>
I can reproduce this or at least something very similar to it, but it
doesn't matter if FIPS_SIGNATURE_SELFTEST is set or not.
>> 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.
>
> Please put your kernel .config file on the bugzilla entry.
I'll test with your .config file...
> What makes you think that this is related to FIPS_SIGNATURE_SELFTEST?
and still that question...
--
~Randy
next prev parent reply other threads:[~2023-04-04 4:43 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
2023-04-03 20:19 ` Randy Dunlap
2023-04-04 4:43 ` Randy Dunlap [this message]
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=1c880cd5-b3f1-46b9-fc66-f7743e068c7a@infradead.org \
--to=rdunlap@infradead.org \
--cc=bugbot@kernel.org \
--cc=bugs@lists.linux.dev \
--cc=linux-kselftest@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.