[Xenial] nvme: Quirks for PM1725 controllers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Critical
|
Canonical Kernel Team | ||
Xenial |
Fix Released
|
Critical
|
Canonical Kernel Team | ||
Yakkety |
Won't Fix
|
Critical
|
Canonical Kernel Team | ||
Zesty |
Fix Released
|
Critical
|
Canonical Kernel Team | ||
Artful |
Fix Released
|
Critical
|
Canonical Kernel Team |
Bug Description
== SRU Xenial ==
Pick up the following device quirk to resolve a hardware/firmware bug affectung some NVMe drives that use the PM1725 controller. Under adverse circumstances the bug can result in data corruption and loss.
nvme: Quirks for PM1725 controllers
PM1725 controllers have a couple of quirks that need to be handled in
the driver:
- I/O queue depth must be limited to 64 entries on controllers that do
not report MQES.
- The host interface registers go offline briefly while resetting the
chip. Thus a delay is needed before checking whether the controller
is ready.
Note that the admin queue depth is also limited to 64 on older versions
of this board. Since our NVME_AQ_DEPTH is now 32 that is no longer an
issue.
Signed-off-by: Martin K. Petersen <email address hidden>
Signed-off-by: Sagi Grimberg <email address hidden>
CVE References
Changed in linux (Ubuntu Xenial): | |
assignee: | nobody → Canonical Kernel Team (canonical-kernel-team) |
status: | New → Triaged |
Changed in linux (Ubuntu Yakkety): | |
status: | New → Triaged |
Changed in linux (Ubuntu Zesty): | |
status: | New → Triaged |
Changed in linux (Ubuntu Artful): | |
status: | New → Triaged |
Changed in linux (Ubuntu Xenial): | |
importance: | Undecided → Critical |
Changed in linux (Ubuntu Zesty): | |
importance: | Undecided → Critical |
Changed in linux (Ubuntu Yakkety): | |
importance: | Undecided → Critical |
Changed in linux (Ubuntu Artful): | |
importance: | Undecided → Critical |
Changed in linux (Ubuntu Yakkety): | |
assignee: | nobody → Canonical Kernel Team (canonical-kernel-team) |
Changed in linux (Ubuntu Zesty): | |
assignee: | nobody → Canonical Kernel Team (canonical-kernel-team) |
Changed in linux (Ubuntu Artful): | |
assignee: | nobody → Canonical Kernel Team (canonical-kernel-team) |
tags: | added: kernel-da-key |
tags: | added: artful xenial yakkety zesty |
Changed in linux (Ubuntu Artful): | |
status: | Triaged → Fix Committed |
Changed in linux (Ubuntu Xenial): | |
status: | Triaged → Fix Committed |
Changed in linux (Ubuntu Yakkety): | |
status: | Triaged → Fix Committed |
Changed in linux (Ubuntu Zesty): | |
status: | Triaged → Fix Committed |
This bug is awaiting verification that the 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- zesty' to 'verification- done-zesty' . If the problem still exists, change the tag 'verification- needed- zesty' to 'verification- failed- zesty'.
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!