** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Xenial)
Status: New => Won't Fix
** Description changed:
[Impact]
SATA disks may be unusable
will not be usable when:
- The disk is connected through a SAS expander
- Controller uses a libsas-based driver (mvsas, aic94xx, hisi_sas)
- link rate between expander & disk is greater than link between controller
and expander
+ This is unlikely to occur in any production environment, but has
+ occurred in early silicon testing. Fixing this would be helpful in those
+ environments.
+
[Test Case]
See conditions in "Impact"
Can be simulated with:
for f in /sys/class/sas_phy/phy-1\:*/maximum_linkrate; do
- echo "3.0 Gbit" | sudo tee $f
+ echo "3.0 Gbit" | sudo tee $f
done
[Fix]
cec9771d2e954 scsi: libsas: Support SATA PHY connection rate unmatch fixing
during discovery
[Regression Risk]
Impact is restricted to drivers that use libsas: mvsas, aic94xx & hisi_sas.
Code change is all within an "if" statement that meets these restrictions.
A bug in this code could possibly reduce the speed of an otherwise working
disk connection.
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1821408
Title:
scsi: libsas: Support SATA PHY connection rate unmatch fixing during
discovery
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Won't Fix
Status in linux source package in Bionic:
Won't Fix
Status in linux source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
In Progress
Bug description:
[Impact]
SATA disks may be unusable
will not be usable when:
- The disk is connected through a SAS expander
- Controller uses a libsas-based driver (mvsas, aic94xx, hisi_sas)
- link rate between expander & disk is greater than link between controller
and expander
This is unlikely to occur in any production environment, but has
occurred in early silicon testing. Fixing this would be helpful in
those environments.
[Test Case]
See conditions in "Impact"
Can be simulated with:
for f in /sys/class/sas_phy/phy-1\:*/maximum_linkrate; do
echo "3.0 Gbit" | sudo tee $f
done
[Fix]
cec9771d2e954 scsi: libsas: Support SATA PHY connection rate unmatch fixing
during discovery
[Regression Risk]
Impact is restricted to drivers that use libsas: mvsas, aic94xx & hisi_sas.
Code change is all within an "if" statement that meets these restrictions.
A bug in this code could possibly reduce the speed of an otherwise working
disk connection.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821408/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
