[Bug 1815212] Re: [Xenial][SRU] Update pci.ids for pciutils

[Eric Desrochers]

** Description changed:

  [Impact]
  
  pci.ids table in Xenial seems a little bit behind in term of new device
  id added since last time it was updated.
  
  Some user are observing that their new device doesn't show up because
  they don't exist in the pci.ids file yet.
  
  User or troubleshooter may get a wrong impression that, for instance,
  the correct raid controller is not present, if the user doesn't read the
  PCI bus address.
  
  While we are here, I will update Xenial and Bionic to be at the same
  version level (Version: 2018.07.21) of current devel release (Disco)
  which isn't too far behind current upstream (github) one in master
  branch.
  
  x/pciutils-3.3.1/pci.ids:#	Version: 2016.01.02
  b/pciutils-3.5.2/pci.ids:#	Version: 2017.03.16
  c/pciutils-3.5.2/pci.ids:#	Version: 2018.07.21
  d/pciutils-3.5.2/pci.ids:#	Version: 2018.07.21
  upstream/pciutils/pci.ids:#	Version: 2018.08.12
  
- 
  [Test case]
  
  Here's an example took by a user using a device id (0014) not in the
  Xenial pci.ids table:
  
  Xenial:
  60:00.0 RAID bus controller: LSI Logic / Symbios Logic Device 0014 (rev 01)
  
  Bionic:
  60:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID Tri-Mode SAS3516 (rev 01)
  
  [Regression Potential]
  
- Low, no core functionality change. 
+ Low, no core functionality change.
  The intention is to only update pci.ids table list to recognize new pci vendor list/hw.
  
  The only thing I can think of ...
- In some cases there is some device id renaming, which I guess can "possibly" impact some user script or HW inventory solution expecting a certain type of device id output.
+ In some cases there is some device id renaming, which I guess can "possibly" impact some user script or HW inventory solution expecting a certain type of device id output, but I don't expect this impact to be high, should be consider low and easy to fix IMHO.
  
  Example:
  - 67df  Ellesmere [Polaris10]
  + 67df  Ellesmere [Radeon RX 470/480]
  
  [Other information]

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pciutils in Ubuntu.
https://bugs.launchpad.net/bugs/1815212

Title:
  [Xenial][SRU] Update pci.ids for pciutils

Status in pciutils package in Ubuntu:
  Fix Released
Status in pciutils source package in Xenial:
  In Progress
Status in pciutils source package in Bionic:
  In Progress

Bug description:
  [Impact]

  pci.ids table in Xenial seems a little bit behind in term of new
  device id added since last time it was updated.

  Some user are observing that their new device doesn't show up because
  they don't exist in the pci.ids file yet.

  User or troubleshooter may get a wrong impression that, for instance,
  the correct raid controller is not present, if the user doesn't read
  the PCI bus address.

  While we are here, I will update Xenial and Bionic to be at the same
  version level (Version: 2018.07.21) of current devel release (Disco)
  which isn't too far behind current upstream (github) one in master
  branch.

  x/pciutils-3.3.1/pci.ids:#	Version: 2016.01.02
  b/pciutils-3.5.2/pci.ids:#	Version: 2017.03.16
  c/pciutils-3.5.2/pci.ids:#	Version: 2018.07.21
  d/pciutils-3.5.2/pci.ids:#	Version: 2018.07.21
  upstream/pciutils/pci.ids:#	Version: 2018.08.12

  [Test case]

  Here's an example took by a user using a device id (0014) not in the
  Xenial pci.ids table:

  Xenial:
  60:00.0 RAID bus controller: LSI Logic / Symbios Logic Device 0014 (rev 01)

  Bionic:
  60:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID Tri-Mode SAS3516 (rev 01)

  [Regression Potential]

  Low, no core functionality change.
  The intention is to only update pci.ids table list to recognize new pci vendor list/hw.

  The only thing I can think of ...
  In some cases there is some device id renaming, which I guess can "possibly" impact some user script or HW inventory solution expecting a certain type of device id output, but I don't expect this impact to be high, should be consider low and easy to fix IMHO.

  Example:
  - 67df  Ellesmere [Polaris10]
  + 67df  Ellesmere [Radeon RX 470/480]

  [Other information]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pciutils/+bug/1815212/+subscriptions