Please change CONFIG_CONSOLE_LOGLEVEL_QUIET to 3

Bug #2049390 reported by Sebastien Bacher
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

The Ubuntu Desktop boot isn't flickerfree today as reported on bug #1970069 , one of the reason is that kernel error messages are often being logged and not filtered out by our default loglevel
(one example with usb messages on https://launchpadlibrarian.net/598152686/20220422_014058.jpg)

Fedora is using CONFIG_CONSOLE_LOGLEVEL_QUIET=3 (instead of 4 which is the default), they change it 5 years ago (https://src.fedoraproject.org/rpms/kernel/c/838818e5), the rational is in the commit message that added the configuration option to the kernel

> This for example will allow distros which want quiet to really mean quiet to set
> CONSOLE_LOGLEVEL_QUIET so that only messages with a higher severity then KERN_ERR (CRIT, ALERT, EMERG)
> get printed, avoiding an endless game of whack-a-mole silencing harmless error messages. '

Could we also get the default change to 3 in Ubuntu?

Tags: noble
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: noble
Revision history for this message
Daniel van Vugt (vanvugt) wrote (last edit ):

Another source of noise is warnings about buggy ACPI implementations (on some, many, machines). I feel hiding those is a bare minimum because getting a less buggy BIOS just isn't feasible in most cases. And displaying the warnings makes Ubuntu look bad.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

I am not sure, which will need to be doublechecked but this may affect boot testing, regression testing, device cert testing that do look for these messages.

Hopefully they all know how to hunt for these messages elsehow, rather than via the graphical console log capture.

Revision history for this message
Andrea Righi (arighi) wrote :

For the general use case I think that reducing the verbosity makes sense. About our testing, I think we're not booting kernels with "quiet", and if we do we should definitely drop it from the kernel boot options.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Since my kernel patch for bug 1970069 is being blocked upstream at the moment, reducing the loglevel to 3 is becoming more of a priority. Otherwise I don't see us making sufficient progress on bug 1970069.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Andrea already applied it to the kernel config, thanks!

https://lists.ubuntu.com/archives/kernel-team/2024-March/149278.html

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Changed in linux (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 6.8.0-20.20

---------------
linux (6.8.0-20.20) noble; urgency=medium

  * noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)

  * Noble update: v6.8.1 upstream stable release (LP: #2058224)
    - x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set
    - Documentation/hw-vuln: Add documentation for RFDS
    - x86/rfds: Mitigate Register File Data Sampling (RFDS)
    - KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests
    - Linux 6.8.1

  * Autopkgtest failures on amd64 (LP: #2048768)
    - [Packaging] update to clang-18

  * Miscellaneous Ubuntu changes
    - SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with
      CONFIG_SECURITY=n
    - [Config] amd64: MITIGATION_RFDS=y

 -- Paolo Pisati <email address hidden> Mon, 18 Mar 2024 11:08:14 +0100

Changed in linux (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.