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

Fri Feb 8 16:37:14 UTC 2019

** 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.

  IMHO, it would be a good idea to update the Xenial pci.ids to represent
  what Bionic has as of today.

  [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.
+ 
+ 
  [Other information]

  An update of pci.ids has been made on October 3rd 2016.
  This update include the device id 0014 (took from the example in "Test Case".)

- upstream repository:
+ Upstream repository:
  https://github.com/pciutils/pciutils.git

  Upstream commit:
  https://github.com/pciutils/pciutils/commit/701fdd1e

  # git show 701fdd1e | grep SAS3516
  ..
  +	0014 MegaRAID Tri-Mode SAS3516
  ..

  # git describe --contains 701fdd1e
  v3.5.2~1

  # rmadison pciutils
- ==> pciutils | 1:3.3.1-1.1ubuntu1.2 | xenial-updates 
- pciutils | 1:3.5.2-1ubuntu1 | bionic 
- pciutils | 1:3.5.2-1ubuntu2 | cosmic 
- pciutils | 1:3.5.2-1ubuntu2 | disco 
+ ==> pciutils | 1:3.3.1-1.1ubuntu1.2 | xenial-updates
+ pciutils | 1:3.5.2-1ubuntu1 | bionic
+ pciutils | 1:3.5.2-1ubuntu2 | cosmic
+ pciutils | 1:3.5.2-1ubuntu2 | disco
  --

** 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.

  IMHO, it would be a good idea to update the Xenial pci.ids to represent
  what Bionic has as of today.

  [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.

+ The only thing I can think of ... 
+ If we apply commit [701fdd1e], there is some device id renaming, which I guess can impact some possible customer script expecting a certain type of device output, maybe ? 
+ 
+ Example:
+ - 67df  Ellesmere [Polaris10]		
+ + 67df  Ellesmere [Radeon RX 470/480]

  [Other information]

  An update of pci.ids has been made on October 3rd 2016.
  This update include the device id 0014 (took from the example in "Test Case".)

  Upstream repository:
  https://github.com/pciutils/pciutils.git

  Upstream commit:
  https://github.com/pciutils/pciutils/commit/701fdd1e

  # git show 701fdd1e | grep SAS3516
  ..
  +	0014 MegaRAID Tri-Mode SAS3516
  ..

  # git describe --contains 701fdd1e
  v3.5.2~1

  # rmadison pciutils
  ==> pciutils | 1:3.3.1-1.1ubuntu1.2 | xenial-updates
  pciutils | 1:3.5.2-1ubuntu1 | bionic
  pciutils | 1:3.5.2-1ubuntu2 | cosmic
  pciutils | 1:3.5.2-1ubuntu2 | disco
  --

** 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.

  IMHO, it would be a good idea to update the Xenial pci.ids to represent
  what Bionic has as of today.

  [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.

- The only thing I can think of ... 
- If we apply commit [701fdd1e], there is some device id renaming, which I guess can impact some possible customer script expecting a certain type of device output, maybe ? 
+ The only thing I can think of ...
+ If we apply commit [701fdd1e], there is some device id renaming, which I guess can impact some potential users' in-house script expecting a certain type of device output, maybe ?

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

  [Other information]

  An update of pci.ids has been made on October 3rd 2016.
  This update include the device id 0014 (took from the example in "Test Case".)

  Upstream repository:
  https://github.com/pciutils/pciutils.git

  Upstream commit:
  https://github.com/pciutils/pciutils/commit/701fdd1e

  # git show 701fdd1e | grep SAS3516
  ..
  +	0014 MegaRAID Tri-Mode SAS3516
  ..

  # git describe --contains 701fdd1e
  v3.5.2~1

  # rmadison pciutils
  ==> pciutils | 1:3.3.1-1.1ubuntu1.2 | xenial-updates
  pciutils | 1:3.5.2-1ubuntu1 | bionic
  pciutils | 1:3.5.2-1ubuntu2 | cosmic
  pciutils | 1:3.5.2-1ubuntu2 | disco
  --

** 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.

  IMHO, it would be a good idea to update the Xenial pci.ids to represent
  what Bionic has as of today.

  [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.

  The only thing I can think of ...
  If we apply commit [701fdd1e], there is some device id renaming, which I guess can impact some potential users' in-house script expecting a certain type of device output, maybe ?

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

+ If we decide to go with the renaming as well, we could also simply
+ decide to only add what is missing/
+ 
  [Other information]

  An update of pci.ids has been made on October 3rd 2016.
  This update include the device id 0014 (took from the example in "Test Case".)

  Upstream repository:
  https://github.com/pciutils/pciutils.git

  Upstream commit:
  https://github.com/pciutils/pciutils/commit/701fdd1e

  # git show 701fdd1e | grep SAS3516
  ..
  +	0014 MegaRAID Tri-Mode SAS3516
  ..

  # git describe --contains 701fdd1e
  v3.5.2~1

  # rmadison pciutils
  ==> pciutils | 1:3.3.1-1.1ubuntu1.2 | xenial-updates
  pciutils | 1:3.5.2-1ubuntu1 | bionic
  pciutils | 1:3.5.2-1ubuntu2 | cosmic
  pciutils | 1:3.5.2-1ubuntu2 | disco
  --

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

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.

  IMHO, it would be a good idea to update the Xenial pci.ids to
  represent what Bionic has as of today.

  [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.

  The only thing I can think of ...
  If we apply commit [701fdd1e], there is some device id renaming, which I guess can impact some potential users' in-house script expecting a certain type of device output, maybe ?

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

  If we decide to go with the renaming as well, we could also simply
  decide to only add what is missing/

  [Other information]

  An update of pci.ids has been made on October 3rd 2016.
  This update include the device id 0014 (took from the example in "Test Case".)

  Upstream repository:
  https://github.com/pciutils/pciutils.git

  Upstream commit:
  https://github.com/pciutils/pciutils/commit/701fdd1e

  # git show 701fdd1e | grep SAS3516
  ..
  +	0014 MegaRAID Tri-Mode SAS3516
  ..

  # git describe --contains 701fdd1e
  v3.5.2~1

  # rmadison pciutils
  ==> pciutils | 1:3.3.1-1.1ubuntu1.2 | xenial-updates
  pciutils | 1:3.5.2-1ubuntu1 | bionic
  pciutils | 1:3.5.2-1ubuntu2 | cosmic
  pciutils | 1:3.5.2-1ubuntu2 | disco
  --

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