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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

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!


** Tags added: verification-needed-focal

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

Title:
  [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]
  Whenever the driver is adding a vSES to virtual-phys list it is
  reinitializing the list head. Hence those vSES devices which were added
  previously are lost.

  [FIXES]

  Stop reinitializing the list every time a new vSES device is added.

  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=4c51f9569651

  CommitID: 4c51f956965120b3441cdd39c358b87daba13e19

  [TESTING]

  Load the mpt3sas driver on the system where Brodcom's HBA 9500 Tri-Mode 
Storage Adapter (IT HBA Aero/Ventura) is connected to two backplanes (so that 
two vSES device get configured on the HBA). After loading the driver user 
should able to access both the vSES devices. Also even after performing host 
reset operation user must able to access both the vSES devices.
  i.e. lsscsi must list both the vSES devices after loading the driver and also 
after performing host reset operation.

  [REGRESSION RISK]

  There is no regression risk with this bug fix patch.

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