From: Jan Kiszka <jan.kiszka@siemens.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Aaron Kling <webgeek1234@gmail.com>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] efistub: Lower default log level
Date: Sun, 24 Aug 2025 08:47:42 +0200 [thread overview]
Message-ID: <09cb03e4-21f3-418c-98f2-66004cc3080f@siemens.com> (raw)
In-Reply-To: <CAMj1kXG=zG8j+cr0gNMpkKRvdekqMR-EiEkMHiFgRvbaWy9aKg@mail.gmail.com>
On 24.08.25 02:31, Ard Biesheuvel wrote:
> On Sat, 16 Aug 2025 at 16:52, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>>
>> On 15.07.25 03:35, Ard Biesheuvel wrote:
>>> On Tue, 8 Jul 2025 at 17:31, Aaron Kling <webgeek1234@gmail.com> wrote:
>>>>
>>>> On Tue, Jul 8, 2025 at 2:30 AM Aaron Kling via B4 Relay
>>>> <devnull+webgeek1234.gmail.com@kernel.org> wrote:
>>>>>
>>>>> From: Aaron Kling <webgeek1234@gmail.com>
>>>>>
>>>>> Some uefi implementations will write the efistub logs to the display
>>>>> over a splash image. This is not desirable for debug and info logs, so
>>>>> lower the default efi log level to exclude them.
>>>>>
>>>>> Suggested-by: Ard Biesheuvel <ardb@kernel.org>
>>>>> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
>>>>> ---
>>>>> drivers/firmware/efi/libstub/printk.c | 4 ++--
>>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>>
>>>>> diff --git a/drivers/firmware/efi/libstub/printk.c b/drivers/firmware/efi/libstub/printk.c
>>>>> index 3a67a2cea7bdf1aa215d48dbf9ece4ceec6e4c28..bc599212c05dd746a9c54abbbe61a4bf70f1a8c4 100644
>>>>> --- a/drivers/firmware/efi/libstub/printk.c
>>>>> +++ b/drivers/firmware/efi/libstub/printk.c
>>>>> @@ -5,13 +5,13 @@
>>>>> #include <linux/ctype.h>
>>>>> #include <linux/efi.h>
>>>>> #include <linux/kernel.h>
>>>>> -#include <linux/printk.h> /* For CONSOLE_LOGLEVEL_* */
>>>>> +#include <linux/kern_levels.h>
>>>>> #include <asm/efi.h>
>>>>> #include <asm/setup.h>
>>>>>
>>>>> #include "efistub.h"
>>>>>
>>>>> -int efi_loglevel = CONSOLE_LOGLEVEL_DEFAULT;
>>>>> +int efi_loglevel = LOGLEVEL_NOTICE;
>>>>>
>>>>> /**
>>>>> * efi_char16_puts() - Write a UCS-2 encoded string to the console
>>>>>
>>>>> ---
>>>>> base-commit: d7b8f8e20813f0179d8ef519541a3527e7661d3a
>>>>> change-id: 20250708-efi-default-loglevel-4da5a36cac87
>>>>>
>>>>> Best regards,
>>>>> --
>>>>> Aaron Kling <webgeek1234@gmail.com>
>>>>
>>>> This patch was originally suggested a few months ago [0], but as far
>>>> as I can tell was never queued for merge. Since I'm also hitting a
>>>> case where this is relevant, I'm sending this in to bring attention
>>>> back to it.
>>>>
>>>
>>> I've queued this up now - thanks.
>>>
>>
>> And how can I get back the loglevel info? It seems I can only choose
>> between notice, silent and debug now. And the latter two only by also
>> touching the kernel's loglevel.
>>
>> I'm particularly missing [1] in my UART logs now which is helpful in
>> understanding this essential system state.
>>
>
> Hi Jan,
>
> Is efi=debug too noisy for you?
Yes, also because it affects the kernel even more. I'm looking for
"efi=info".
I don't get the reason behind this change anymore as well. If you have a
splash screen shown, weren't you booting with "quiet" before already,
thus also without any stub messages?
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
next prev parent reply other threads:[~2025-08-24 6:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 7:30 Aaron Kling via B4 Relay
2025-07-08 7:31 ` Aaron Kling
2025-07-15 1:35 ` Ard Biesheuvel
2025-08-16 6:52 ` Jan Kiszka
2025-08-24 0:31 ` Ard Biesheuvel
2025-08-24 6:47 ` Jan Kiszka [this message]
2025-08-25 10:44 ` Ard Biesheuvel
2025-08-25 16:34 ` Aaron Kling
2025-08-25 21:28 ` Ard Biesheuvel
2025-08-25 22:09 ` Aaron Kling
2025-08-26 7:23 ` Jan Kiszka
2025-08-26 8:16 ` Ard Biesheuvel
2025-08-26 12:43 ` Ard Biesheuvel
2025-08-26 16:34 ` Aaron Kling
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=09cb03e4-21f3-418c-98f2-66004cc3080f@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=ardb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=webgeek1234@gmail.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
all inboxes | Powered by JetHome®