5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2 5u84
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Ubuntu-power-systems project |
Fix Released
|
Medium
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Medium
|
Joseph Salisbury | ||
Xenial |
Fix Released
|
Medium
|
Joseph Salisbury | ||
Zesty |
Fix Released
|
Medium
|
Joseph Salisbury | ||
Artful |
Fix Released
|
Medium
|
Joseph Salisbury |
Bug Description
== SRU Justification ==
This bug is resolved by commit 62e62ffd95539b9
Without this patch, the symlink in sysfs which binds a SAS device to an enclosure
slot does not get created. This makes disk hotplug near impossible on large
JBOD disk drawers.
Commit 62e62ffd95 is also needed in Xenial. However, Xenial also needed some
prereq commits, so it's SRU will be sent separately.
Commit 62e62ffd95 is in mainline as of 4.13-rc1.
== Fix ==
commit 62e62ffd95539b9
Author: Maurizio Lombardi <email address hidden>
Date: Tue Jun 27 11:53:27 2017 +0200
scsi: ses: do not add a device to an enclosure if enclosure_
== Regression Potential ==
This patch was also cc'd and applied to upstream stable, so there is
upstream confidence in it.
== Test Case ==
A test kernel was built with this patch and tested by the original bug reporter.
The bug reporter states the test kernel resolved the bug.
This is a request to add the following upstream commit to both Ubuntu 16.04.1 and 16.04.2:
Without this patch, the symlink in sysfs which binds a SAS device to an enclosure slot does not get created. This makes disk hotplug near impossible on large JBOD disk drawers.
You should be able to do:
ls /sys/block/
and see something like:
enclosure_device:1
If you cd to this directory, you can then access the SES controls for that slot to flash the LED to assist in locating the disk to replace a failed disk.
Currently with 16.04.1 and 16.04.2, these symlinks are not getting created.
CVE References
tags: | added: architecture-ppc64le bugnameltc-155011 severity-critical targetmilestone-inin16041 |
Changed in ubuntu: | |
assignee: | nobody → Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) |
affects: | ubuntu → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
assignee: | Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) → Canonical Kernel Team (canonical-kernel-team) |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Xenial): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Yakkety): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Xenial): | |
status: | New → Triaged |
Changed in linux (Ubuntu Yakkety): | |
status: | New → Triaged |
tags: | added: ubuntu-16.04 |
Changed in linux (Ubuntu Yakkety): | |
status: | In Progress → Won't Fix |
Changed in ubuntu-power-systems: | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Zesty): | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
Changed in ubuntu-power-systems: | |
status: | New → In Progress |
tags: | added: triage-g |
tags: |
added: triage-a removed: triage-g |
no longer affects: | linux (Ubuntu Yakkety) |
Changed in linux (Ubuntu Artful): | |
status: | In Progress → Fix Released |
assignee: | Canonical Kernel Team (canonical-kernel-team) → Joseph Salisbury (jsalisbury) |
description: | updated |
Changed in linux (Ubuntu Zesty): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Xenial): | |
status: | In Progress → Fix Committed |
Changed in ubuntu-power-systems: | |
status: | In Progress → Fix Committed |
tags: |
added: triage-g removed: triage-a |
Changed in ubuntu-power-systems: | |
status: | Fix Committed → Fix Released |
I built a Yakkety test kernel with commit 9373eba6cfae. The test kernel can be downloaded from:
http:// kernel. ubuntu. com/~jsalisbury /lp1693369/ yakkety/
Can you test this kernel and see if it resolves this bug? Xenial needs some prereq commits, so I'm working on identifying them and and should have that test kernel shortly.