Micron NVME storage failure [1344,5407]
Bug #1998883 reported by
AceLan Kao
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Medium
|
AceLan Kao | ||
Kinetic |
Fix Released
|
Undecided
|
Unassigned | ||
linux-oem-5.17 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
AceLan Kao | ||
Kinetic |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Micron NVME storage fails to init with below error messages
[ 8.965698] nvme nvme1: Duplicate cntlid 0 with nvme0, subsys nqn.2014-
[ 8.966111] nvme nvme1: Removing after probe failure status: -22
[Fix]
The patch from v5.19 add a quirk for Micron NVME fixes this issue
41f38043f884 nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH
[Test]
Verified with 5.17 OEM kernel on the reported machine.
Didn't verify with 5.15 Jammy kernel, but confirmed the kernel could be compiled.
[Where problems could occur]
The impact should be low as it adds one device ID into a quirk.
CVE References
Changed in linux (Ubuntu Jammy): | |
status: | New → In Progress |
assignee: | nobody → AceLan Kao (acelankao) |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
assignee: | nobody → AceLan Kao (acelankao) |
status: | New → In Progress |
Changed in linux-oem-5.17 (Ubuntu): | |
status: | New → Invalid |
Changed in linux (Ubuntu): | |
status: | New → Invalid |
description: | updated |
tags: | added: oem-priority originate-from-1997768 somerville |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-jammy removed: verification-needed-jammy |
Changed in linux (Ubuntu Jammy): | |
importance: | Undecided → Medium |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Kinetic): | |
status: | New → Fix Released |
Changed in linux-oem-5.17 (Ubuntu Kinetic): | |
status: | New → Invalid |
Changed in hwe-next: | |
status: | New → Fix Released |
To post a comment you must log in.
This bug is awaiting verification that the linux-oem- 5.17/5. 17.0-1025. 26 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- jammy' to 'verification- done-jammy' . If the problem still exists, change the tag 'verification- needed- jammy' to 'verification- failed- jammy'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!