Follow-up: after further investigation, the issue now appears likely related to a hardware failure rather than a pure kernel regression.
Over time, the machine became unstable across multiple operating systems and environments: Windows entered BSOD loops multiple Linux distributions failed to boot live/recovery environments produced kernel panics and SquashFS corruption errors The system was eventually returned under warranty, and the manufacturer ultimately replaced the unit entirely after unsuccessful repair attempts. Because of this, I can no longer confidently attribute the original symptoms solely to the kernel update. However, it is still possible that newer kernels interacted differently with marginal hardware, since the failures first became visible after a kernel update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2146606 Title: Regression: NVMe "Invalid Field in Command" errors and instability on Meteor Lake (Kingston OM8PGP41024Q-AA) starting with kernel 6.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146606/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
