Bug 471037 - Neon Unstable iso booting - TSC_DEADLINE disabled due to Errata... (Ventoy Stick)
Summary: Neon Unstable iso booting - TSC_DEADLINE disabled due to Errata... (Ventoy S...
Status: REPORTED
Alias: None
Product: neon
Classification: KDE Neon
Component: Live/Install images (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-14 20:18 UTC by publiclyvisibleemail
Modified: 2023-07-04 16:15 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Blank screen with error (1.58 MB, image/jpeg)
2023-06-14 20:18 UTC, publiclyvisibleemail
Details

Note You need to log in before you can comment on or make changes to this bug.
Description publiclyvisibleemail 2023-06-14 20:18:42 UTC
Created attachment 159663 [details]
Blank screen with error

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1.  Put neon-developer-20230213-1602.iso on Ventoy stick
2.  Reboot to Ventoy stick
3.  Pick Normal, (not Grub2) boot, (happens everytime)

OBSERVED RESULT
Black loading screen with following line shown:
[0.050601] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)

EXPECTED RESULT
No such error

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KDE Neon Unstable, Developer iso
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Have never gotten this firmware bug on any other Linux distro, either installed or via Ventoy stick boot.
Comment 1 publiclyvisibleemail 2023-06-14 20:24:08 UTC
Three other messages during loading, after this one:

"[  3.777003] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 022554
[ PRIVRING ]"

"[FAILED] Failed to start Migrate UID 1000 from semi-wrong groups to correct ones.."

"[  24.705267] Bluetooth: hci0: unexpected event for opcode 0xfc2f"
Comment 2 publiclyvisibleemail 2023-07-04 16:15:26 UTC
From further googling, the ACPI bugs appear to be fairly common and don't seem to get in the way of anything, and must just have been suppressed by my last distro, (Fedora) so I just didn't see them, but did see them when I installed OpenSUSE Tumbleweed and Debian yesterday, so definitely not a Neon problem, so can just close this one.

The nouveau one sounds like it may not supporting my card, (Nvidia 970M) but, as with the ACPI ones, both doesn't seem to get in the way / cause problems, (at least until I could install the (535) proprietary drivers) nor is it unique to Neon, so, at best it'd be a nouveau issue and you can close this one here.