** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
     Assignee: dann frazier (dannf)
       Status: In Progress

** Changed in: linux (Ubuntu Disco)
       Status: New => In Progress

** Changed in: linux (Ubuntu Disco)
     Assignee: (unassigned) => dann frazier (dannf)

** Summary changed:

- phy linkrate persists after deactivation
+ libsas: old linkrate advertised after phy disabled

** Description changed:

  [Impact]
  sysfs continues to expose a valid phy linkrate even after the phy has been 
disabled.
  
  [Test Case]
  Using hisi_sas, a libsas-based driver:
  (initramfs) cd /sys/class/sas_phy/phy-0\:0\:20
- (initramfs) cat negotiated_linkrate 
+ (initramfs) cat negotiated_linkrate
  12.0 Gbit
- (initramfs) echo 0 > enable 
+ (initramfs) echo 0 > enable
  [   59.172411] hisi_sas_v3_hw 0000:74:02.0: phydown: phy0 phy_state=0xfe
  [   59.178851] hisi_sas_v3_hw 0000:74:02.0: erroneous completion iptt=4028 
task=00000000bb3ab63f dev id=1 CQ hdr: 0x1103 0x10fbc 0x0 0x20000 Error info: 
0x0 0x4000000 0x0 0x0
  [   59.194139] sas: smp_execute_task_sg: task to dev 500e004aaaaaaa1f 
response: 0x0 status 0x2
- (initramfs) cat negotiated_linkrate 
+ (initramfs) cat negotiated_linkrate
  12.0 Gbit
+ 
+ [Fix]
+ d8649fc1c5e40 scsi: libsas: Do discovery on empty PHY to update PHY info
+ 085f104a83d56 scsi: libsas: Inject revalidate event for root port event
  
  [Regression Risk]
  Impact is limited to drivers built on top of libsas.

-- 
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/1830435

Title:
  libsas: old linkrate advertised after phy disabled

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress

Bug description:
  [Impact]
  sysfs continues to expose a valid phy linkrate even after the phy has been 
disabled.

  [Test Case]
  Using hisi_sas, a libsas-based driver:
  (initramfs) cd /sys/class/sas_phy/phy-0\:0\:20
  (initramfs) cat negotiated_linkrate
  12.0 Gbit
  (initramfs) echo 0 > enable
  [   59.172411] hisi_sas_v3_hw 0000:74:02.0: phydown: phy0 phy_state=0xfe
  [   59.178851] hisi_sas_v3_hw 0000:74:02.0: erroneous completion iptt=4028 
task=00000000bb3ab63f dev id=1 CQ hdr: 0x1103 0x10fbc 0x0 0x20000 Error info: 
0x0 0x4000000 0x0 0x0
  [   59.194139] sas: smp_execute_task_sg: task to dev 500e004aaaaaaa1f 
response: 0x0 status 0x2
  (initramfs) cat negotiated_linkrate
  12.0 Gbit

  [Fix]
  d8649fc1c5e40 scsi: libsas: Do discovery on empty PHY to update PHY info
  085f104a83d56 scsi: libsas: Inject revalidate event for root port event

  [Regression Risk]
  Impact is limited to drivers built on top of libsas.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830435/+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

Reply via email to