Displayed Boot errors pre-login after moving to 22.10

[waburden-4]

ERROR: Unable to locate IOAPIC for GSI 37
ERROR: Unable to locate IOAPIC for GSI 38

Started seeing this pre-login immediately after upgrading 22.04 to 22.10 along with a series of "blacklist: blacklisting hash (-13)" errors
preceding the above. Everything seems to work fine, but why do I get that - it's annoying to be reminded of instability during each boot.
As a former programmer, I find it rather unprofessional to allow this to persist after this much time. I've googled, but I only find
really old issues and there seems to be no explanation or fix. If it will not cause future issues can I hide it from the display during
bootups?

In case it matters, I have also reinstalled and updated 22.10 with the same result - indicating the kernal as source.

[ActionParsnip]

What is the output of

lsb_release -a; uname -a

Thanks

[waburden-4]

Exactly as output:

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.10
Release: 22.10
Codename: kinetic
Linux WAB-E6540 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

[waburden-4]

Hmmm... Ubuntu still reigns as the most popular LInux Distro, but after 3 weeks, the Ubuntu Community for all it's wealth of experience, still had nothing to offer this User? Can't say I wasn't loyal - been with Ubuntu since 2005! Guess moving my other devices to POP-OS was not such a bad strategy after all.

[oldfred]

What hardware?
Similar errors going back many years, but typically hardware related.
More of a warning than a real error.

You may be able to suppress warning with noapic boot parameter.

https://mjmwired.net/kernel/Document...parameters.txt

noapic [SMP,APIC] Tells the kernel to not make use of any
2630 IOAPICs that may be present in the system.

Are you connecting to unusual devices, Windows NTFS or using Virtual Box

[waburden-4]

Thank you for your response. I'll check into these suggestions. My hardware is a Dell Latitude E6540 (UEFI boot). I have used Dell Hardware for years as it's particularly LInux friendly! Had no issues like this in the past. As stated previously, this issue arose first on my upgrade to 22.10. No connections to any unusual devices. My only problematic connection to any device is my old HP Laserject 1020 which is job in itself with every upgrade - but that completely HP's issue and it's unwillingness to play nice with LInux.

Other than these annoying boot messages, the hardware seems to work flawlessly with Ubuntu 22.10 and I quite like the new desktop changes! Stand by...

[oldfred]

I do not see your Dell model in fwupdate. Newer Dell systems are all available for update.
UEFI/BIOS updates brand model list for Dell with (uefi >= 0.6.2 & dell >= 0.7.3)
https://fwupd.org/lvfs/devicelist

Do you have latest UEFI firmware from Dell that is available?

[waburden-4]

Since this laptop is seldom used, I did not get around to trying any of the suggestions offered. I was kinda hoping Lunar Lobster would solve the problem but alas, no. The upgrade went flawlessly but the issue still persists. At this point i'd be happy just hiding the boot error messages rather than exploring firmware upgrades. Can you explain more about "suppressing the noapic boot parameter, previously mentioned. Do I edit grub in /etc/default and what's the syntax and position, for example?

[tea for one]

The suggestion in post 2 here https://ubuntuforums.org/showthread.php?t=2477426 may help.
Example below

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash loglevel=3"
GRUB_CMDLINE_LINUX=""
GRUB_DISABLE_OS_PROBER=true

Don't forget to run sudo update-grub after editing.

[arp-101]

This is not a bug-fix. That is hiding the bug. loglevel=3 means only critical or fatal errors. 2 for warnings and 1 for Information. Finally 0 for debugging. I guess not everyone wants to hide that bug.