[Kernel-packages] [Bug 1942589] Re: Ubuntu 5.4.0-81 stops bnx2x loading hardware
I've tested 5.4.0-90 from focal-proposed and the issue is no longer reproducible and bnx2x works as in 5.4.0-80 before: $ uname -a Linux jackrabbit-build 5.4.0-90-generic #101-Ubuntu SMP Fri Oct 15 20:00:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ dmesg | grep bnx [2.227656] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.713.36-0 (2014/02/10) [2.227942] bnx2x :06:00.0: msix capability found [2.228274] bnx2x :06:00.0: part number 0-0-0-0 [2.366450] bnx2x :06:00.0: 63.008 Gb/s available PCIe bandwidth (8 GT/s x8 link) [2.366558] bnx2x :06:00.1: msix capability found [2.366874] bnx2x :06:00.1: part number 0-0-0-0 [2.502096] bnx2x :06:00.1: 63.008 Gb/s available PCIe bandwidth (8 GT/s x8 link) [2.502201] bnx2x :06:00.2: msix capability found [2.502452] bnx2x :06:00.2: part number 0-0-0-0 [2.629572] bnx2x :06:00.2: 63.008 Gb/s available PCIe bandwidth (8 GT/s x8 link) [2.629679] bnx2x :06:00.3: msix capability found [2.629930] bnx2x :06:00.3: part number 0-0-0-0 [2.753882] bnx2x :06:00.3: 63.008 Gb/s available PCIe bandwidth (8 GT/s x8 link) [2.753987] bnx2x :06:00.4: msix capability found [2.754226] bnx2x :06:00.4: part number 0-0-0-0 [2.881840] bnx2x :06:00.4: 63.008 Gb/s available PCIe bandwidth (8 GT/s x8 link) [2.881946] bnx2x :06:00.5: msix capability found [2.882202] bnx2x :06:00.5: part number 0-0-0-0 [3.010083] bnx2x :06:00.5: 63.008 Gb/s available PCIe bandwidth (8 GT/s x8 link) [3.013799] bnx2x :06:00.1 eno50: renamed from eth1 [3.044278] bnx2x :06:00.0 eno49: renamed from eth0 [3.076775] bnx2x :06:00.2 eno51: renamed from eth2 [3.108745] bnx2x :06:00.4 eno53: renamed from eth4 [3.140563] bnx2x :06:00.3 eno52: renamed from eth3 [3.164303] bnx2x :06:00.5 eno54: renamed from eth5 -- 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/1942589 Title: Ubuntu 5.4.0-81 stops bnx2x loading hardware Status in linux package in Ubuntu: Confirmed Bug description: Server: HPE BL460c Gen9 Network: HP FlexFabric 10Gb 2-port 536FLB Adapter (Broadcom/Qlogic Net Extreme II 10/20GBE) Using ubuntu 20.04.2 with linux kernel 5.4.0-80 all functionality worked however upon upgrades via apt to 20.04.3 which uses linux kernel 5.4.0-81, ubuntu is unable to load the drivers for the network device. Below is the output for both kernels when the system is booted. ### # Kernel 5.4.0-80 working # ### ubuntu@server:$ dmesg | grep bnx2x [6.648833] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.713.36-0 (2014/02/10) [6.695219] bnx2x :06:00.0: msix capability found [6.719107] bnx2x :06:00.0: part number 0-0-0-0 [7.112390] bnx2x :06:00.0: 63.008 Gb/s available PCIe bandwidth (8 GT/s x8 link) [7.112504] bnx2x :06:00.1: msix capability found [7.112889] bnx2x :06:00.1: part number 0-0-0-0 [7.320779] bnx2x :06:00.1: 63.008 Gb/s available PCIe bandwidth (8 GT/s x8 link) [7.323549] bnx2x :06:00.0 eno49: renamed from eth0 [7.343281] bnx2x :06:00.1 eno50: renamed from eth1 [ 16.321102] bnx2x :06:00.1 eno50: using MSI-X IRQs: sp 130 fp[0] 132 ... fp[7] 139 [ 16.770833] bnx2x :06:00.1 eno50: NIC Link is Up, 1 Mbps full duplex, Flow control: ON - receive & transmit [ 17.136896] bnx2x :06:00.0 eno49: using MSI-X IRQs: sp 120 fp[0] 122 ... fp[7] 129 [ 17.526831] bnx2x :06:00.0 eno49: NIC Link is Up, 1 Mbps full duplex, Flow control: ON - receive & transmit ubuntu@server:$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno49: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 9e:b2:88:1c:ea:40 brd ff:ff:ff:ff:ff:ff 3: eno50: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 9e:b2:88:1c:ea:40 brd ff:ff:ff:ff:ff:ff 4: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 9e:b2:88:1c:ea:40 brd ff:ff:ff:ff:ff:ff inet 10.0.0.68/24 brd 10.0.0.255 scope global bond0 valid_lft forever preferred_lft forever inet6 fe80::9cb2:88ff:fe1c:ea40/64 scope link valid_lft forever preferred_lft forever ubuntu@server:$ sudo lshw -C network *-network:0 description: Ethernet interface product: BCM57840 NetXtreme II 10/20-Gigabit Ethernet vendor: Broadcom Inc
[Kernel-packages] [Bug 1942589] Re: Ubuntu 5.4.0-81 stops bnx2x loading hardware
Looks like this might be fixed in 5.4.0-90 with: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945707 -- 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/1942589 Title: Ubuntu 5.4.0-81 stops bnx2x loading hardware Status in linux package in Ubuntu: Confirmed Bug description: Server: HPE BL460c Gen9 Network: HP FlexFabric 10Gb 2-port 536FLB Adapter (Broadcom/Qlogic Net Extreme II 10/20GBE) Using ubuntu 20.04.2 with linux kernel 5.4.0-80 all functionality worked however upon upgrades via apt to 20.04.3 which uses linux kernel 5.4.0-81, ubuntu is unable to load the drivers for the network device. Below is the output for both kernels when the system is booted. ### # Kernel 5.4.0-80 working # ### ubuntu@server:$ dmesg | grep bnx2x [6.648833] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.713.36-0 (2014/02/10) [6.695219] bnx2x :06:00.0: msix capability found [6.719107] bnx2x :06:00.0: part number 0-0-0-0 [7.112390] bnx2x :06:00.0: 63.008 Gb/s available PCIe bandwidth (8 GT/s x8 link) [7.112504] bnx2x :06:00.1: msix capability found [7.112889] bnx2x :06:00.1: part number 0-0-0-0 [7.320779] bnx2x :06:00.1: 63.008 Gb/s available PCIe bandwidth (8 GT/s x8 link) [7.323549] bnx2x :06:00.0 eno49: renamed from eth0 [7.343281] bnx2x :06:00.1 eno50: renamed from eth1 [ 16.321102] bnx2x :06:00.1 eno50: using MSI-X IRQs: sp 130 fp[0] 132 ... fp[7] 139 [ 16.770833] bnx2x :06:00.1 eno50: NIC Link is Up, 1 Mbps full duplex, Flow control: ON - receive & transmit [ 17.136896] bnx2x :06:00.0 eno49: using MSI-X IRQs: sp 120 fp[0] 122 ... fp[7] 129 [ 17.526831] bnx2x :06:00.0 eno49: NIC Link is Up, 1 Mbps full duplex, Flow control: ON - receive & transmit ubuntu@server:$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno49: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 9e:b2:88:1c:ea:40 brd ff:ff:ff:ff:ff:ff 3: eno50: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 9e:b2:88:1c:ea:40 brd ff:ff:ff:ff:ff:ff 4: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 9e:b2:88:1c:ea:40 brd ff:ff:ff:ff:ff:ff inet 10.0.0.68/24 brd 10.0.0.255 scope global bond0 valid_lft forever preferred_lft forever inet6 fe80::9cb2:88ff:fe1c:ea40/64 scope link valid_lft forever preferred_lft forever ubuntu@server:$ sudo lshw -C network *-network:0 description: Ethernet interface product: BCM57840 NetXtreme II 10/20-Gigabit Ethernet vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@:06:00.0 logical name: eno49 version: 11 serial: 9e:b2:88:1c:ea:40 size: 10Gbit/s capacity: 10Gbit/s width: 64 bits clock: 33MHz capabilities: pm vpd msix pciexpress bus_master cap_list rom ethernet physical fibre 1000bt-fd 1bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=bnx2x driverversion=1.713.36-0 storm 7.13.11.0 duplex=full firmware=mbi 7.18.77 bc 7.15.80 latency=0 link=yes multicast=yes port=fibre slave=yes speed=10Gbit/s resources: irq:16 memory:9400-947f memory:9480-94ff memory:9501-9501 memory:92b0-92b7 *-network:1 description: Ethernet interface product: BCM57840 NetXtreme II 10/20-Gigabit Ethernet vendor: Broadcom Inc. and subsidiaries physical id: 0.1 bus info: pci@:06:00.1 logical name: eno50 version: 11 serial: 9e:b2:88:1c:ea:40 size: 10Gbit/s capacity: 10Gbit/s width: 64 bits clock: 33MHz capabilities: pm vpd msix pciexpress bus_master cap_list rom ethernet physical fibre 1000bt-fd 1bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=bnx2x driverversion=1.713.36-0 storm 7.13.11.0 duplex=full firmware=mbi 7.18.77 bc 7.15.80 latency=0 link=yes multicast=yes port=fibre slave=yes speed=10Gbit/s resources: irq:17 memory:9300-937f memory:9380-93ff memory:9500-9500 memory:92b8-92bf *-network description: Ethernet interface physical id: 1 logical name: bond0 serial: 9e:b2:88:1c:ea:40 size: 10Gbit/s cap
[Kernel-packages] [Bug 1942589] Re: Ubuntu 5.4.0-81 stops bnx2x loading hardware
Discussion about a fix for this in upstream: https://lkml.org/lkml/2021/9/13/432 -- 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/1942589 Title: Ubuntu 5.4.0-81 stops bnx2x loading hardware Status in linux package in Ubuntu: Confirmed Bug description: Server: HPE BL460c Gen9 Network: HP FlexFabric 10Gb 2-port 536FLB Adapter (Broadcom/Qlogic Net Extreme II 10/20GBE) Using ubuntu 20.04.2 with linux kernel 5.4.0-80 all functionality worked however upon upgrades via apt to 20.04.3 which uses linux kernel 5.4.0-81, ubuntu is unable to load the drivers for the network device. Below is the output for both kernels when the system is booted. ### # Kernel 5.4.0-80 working # ### ubuntu@server:$ dmesg | grep bnx2x [6.648833] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.713.36-0 (2014/02/10) [6.695219] bnx2x :06:00.0: msix capability found [6.719107] bnx2x :06:00.0: part number 0-0-0-0 [7.112390] bnx2x :06:00.0: 63.008 Gb/s available PCIe bandwidth (8 GT/s x8 link) [7.112504] bnx2x :06:00.1: msix capability found [7.112889] bnx2x :06:00.1: part number 0-0-0-0 [7.320779] bnx2x :06:00.1: 63.008 Gb/s available PCIe bandwidth (8 GT/s x8 link) [7.323549] bnx2x :06:00.0 eno49: renamed from eth0 [7.343281] bnx2x :06:00.1 eno50: renamed from eth1 [ 16.321102] bnx2x :06:00.1 eno50: using MSI-X IRQs: sp 130 fp[0] 132 ... fp[7] 139 [ 16.770833] bnx2x :06:00.1 eno50: NIC Link is Up, 1 Mbps full duplex, Flow control: ON - receive & transmit [ 17.136896] bnx2x :06:00.0 eno49: using MSI-X IRQs: sp 120 fp[0] 122 ... fp[7] 129 [ 17.526831] bnx2x :06:00.0 eno49: NIC Link is Up, 1 Mbps full duplex, Flow control: ON - receive & transmit ubuntu@server:$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno49: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 9e:b2:88:1c:ea:40 brd ff:ff:ff:ff:ff:ff 3: eno50: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 9e:b2:88:1c:ea:40 brd ff:ff:ff:ff:ff:ff 4: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 9e:b2:88:1c:ea:40 brd ff:ff:ff:ff:ff:ff inet 10.0.0.68/24 brd 10.0.0.255 scope global bond0 valid_lft forever preferred_lft forever inet6 fe80::9cb2:88ff:fe1c:ea40/64 scope link valid_lft forever preferred_lft forever ubuntu@server:$ sudo lshw -C network *-network:0 description: Ethernet interface product: BCM57840 NetXtreme II 10/20-Gigabit Ethernet vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@:06:00.0 logical name: eno49 version: 11 serial: 9e:b2:88:1c:ea:40 size: 10Gbit/s capacity: 10Gbit/s width: 64 bits clock: 33MHz capabilities: pm vpd msix pciexpress bus_master cap_list rom ethernet physical fibre 1000bt-fd 1bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=bnx2x driverversion=1.713.36-0 storm 7.13.11.0 duplex=full firmware=mbi 7.18.77 bc 7.15.80 latency=0 link=yes multicast=yes port=fibre slave=yes speed=10Gbit/s resources: irq:16 memory:9400-947f memory:9480-94ff memory:9501-9501 memory:92b0-92b7 *-network:1 description: Ethernet interface product: BCM57840 NetXtreme II 10/20-Gigabit Ethernet vendor: Broadcom Inc. and subsidiaries physical id: 0.1 bus info: pci@:06:00.1 logical name: eno50 version: 11 serial: 9e:b2:88:1c:ea:40 size: 10Gbit/s capacity: 10Gbit/s width: 64 bits clock: 33MHz capabilities: pm vpd msix pciexpress bus_master cap_list rom ethernet physical fibre 1000bt-fd 1bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=bnx2x driverversion=1.713.36-0 storm 7.13.11.0 duplex=full firmware=mbi 7.18.77 bc 7.15.80 latency=0 link=yes multicast=yes port=fibre slave=yes speed=10Gbit/s resources: irq:17 memory:9300-937f memory:9380-93ff memory:9500-9500 memory:92b8-92bf *-network description: Ethernet interface physical id: 1 logical name: bond0 serial: 9e:b2:88:1c:ea:40 size: 10Gbit/s capabilities: ethernet physical
[Kernel-packages] [Bug 1898716] Re: Please trust Canonical Livepatch Service kmod signing key
Mainline kernel-ppa issue is now resolved, thanks! - to unknown fixer. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1898716 Title: Please trust Canonical Livepatch Service kmod signing key Status in linux package in Ubuntu: Fix Committed Status in linux-gcp package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux-gcp source package in Bionic: New Status in linux-kvm source package in Bionic: Confirmed Status in linux source package in Focal: Fix Committed Status in linux-gcp source package in Focal: Confirmed Status in linux-kvm source package in Focal: Confirmed Status in linux source package in Groovy: Fix Committed Status in linux-gcp source package in Groovy: New Status in linux-kvm source package in Groovy: Confirmed Bug description: [Impact] * Currently Canonical Livepatch service is signing kernel modules that are not trusted by the default Ubuntu kernels * to make Canonical Livepatch service out of the box compatible with SecureBoot, please add Canonical Livepatch service key as trusted in the kernel by default * if user wants to distrust the key, they can remove it via mokx, dbx, and we can revoke it by signing revocation with 'canonical master ca'. [Test Case] * Boot kernel * Check the built-in keyring to ensure that Livepatch key is trusted by the built-in keyring Bad: $ sudo keyctl list %:.builtin_trusted_keys 1 key in keyring: 204809401: ---lswrv 0 0 asymmetric: Build time autogenerated kernel key: 4182e0d0113d4a8f460783380c9e618ef1597bf5 Good: $ sudo keyctl list %:.builtin_trusted_keys 2 keys in keyring: 637801673: ---lswrv 0 0 asymmetric: Build time autogenerated kernel key: 52f8757621e8fc6dd500b32c3ead885a3b6d3cbc 1044383508: ---lswrv 0 0 asymmetric: Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969 [Regression Potential] * Kernel keyring size will increase by one key. And thus kernel image will too. [Other Info] * Current livepatch key fingerprints mokutil uses der format $ openssl x509 -inform der -in /snap/canonical-livepatch/current/keys/livepatch-kmod.x509 -noout -fingerprint -sha256 SHA256 Fingerprint=A4:1E:49:06:12:DD:38:56:F9:78:82:E3:66:66:9E:95:15:78:8E:65:68:50:35:46:0F:AC:59:72:4A:5B:92:FA kernel use pem format $ openssl x509 -inform pem -in debian/canonical-livepatch.pem -noout -fingerprint -sha256 SHA256 Fingerprint=A4:1E:49:06:12:DD:38:56:F9:78:82:E3:66:66:9E:95:15:78:8E:65:68:50:35:46:0F:AC:59:72:4A:5B:92:FA [Target kernels] bionic and up, across the board, but maybe excluding fips kernels?! [Patch] https://lists.ubuntu.com/archives/kernel-team/2020-October/113929.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898716/+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
[Kernel-packages] [Bug 1898716] Re: Please trust Canonical Livepatch Service kmod signing key
Not sure if this is the right place to report this, but these changes seem to cause automated mainline kernel builds to fail. e.g. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11.1/amd64/log shows make[3]: *** No rule to make target 'debian/canonical-certs.pem', needed by 'certs/x509_certificate_list'. Stop. possibly because changes from this ticket were only partially migrated there e.g. in: https://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git /mainline- crack/commit/?h=cod/mainline/v5.11.1&id=4508c61e1cf702e70308f1c1fbb0f26a45d0b853 which updated the configs, but not the rule for debian/canonical- certs.pem in debian/rules. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1898716 Title: Please trust Canonical Livepatch Service kmod signing key Status in linux package in Ubuntu: Fix Committed Status in linux-gcp package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux-gcp source package in Bionic: New Status in linux-kvm source package in Bionic: Confirmed Status in linux source package in Focal: Fix Committed Status in linux-gcp source package in Focal: Confirmed Status in linux-kvm source package in Focal: Confirmed Status in linux source package in Groovy: Fix Committed Status in linux-gcp source package in Groovy: New Status in linux-kvm source package in Groovy: Confirmed Bug description: [Impact] * Currently Canonical Livepatch service is signing kernel modules that are not trusted by the default Ubuntu kernels * to make Canonical Livepatch service out of the box compatible with SecureBoot, please add Canonical Livepatch service key as trusted in the kernel by default * if user wants to distrust the key, they can remove it via mokx, dbx, and we can revoke it by signing revocation with 'canonical master ca'. [Test Case] * Boot kernel * Check the built-in keyring to ensure that Livepatch key is trusted by the built-in keyring Bad: $ sudo keyctl list %:.builtin_trusted_keys 1 key in keyring: 204809401: ---lswrv 0 0 asymmetric: Build time autogenerated kernel key: 4182e0d0113d4a8f460783380c9e618ef1597bf5 Good: $ sudo keyctl list %:.builtin_trusted_keys 2 keys in keyring: 637801673: ---lswrv 0 0 asymmetric: Build time autogenerated kernel key: 52f8757621e8fc6dd500b32c3ead885a3b6d3cbc 1044383508: ---lswrv 0 0 asymmetric: Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969 [Regression Potential] * Kernel keyring size will increase by one key. And thus kernel image will too. [Other Info] * Current livepatch key fingerprints mokutil uses der format $ openssl x509 -inform der -in /snap/canonical-livepatch/current/keys/livepatch-kmod.x509 -noout -fingerprint -sha256 SHA256 Fingerprint=A4:1E:49:06:12:DD:38:56:F9:78:82:E3:66:66:9E:95:15:78:8E:65:68:50:35:46:0F:AC:59:72:4A:5B:92:FA kernel use pem format $ openssl x509 -inform pem -in debian/canonical-livepatch.pem -noout -fingerprint -sha256 SHA256 Fingerprint=A4:1E:49:06:12:DD:38:56:F9:78:82:E3:66:66:9E:95:15:78:8E:65:68:50:35:46:0F:AC:59:72:4A:5B:92:FA [Target kernels] bionic and up, across the board, but maybe excluding fips kernels?! [Patch] https://lists.ubuntu.com/archives/kernel-team/2020-October/113929.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898716/+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
