** 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: + lspci on Xenial: 60:00.0 RAID bus controller: LSI Logic / Symbios Logic Device 0014 (rev 01) - Bionic: + lspci on Bionic: 60:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID Tri-Mode SAS3516 (rev 01) + + [Pending SRU status] + + * Regression in autopkgtest for linux (ppc64el): test log ## Xenial + https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20190211_161758_29cc4@/log.gz + + This start failing before this current SRU on 2019-02-05 ... so far 3 + same exact failure occurred, meaning this is a recurrent ADT failure. + [Regression Potential] Low, no core functionality change. The intention is to only update pci.ids table list to recognise new PCI vendor/product list, by updating it to the same version level as Cosmic and Disco has as of today. 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 and/or HW inventory solution. If this happens to certain users, I don't expect it to have a major impact and this should can be consider low and easy to fix by the user or admin of the HW inventory solution ... IMHO. Example: - 67df Ellesmere [Polaris10] + 67df Ellesmere [Radeon RX 470/480] [Other information] Confirmed w/ vorlon (SRU verification team) on #ubuntu-release https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases For Long Term Support releases we regularly want to enable new hardware. Such changes are appropriate provided that we can ensure not to affect upgrades on existing hardware. For example, modaliases of newly introduced drivers must not overlap with previously shipped drivers. This also includes updating hardware description data such as udev's keymaps, media-player-info, mobile broadband vendors, or PCI vendor/product list updates.
** 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: lspci on Xenial: 60:00.0 RAID bus controller: LSI Logic / Symbios Logic Device 0014 (rev 01) lspci on Bionic: 60:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID Tri-Mode SAS3516 (rev 01) [Pending SRU status] * Regression in autopkgtest for linux (ppc64el): test log ## Xenial https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20190211_161758_29cc4@/log.gz This start failing before this current SRU on 2019-02-05 ... so far 3 - same exact failure occurred, meaning this is a recurrent ADT failure. - + same exact failure occurred, meaning this is a recurrent ADT failure, + nothing to do with the ongoing SRU. [Regression Potential] Low, no core functionality change. The intention is to only update pci.ids table list to recognise new PCI vendor/product list, by updating it to the same version level as Cosmic and Disco has as of today. 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 and/or HW inventory solution. If this happens to certain users, I don't expect it to have a major impact and this should can be consider low and easy to fix by the user or admin of the HW inventory solution ... IMHO. Example: - 67df Ellesmere [Polaris10] + 67df Ellesmere [Radeon RX 470/480] [Other information] Confirmed w/ vorlon (SRU verification team) on #ubuntu-release https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases For Long Term Support releases we regularly want to enable new hardware. Such changes are appropriate provided that we can ensure not to affect upgrades on existing hardware. For example, modaliases of newly introduced drivers must not overlap with previously shipped drivers. This also includes updating hardware description data such as udev's keymaps, media-player-info, mobile broadband vendors, or PCI vendor/product list updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815212 Title: [Xenial][Bionic][SRU] Update pci.ids to version 2018.07.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pciutils/+bug/1815212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
