Error messages on reboot after upgrade

[blueberry]

Post upgrade:
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-56-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5 CPU 660 @ 3.33GHz
Memory: 5.7 GiB of RAM
Graphics Processor: AMD CEDAR

Upgraded from 20.04 to 22.04 by the upgrade icon that appeared on desktop panel.

The issue below did not exist while running 20.04

After upgrade to 22.04, on computer reboot the following message appears on black screen, if anyone knows what needs to be done please let me know.


[ 0.126512] x86/CPU: VMX (outside TXT) disabled by BIOS

[ 0.286552] acpi LNXCPU:00: Invalid PBLK length [7]

[ 0.286570] acpi LNXCPU:01: Invalid PBLK length [7]

[ 0.286578] acpi LNXCPU:02: Invalid PBLK length [7]

[ 0.286587] acpi LNXCPU:02: Invalid PBLK length [7]

[ 0.286888] ACPI BIOS Error (bug): \_SB.PCIO._OSC: Excess arguments - ASL dec

lared 5, ACPI requires 4 (20210730/nsarguments - 162)

[ 0.286962] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCIO._

OSC.CAPD], AE-ALREADY-EXISTS (20210730/dsfield-184)

[ 0.286969] ACPI Error: AE-ALREADY-EXISTS, CreateBufferField failure (2021073

0/dswload2-477)

[ 0.287009] ACPI Error: Aborting method |-SB.PCIO._OSC due to previous error

(AE-ALREADY-EXISTS) (20210730/psparse-529)

[ 1.045846] ima: Error Communicating to TPM chip

[ 1.061872] ima: Error Communicating to TPM chip

[ 1.077847] ima: Error Communicating to TPM chip

[ 1.093841] ima: Error Communicating to TPM chip

[ 1.109841] ima: Error Communicating to TPM chip

[ 1.125841] ima: Error Communicating to TPM chip

[ 1.135982] ima: Error Communicating to TPM chip

[ 1.139982] ima: Error Communicating to TPM chip

[ 35.107148] ================================================== =====================

[ 35.107215] UBSAN: invalid-load in/build/Linux-Mux13y/Linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:497:16

[ 35.107277] load of value 255 is not a valid value for type ‘_Bool’

[ 35.107875] ================================================== =====================

[ 35.112272] ================================================== =====================

[ 35.112332] UBSAN: invalid-load in/build/Linux-Mux13y/Linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:488:16

[ 35.112412] load of value 255 is not a valid value for type ‘_Bool’

[ 35.112883] ================================================== =====================


There was also a problem with partition label and mounting of extended partition as explained here:
https://www.kubuntuforums.net/forum/...-after-upgrade

[claydoh]

Does it boot and run normally?
If so, this is most likely safe to ignore
I don't know why these are not being properly hidden, if they are purely messaging/informational and not critical errors, but these do not look critical at all.

[Schwarzer Kater]

If everthing runs normally, try adding "loglevel=3" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub to hide the messages - don't forget to sudo update-grub afterwards.

[claydoh]

try adding "loglevel=3" to GRUB_CMDLINE_LINUX_DEFAULT

Might this potentially hide some useful or more important messaging?
This concern as well as the inconsistencies with this recently is why I did not suggest this.

[blueberry]

Thank you for your advice. Yes the computer currently is booting and seems to be running normally.

[Schwarzer Kater]

Might this potentially hide some useful or more important messaging? […]

Of course it could - that is why I wrote "If everything runs normally", and to be a bit more specific (sorry…) I meant by that:
"If you already have confirmed (one by one) that these messages are not important for the state of your system and no further actions are required."

One can of course always see all messaging with journalctl or KSystemLog - the "loglevel=X" in /etc/default/grub only suppresses these messages on screen during the boot process.

One can determine by X in "loglevel=X" what is important enough for one to show during boot.


From https://www.kernel.org/doc/html/late...arameters.html :

loglevel= All Kernel Messages with a loglevel smaller than the
console loglevel will be printed to the console. It can
also be changed with klogd or other programs. The
loglevels are defined as follows:

0 (KERN_EMERG) system is unusable
1 (KERN_ALERT) action must be taken immediately
2 (KERN_CRIT) critical conditions
3 (KERN_ERR) error conditions
4 (KERN_WARNING) warning conditions
5 (KERN_NOTICE) normal but significant condition
6 (KERN_INFO) informational
7 (KERN_DEBUG) debug-level messages


PS: Which inconsistencies do you mean?