** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
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
Status in linux package in Ubuntu:
New
Bug description:
I am reporting a kernel regression affecting NVMe behavior on recent
Intel Meteor Lake hardware.
Hardware:
- CPU: Intel Core Ultra 7 (Meteor Lake, family 6 model 189)
- SSD: Kingston OM8PGP41024Q-AA (NVMe 1.4)
Observed behavior:
Kernel 6.14:
- system stable
- no increase in NVMe error log entries
Kernel 6.16 (mainline):
- system stable
- NVMe error log entries remain constant over time
Kernel 6.17 and newer (Ubuntu HWE):
- NVMe error log entries increase during normal usage
- SMART log shows repeated errors:
"Invalid Field in Command"
- system becomes unstable after some time:
- application crashes (segfaults)
- filesystem inconsistencies
SMART excerpt:
- Media and Data Integrity Errors: 0
- Error Information Log Entries: increasing during runtime
- Error type: "Invalid Field in Command"
Important observation:
- reverting to kernel 6.16 stops the increase in error count
- system stability is restored under 6.16
Reproduction:
1. Boot kernel 6.17 or newer
2. Use system normally
3. Observe increasing NVMe error count (smartctl)
4. System instability follows
Regression window:
- Not present in 6.16
- Present in 6.17 and newer kernels
Notes:
- Disk health otherwise reports OK
- No media errors reported
- Issue appears to be NVMe driver/controller interaction rather than hardware failure
This looks like a regression in the NVMe driver or related subsystem
triggered by newer kernels on this hardware.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146606/+subscriptions
Комментариев нет:
Отправить комментарий