** Changed in: kunpeng920/ubuntu-19.04
Status: New => Triaged
** Changed in: kunpeng920/ubuntu-19.10
Status: New => Triaged
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: kunpeng920
Status: New => Triaged
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in: linux (Ubuntu Disco)
Status: New => Triaged
** Changed in: linux (Ubuntu Eoan)
Status: New => Triaged
** Changed in: linux (Ubuntu Focal)
Status: New => Fix Released
** Changed in: kunpeng920/ubuntu-18.04
Milestone: None => ubuntu-18.04.4-sru-1
** Changed in: kunpeng920/ubuntu-18.04-hwe
Milestone: None => ubuntu-18.04.4-sru-1
** Changed in: kunpeng920/ubuntu-19.04
Milestone: None => ubuntu-19.04-sru-11
** Changed in: kunpeng920/ubuntu-19.10
Milestone: None => ubuntu-19.10-sru-5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1853997
Title:
[sas-1126]scsi: hisi_sas: Fix the conflict between device gone and
host reset
Status in kunpeng920:
Triaged
Status in kunpeng920 ubuntu-18.04 series:
Triaged
Status in kunpeng920 ubuntu-18.04-hwe series:
Triaged
Status in kunpeng920 ubuntu-19.04 series:
Triaged
Status in kunpeng920 ubuntu-19.10 series:
Triaged
Status in kunpeng920 ubuntu-20.04 series:
Fix Committed
Status in kunpeng920 upstream-kernel series:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux source package in Disco:
Triaged
Status in linux source package in Eoan:
Triaged
Status in linux source package in Focal:
Fix Released
Bug description:
"[Steps to Reproduce]
1. Close all the PHYS;
2. Inject error;
3. Open one PHY;
[Actual Results]
Some disk will be lost
[Expected Results]
No disk will be lost
[Reproducibility]
occasionally
[Additional information]
Hardware: D06 CS
Firmware: NA+I59
Kernel: NA
[Resolution]
When init device for SAS disks, it will send TMF IO to clear disks. At that
time TMF IO is broken by some operations such as injecting controller reset
from HW RAs event, the TMF IO will be timeout, and at last device will be
gone. Print is as followed:
hisi_sas_v3_hw 0000:74:02.0: dev[240:1] found
...
hisi_sas_v3_hw 0000:74:02.0: controller resetting...
hisi_sas_v3_hw 0000:74:02.0: phyup: phy7 link_rate=10(sata)
hisi_sas_v3_hw 0000:74:02.0: phyup: phy0 link_rate=9(sata)
hisi_sas_v3_hw 0000:74:02.0: phyup: phy1 link_rate=9(sata)
hisi_sas_v3_hw 0000:74:02.0: phyup: phy2 link_rate=9(sata)
hisi_sas_v3_hw 0000:74:02.0: phyup: phy3 link_rate=9(sata)
hisi_sas_v3_hw 0000:74:02.0: phyup: phy6 link_rate=10(sata)
hisi_sas_v3_hw 0000:74:02.0: phyup: phy5 link_rate=11
hisi_sas_v3_hw 0000:74:02.0: phyup: phy4 link_rate=11
hisi_sas_v3_hw 0000:74:02.0: controller reset complete
hisi_sas_v3_hw 0000:74:02.0: abort tmf: TMF task timeout and not done
hisi_sas_v3_hw 0000:74:02.0: dev[240:1] is gone
sas: driver on host 0000:74:02.0 cannot handle device 5000c500a75a860d,
error:5
To improve the reliability, retry TMF IO max of 3 times for SAS disks which
is the same as softreset does."
scsi: hisi_sas: Fix the conflict between device gone and host reset
To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1853997/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
