[Kernel-packages] [Bug 1804183] Re: netronome firmware symlinks are overwritten by package upgrade
Hi, Netronome would like to propose the following fix, which is to mark the symlinks as conffiles. This produces a debian package which does not overwrite the symlinks when installed. ** Patch added: "0001-UBUNTU-Mark-netronome-firmware-symlinks-as-config-fi.patch" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1804183/+attachment/5270366/+files/0001-UBUNTU-Mark-netronome-firmware-symlinks-as-config-fi.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1804183 Title: netronome firmware symlinks are overwritten by package upgrade Status in linux-firmware package in Ubuntu: New Bug description: The linux-firmware package includes symlinks to installed Netronome firmware files. These links may be updated by a user but are overwritten when the linux-firmware package is upgraded whereas the desired behaviour is to leave existing symlinks unmodified. # apt install linux-firmware Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: grub-pc-bin Use 'apt autoremove' to remove it. The following NEW packages will be installed: linux-firmware 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 64.6 MB of archives. After this operation, 278 MB of additional disk space will be used. Get:1 http://lon1.mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 linux-firmware all 1.173.1 [64.6 MB] Fetched 64.6 MB in 1s (43.8 MB/s) Selecting previously unselected package linux-firmware. (Reading database ... 59988 files and directories currently installed.) Preparing to unpack .../linux-firmware_1.173.1_all.deb ... Unpacking linux-firmware (1.173.1) ... Setting up linux-firmware (1.173.1) ... update-initramfs: Generating /boot/initrd.img-4.15.0-38-generic # cd /lib/firmware/netronome/ # ls -l total 8 drwxr-xr-x 2 root root 4096 Nov 20 09:07 flower drwxr-xr-x 2 root root 4096 Nov 20 09:07 nic lrwxrwxrwx 1 root root 31 May 18 2018 nic_AMDA0081-0001_1x40.nffw -> nic/nic_AMDA0081-0001_1x40.nffw lrwxrwxrwx 1 root root 31 May 18 2018 nic_AMDA0081-0001_4x10.nffw -> nic/nic_AMDA0081-0001_4x10.nffw lrwxrwxrwx 1 root root 31 May 18 2018 nic_AMDA0096-0001_2x10.nffw -> nic/nic_AMDA0096-0001_2x10.nffw lrwxrwxrwx 1 root root 31 May 18 2018 nic_AMDA0097-0001_2x40.nffw -> nic/nic_AMDA0097-0001_2x40.nffw lrwxrwxrwx 1 root root 36 May 18 2018 nic_AMDA0097-0001_4x10_1x40.nffw -> nic/nic_AMDA0097-0001_4x10_1x40.nffw lrwxrwxrwx 1 root root 31 May 18 2018 nic_AMDA0097-0001_8x10.nffw -> nic/nic_AMDA0097-0001_8x10.nffw lrwxrwxrwx 1 root root 36 May 18 2018 nic_AMDA0099-0001_1x10_1x25.nffw -> nic/nic_AMDA0099-0001_1x10_1x25.nffw lrwxrwxrwx 1 root root 31 May 18 2018 nic_AMDA0099-0001_2x10.nffw -> nic/nic_AMDA0099-0001_2x10.nffw lrwxrwxrwx 1 root root 31 May 18 2018 nic_AMDA0099-0001_2x25.nffw -> nic/nic_AMDA0099-0001_2x25.nffw # for i in $(find flower/ -type l); do ln -sf $i $(basename $i); done # ls -l total 8 drwxr-xr-x 2 root root 4096 Nov 20 09:07 flower drwxr-xr-x 2 root root 4096 Nov 20 09:07 nic lrwxrwxrwx 1 root root 34 Nov 20 09:09 nic_AMDA0081-0001_1x40.nffw -> flower/nic_AMDA0081-0001_1x40.nffw lrwxrwxrwx 1 root root 34 Nov 20 09:09 nic_AMDA0081-0001_4x10.nffw -> flower/nic_AMDA0081-0001_4x10.nffw lrwxrwxrwx 1 root root 34 Nov 20 09:09 nic_AMDA0096-0001_2x10.nffw -> flower/nic_AMDA0096-0001_2x10.nffw lrwxrwxrwx 1 root root 34 Nov 20 09:09 nic_AMDA0097-0001_2x40.nffw -> flower/nic_AMDA0097-0001_2x40.nffw lrwxrwxrwx 1 root root 39 Nov 20 09:09 nic_AMDA0097-0001_4x10_1x40.nffw -> flower/nic_AMDA0097-0001_4x10_1x40.nffw lrwxrwxrwx 1 root root 34 Nov 20 09:09 nic_AMDA0097-0001_8x10.nffw -> flower/nic_AMDA0097-0001_8x10.nffw lrwxrwxrwx 1 root root 36 May 18 2018 nic_AMDA0099-0001_1x10_1x25.nffw -> nic/nic_AMDA0099-0001_1x10_1x25.nffw lrwxrwxrwx 1 root root 34 Nov 20 09:09 nic_AMDA0099-0001_2x10.nffw -> flower/nic_AMDA0099-0001_2x10.nffw lrwxrwxrwx 1 root root 34 Nov 20 09:09 nic_AMDA0099-0001_2x25.nffw -> flower/nic_AMDA0099-0001_2x25.nffw # apt update ... # apt install linux-firmware Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: grub-pc-bin Use 'apt autoremove' to remove it. The following packages will be upgraded: linux-firmware 1 upgraded, 0 newly installed, 0 to remove and 49 not upgraded. Need to get 64.6 MB of archives. After this operation, 30.7 kB of additional disk space will be used. Get:1 http://lon1.mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 linux-firmware all 1.173.2 [64.6 MB] Fetched
[Kernel-packages] [Bug 1804183] [NEW] netronome firmware symlinks are overwritten by package upgrade
Public bug reported: The linux-firmware package includes symlinks to installed Netronome firmware files. These links may be updated by a user but are overwritten when the linux-firmware package is upgraded whereas the desired behaviour is to leave existing symlinks unmodified. # apt install linux-firmware Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: grub-pc-bin Use 'apt autoremove' to remove it. The following NEW packages will be installed: linux-firmware 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 64.6 MB of archives. After this operation, 278 MB of additional disk space will be used. Get:1 http://lon1.mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 linux-firmware all 1.173.1 [64.6 MB] Fetched 64.6 MB in 1s (43.8 MB/s) Selecting previously unselected package linux-firmware. (Reading database ... 59988 files and directories currently installed.) Preparing to unpack .../linux-firmware_1.173.1_all.deb ... Unpacking linux-firmware (1.173.1) ... Setting up linux-firmware (1.173.1) ... update-initramfs: Generating /boot/initrd.img-4.15.0-38-generic # cd /lib/firmware/netronome/ # ls -l total 8 drwxr-xr-x 2 root root 4096 Nov 20 09:07 flower drwxr-xr-x 2 root root 4096 Nov 20 09:07 nic lrwxrwxrwx 1 root root 31 May 18 2018 nic_AMDA0081-0001_1x40.nffw -> nic/nic_AMDA0081-0001_1x40.nffw lrwxrwxrwx 1 root root 31 May 18 2018 nic_AMDA0081-0001_4x10.nffw -> nic/nic_AMDA0081-0001_4x10.nffw lrwxrwxrwx 1 root root 31 May 18 2018 nic_AMDA0096-0001_2x10.nffw -> nic/nic_AMDA0096-0001_2x10.nffw lrwxrwxrwx 1 root root 31 May 18 2018 nic_AMDA0097-0001_2x40.nffw -> nic/nic_AMDA0097-0001_2x40.nffw lrwxrwxrwx 1 root root 36 May 18 2018 nic_AMDA0097-0001_4x10_1x40.nffw -> nic/nic_AMDA0097-0001_4x10_1x40.nffw lrwxrwxrwx 1 root root 31 May 18 2018 nic_AMDA0097-0001_8x10.nffw -> nic/nic_AMDA0097-0001_8x10.nffw lrwxrwxrwx 1 root root 36 May 18 2018 nic_AMDA0099-0001_1x10_1x25.nffw -> nic/nic_AMDA0099-0001_1x10_1x25.nffw lrwxrwxrwx 1 root root 31 May 18 2018 nic_AMDA0099-0001_2x10.nffw -> nic/nic_AMDA0099-0001_2x10.nffw lrwxrwxrwx 1 root root 31 May 18 2018 nic_AMDA0099-0001_2x25.nffw -> nic/nic_AMDA0099-0001_2x25.nffw # for i in $(find flower/ -type l); do ln -sf $i $(basename $i); done # ls -l total 8 drwxr-xr-x 2 root root 4096 Nov 20 09:07 flower drwxr-xr-x 2 root root 4096 Nov 20 09:07 nic lrwxrwxrwx 1 root root 34 Nov 20 09:09 nic_AMDA0081-0001_1x40.nffw -> flower/nic_AMDA0081-0001_1x40.nffw lrwxrwxrwx 1 root root 34 Nov 20 09:09 nic_AMDA0081-0001_4x10.nffw -> flower/nic_AMDA0081-0001_4x10.nffw lrwxrwxrwx 1 root root 34 Nov 20 09:09 nic_AMDA0096-0001_2x10.nffw -> flower/nic_AMDA0096-0001_2x10.nffw lrwxrwxrwx 1 root root 34 Nov 20 09:09 nic_AMDA0097-0001_2x40.nffw -> flower/nic_AMDA0097-0001_2x40.nffw lrwxrwxrwx 1 root root 39 Nov 20 09:09 nic_AMDA0097-0001_4x10_1x40.nffw -> flower/nic_AMDA0097-0001_4x10_1x40.nffw lrwxrwxrwx 1 root root 34 Nov 20 09:09 nic_AMDA0097-0001_8x10.nffw -> flower/nic_AMDA0097-0001_8x10.nffw lrwxrwxrwx 1 root root 36 May 18 2018 nic_AMDA0099-0001_1x10_1x25.nffw -> nic/nic_AMDA0099-0001_1x10_1x25.nffw lrwxrwxrwx 1 root root 34 Nov 20 09:09 nic_AMDA0099-0001_2x10.nffw -> flower/nic_AMDA0099-0001_2x10.nffw lrwxrwxrwx 1 root root 34 Nov 20 09:09 nic_AMDA0099-0001_2x25.nffw -> flower/nic_AMDA0099-0001_2x25.nffw # apt update ... # apt install linux-firmware Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: grub-pc-bin Use 'apt autoremove' to remove it. The following packages will be upgraded: linux-firmware 1 upgraded, 0 newly installed, 0 to remove and 49 not upgraded. Need to get 64.6 MB of archives. After this operation, 30.7 kB of additional disk space will be used. Get:1 http://lon1.mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 linux-firmware all 1.173.2 [64.6 MB] Fetched 64.6 MB in 1s (55.1 MB/s) (Reading database ... 61821 files and directories currently installed.) Preparing to unpack .../linux-firmware_1.173.2_all.deb ... Unpacking linux-firmware (1.173.2) over (1.173.1) ... Setting up linux-firmware (1.173.2) ... update-initramfs: Generating /boot/initrd.img-4.15.0-38-generic root@ubuntu-s-1vcpu-1gb-ams3-01:/lib/firmware/netronome# ls -l total 8 drwxr-xr-x 2 root root 4096 Nov 20 09:13 flower drwxr-xr-x 2 root root 4096 Nov 20 09:13 nic lrwxrwxrwx 1 root root 31 Nov 6 14:30 nic_AMDA0081-0001_1x40.nffw -> nic/nic_AMDA0081-0001_1x40.nffw lrwxrwxrwx 1 root root 31 Nov 6 14:30 nic_AMDA0081-0001_4x10.nffw -> nic/nic_AMDA0081-0001_4x10.nffw lrwxrwxrwx 1 root root 31 Nov 6 14:30 nic_AMDA0096-0001_2x10.nffw -> nic/nic_AMDA0096-0001_2x10.nffw lrwxrwxrwx 1 root root 31 Nov 6 14:30
[Kernel-packages] [Bug 1765379] Re: nfp: flower: fixes for cmesg processing timeouts
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Confirmed
** Changed in: linux (Ubuntu)
Status: Triaged => Confirmed
--
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/1765379
Title:
nfp: flower: fixes for cmesg processing timeouts
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
This is a backport request from Netronome for Ubuntu 18.04 LTS
This patch-set improves control message handling making it more robust with
respect to timeouts caused by excessively large number of messages
queued for processing in a workqueue.
The upstream commits, accepted for v4.16, are:
cf2cbadc20f5 ("nfp: flower: split and limit cmsg skb lists")
0b1a989ef5a7 ("nfp: flower: move route ack control messages out of the
workqueue")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765379/+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 1765373] Re: nfp: flower: fixes for cmesg processing timeouts
Hi,
I apologise that I am a little unsure of the process here.
This is a rather severe bug from a Netronome point of view which has now been
fixed upstream.
Is there a procedure available for backports to be included in an updated
Bionic kernel?
--
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/1765373
Title:
nfp: flower: fixes for cmesg processing timeouts
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
This is a backport request from Netronome for Ubuntu 18.04 LTS
This patch-set improves MTU handling for flower offload on Netronome
SmartNICs.
The max MTU is correctly capped and physical port MTU is communicated to the
FW
(and indirectly HW). This prevents the driver from incorrectly reporting a
larger
MTU than the HW is configured to handle.
The upstream commits, accepted for v4.17, are:
29a5dcae2790 ("nfp: flower: offload phys port MTU change")
167cebeffadd ("nfp: modify app MTU setting callbacks")
There are also a dependencies on:
ccbdc596f4f6 ("nfp: bpf: don't allow changing MTU above BPF offload limit
when active")
b57b62139e53 ("nfp: flower: read extra feature support from fw")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765373/+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 1768526] Re: Include nfp driver in linux-modules
Hi, I'm wondering if there is anything Netronome can do to assist with regards to this bug. Its very important to us. -- 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/1768526 Title: Include nfp driver in linux-modules Status in linux package in Ubuntu: Triaged Bug description: SRU Justification: -- [Impact] * Currently the driver for Netronome Agilio SmartNICs, nfp.ko, is included in linux-moudles-extra. An implication of this is that on minimal installs, where the linux-modules but not linux-modules-extra packages are available, the nfp.ko module cannot be installed. In particular this means the driver for any VFs of Netronome Agilio SmartNICs which have been made available to guests using PCI pass-through cannot be used by those guests if they have installed using Canonical cloud images, a likely scenario. In contrast the driver for the i40e is provided in the linux-modules package and thus guests can access their VFs in the scenario described above. Thus we do not believe it is unreasonable to request that nfp.ko be included in linux-modules rather than linux-modules-extras. And we believe that this warrants SRU inclusion as it is the difference between users-of guests being able to use Netronome Agilio SmartNICs and not be able to use them. This is a packaging update request and included no request to change the kernel source code, thus no backports are requred. [Test Case] * Install system using Canonical cloud images * Observer that /lib/modules/*/kernel/drivers/net/ethernet/netronome/nfp/nfp.ko is missing; * If an Netronome Agilio SmartNIC device is present, via PCI pass-through or otherwise, that the nfp driver is not loaded and no netdevs are present for the Netronome Agilio SmartNIC. [Regression Potential] * Any bugs present in the nfp.ko will now be exposted to guests. However as the same nfp.ko driver binary is already included in and available on installs that have access to linux-modules-extra, this does not seem an unreasonable burden. [Other Info] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768526/+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 1768526] [NEW] Include nfp driver in linux-modules
Public bug reported: SRU Justification: -- [Impact] * Currently the driver for Netronome Agilio SmartNICs, nfp.ko, is included in linux-moudles-extra. An implication of this is that on minimal installs, where the linux-modules but not linux-modules-extra packages are available, the nfp.ko module cannot be installed. In particular this means the driver for any VFs of Netronome Agilio SmartNICs which have been made available to guests using PCI pass-through cannot be used by those guests if they have installed using Canonical cloud images, a likely scenario. In contrast the driver for the i40e is provided in the linux-modules package and thus guests can access their VFs in the scenario described above. Thus we do not believe it is unreasonable to request that nfp.ko be included in linux-modules rather than linux-modules-extras. And we believe that this warrants SRU inclusion as it is the difference between users-of guests being able to use Netronome Agilio SmartNICs and not be able to use them. This is a packaging update request and included no request to change the kernel source code, thus no backports are requred. [Test Case] * Install system using Canonical cloud images * Observer that /lib/modules/*/kernel/drivers/net/ethernet/netronome/nfp/nfp.ko is missing; * If an Netronome Agilio SmartNIC device is present, via PCI pass-through or otherwise, that the nfp driver is not loaded and no netdevs are present for the Netronome Agilio SmartNIC. [Regression Potential] * Any bugs present in the nfp.ko will now be exposted to guests. However as the same nfp.ko driver binary is already included in and available on installs that have access to linux-modules-extra, this does not seem an unreasonable burden. [Other Info] * None ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Description changed: + SRU Justification: + -- + [Impact] - * Currently the driver for Netronome Agilio SmartNICs, nfp.ko, is included in linux-moudles-extra. -An implication of this is that on minimal installs, where the linux-modules but not linux-modules-extra -packages are available, the nfp.ko module cannot be installed. In particular this means the driver for -any VFs of Netronome Agilio SmartNICs which have been made available to guests using PCI pass-through -cannot be used by those guests if they have installed using Canonical cloud images, a likely scenario. + * Currently the driver for Netronome Agilio SmartNICs, nfp.ko, is included in linux-moudles-extra. + An implication of this is that on minimal installs, where the linux-modules but not linux-modules-extra + packages are available, the nfp.ko module cannot be installed. In particular this means the driver for + any VFs of Netronome Agilio SmartNICs which have been made available to guests using PCI pass-through + cannot be used by those guests if they have installed using Canonical cloud images, a likely scenario. -In contrast the driver for the i40e is provided in the linux-modules package and thus guests can -access their VFs in the scenario described above. + In contrast the driver for the i40e is provided in the linux-modules package and thus guests can + access their VFs in the scenario described above. -Thus we do not believe it is unreasonable to request that nfp.ko be included in linux-modules rather -than linux-modules-extras. And we believe that this warrants SRU inclusion as it is the difference between -users-of guests being able to use Netronome Agilio SmartNICs and not be able to use them. + Thus we do not believe it is unreasonable to request that nfp.ko be included in linux-modules rather + than linux-modules-extras. And we believe that this warrants SRU inclusion as it is the difference between + users-of guests being able to use Netronome Agilio SmartNICs and not be able to use them. -This is a packaging update request and included no request to change the kernel source code, -thus no backports are requred. + This is a packaging update request and included no request to change the kernel source code, + thus no backports are requred. [Test Case] - * Install system using Canonical cloud images + * Install system using Canonical cloud images - * Observer that /lib/modules/*/kernel/drivers/net/ethernet/netronome/nfp/nfp.ko is missing; - - * If an Netronome Agilio SmartNIC device is present, via PCI pass-through or otherwise, -that the nfp driver is not loaded and no netdevs are present for the Netronome Agilio SmartNIC. + * Observer that + /lib/modules/*/kernel/drivers/net/ethernet/netronome/nfp/nfp.ko is + missing; + + * If an Netronome Agilio SmartNIC device is present, via PCI pass-through or otherwise, + that the nfp driver is not loaded and no netdevs are present for the
[Kernel-packages] [Bug 1765373] Re: nfp: flower: fixes for cmesg processing timeouts
Patch 2/4 of reference backport made against Ubuntu-4.15.0-15.16 tag of
git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
** Patch added: "0002-nfp-modify-app-MTU-setting-callbacks.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765373/+attachment/5122517/+files/0002-nfp-modify-app-MTU-setting-callbacks.patch
--
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/1765373
Title:
nfp: flower: fixes for cmesg processing timeouts
Status in linux package in Ubuntu:
Incomplete
Bug description:
This is a backport request from Netronome for Ubuntu 18.04 LTS
This patch-set improves MTU handling for flower offload on Netronome
SmartNICs.
The max MTU is correctly capped and physical port MTU is communicated to the
FW
(and indirectly HW). This prevents the driver from incorrectly reporting a
larger
MTU than the HW is configured to handle.
The upstream commits, accepted for v4.17, are:
29a5dcae2790 ("nfp: flower: offload phys port MTU change")
167cebeffadd ("nfp: modify app MTU setting callbacks")
There are also a dependencies on:
ccbdc596f4f6 ("nfp: bpf: don't allow changing MTU above BPF offload limit
when active")
b57b62139e53 ("nfp: flower: read extra feature support from fw")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765373/+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 1765379] [NEW] nfp: flower: fixes for cmesg processing timeouts
Public bug reported:
This is a backport request from Netronome for Ubuntu 18.04 LTS
This patch-set improves control message handling making it more robust with
respect to timeouts caused by excessively large number of messages
queued for processing in a workqueue.
The upstream commits, accepted for v4.16, are:
cf2cbadc20f5 ("nfp: flower: split and limit cmsg skb lists")
0b1a989ef5a7 ("nfp: flower: move route ack control messages out of the
workqueue")
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1765379
Title:
nfp: flower: fixes for cmesg processing timeouts
Status in linux package in Ubuntu:
New
Bug description:
This is a backport request from Netronome for Ubuntu 18.04 LTS
This patch-set improves control message handling making it more robust with
respect to timeouts caused by excessively large number of messages
queued for processing in a workqueue.
The upstream commits, accepted for v4.16, are:
cf2cbadc20f5 ("nfp: flower: split and limit cmsg skb lists")
0b1a989ef5a7 ("nfp: flower: move route ack control messages out of the
workqueue")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765379/+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 1765379] Re: nfp: flower: fixes for cmesg processing timeouts
Patch 1/2 of reference backport made against Ubuntu-4.15.0-15.16 tag of
git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
** Patch added: "0001-nfp-flower-split-and-limit-cmsg-skb-lists.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765379/+attachment/5122528/+files/0001-nfp-flower-split-and-limit-cmsg-skb-lists.patch
--
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/1765379
Title:
nfp: flower: fixes for cmesg processing timeouts
Status in linux package in Ubuntu:
New
Bug description:
This is a backport request from Netronome for Ubuntu 18.04 LTS
This patch-set improves control message handling making it more robust with
respect to timeouts caused by excessively large number of messages
queued for processing in a workqueue.
The upstream commits, accepted for v4.16, are:
cf2cbadc20f5 ("nfp: flower: split and limit cmsg skb lists")
0b1a989ef5a7 ("nfp: flower: move route ack control messages out of the
workqueue")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765379/+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 1765379] Re: nfp: flower: fixes for cmesg processing timeouts
Patch 2/2 of reference backport made against Ubuntu-4.15.0-15.16 tag of
git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
** Patch added:
"0002-nfp-flower-move-route-ack-control-messages-out-of-th.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765379/+attachment/5122529/+files/0002-nfp-flower-move-route-ack-control-messages-out-of-th.patch
--
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/1765379
Title:
nfp: flower: fixes for cmesg processing timeouts
Status in linux package in Ubuntu:
New
Bug description:
This is a backport request from Netronome for Ubuntu 18.04 LTS
This patch-set improves control message handling making it more robust with
respect to timeouts caused by excessively large number of messages
queued for processing in a workqueue.
The upstream commits, accepted for v4.16, are:
cf2cbadc20f5 ("nfp: flower: split and limit cmsg skb lists")
0b1a989ef5a7 ("nfp: flower: move route ack control messages out of the
workqueue")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765379/+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 1765373] [NEW] nfp: flower: fixes for cmesg processing timeouts
Public bug reported:
This is a backport request from Netronome for Ubuntu 18.04 LTS
This patch-set improves MTU handling for flower offload on Netronome SmartNICs.
The max MTU is correctly capped and physical port MTU is communicated to the FW
(and indirectly HW). This prevents the driver from incorrectly reporting a
larger
MTU than the HW is configured to handle.
The upstream commits, accepted for v4.17, are:
29a5dcae2790 ("nfp: flower: offload phys port MTU change")
167cebeffadd ("nfp: modify app MTU setting callbacks")
There are also a dependencies on:
ccbdc596f4f6 ("nfp: bpf: don't allow changing MTU above BPF offload limit when
active")
b57b62139e53 ("nfp: flower: read extra feature support from fw")
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
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/1765373
Title:
nfp: flower: fixes for cmesg processing timeouts
Status in linux package in Ubuntu:
Incomplete
Bug description:
This is a backport request from Netronome for Ubuntu 18.04 LTS
This patch-set improves MTU handling for flower offload on Netronome
SmartNICs.
The max MTU is correctly capped and physical port MTU is communicated to the
FW
(and indirectly HW). This prevents the driver from incorrectly reporting a
larger
MTU than the HW is configured to handle.
The upstream commits, accepted for v4.17, are:
29a5dcae2790 ("nfp: flower: offload phys port MTU change")
167cebeffadd ("nfp: modify app MTU setting callbacks")
There are also a dependencies on:
ccbdc596f4f6 ("nfp: bpf: don't allow changing MTU above BPF offload limit
when active")
b57b62139e53 ("nfp: flower: read extra feature support from fw")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765373/+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 1765373] Re: nfp: flower: fixes for cmesg processing timeouts
Patch 3/4 of reference backport made against Ubuntu-4.15.0-15.16 tag of
git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
** Patch added: "0003-nfp-flower-read-extra-feature-support-from-fw.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765373/+attachment/5122518/+files/0003-nfp-flower-read-extra-feature-support-from-fw.patch
--
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/1765373
Title:
nfp: flower: fixes for cmesg processing timeouts
Status in linux package in Ubuntu:
Incomplete
Bug description:
This is a backport request from Netronome for Ubuntu 18.04 LTS
This patch-set improves MTU handling for flower offload on Netronome
SmartNICs.
The max MTU is correctly capped and physical port MTU is communicated to the
FW
(and indirectly HW). This prevents the driver from incorrectly reporting a
larger
MTU than the HW is configured to handle.
The upstream commits, accepted for v4.17, are:
29a5dcae2790 ("nfp: flower: offload phys port MTU change")
167cebeffadd ("nfp: modify app MTU setting callbacks")
There are also a dependencies on:
ccbdc596f4f6 ("nfp: bpf: don't allow changing MTU above BPF offload limit
when active")
b57b62139e53 ("nfp: flower: read extra feature support from fw")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765373/+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 1765373] Re: nfp: flower: fixes for cmesg processing timeouts
Patch 4/4 of reference backport made against Ubuntu-4.15.0-15.16 tag of
git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
** Patch added: "0004-nfp-flower-offload-phys-port-MTU-change.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765373/+attachment/5122519/+files/0004-nfp-flower-offload-phys-port-MTU-change.patch
--
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/1765373
Title:
nfp: flower: fixes for cmesg processing timeouts
Status in linux package in Ubuntu:
Incomplete
Bug description:
This is a backport request from Netronome for Ubuntu 18.04 LTS
This patch-set improves MTU handling for flower offload on Netronome
SmartNICs.
The max MTU is correctly capped and physical port MTU is communicated to the
FW
(and indirectly HW). This prevents the driver from incorrectly reporting a
larger
MTU than the HW is configured to handle.
The upstream commits, accepted for v4.17, are:
29a5dcae2790 ("nfp: flower: offload phys port MTU change")
167cebeffadd ("nfp: modify app MTU setting callbacks")
There are also a dependencies on:
ccbdc596f4f6 ("nfp: bpf: don't allow changing MTU above BPF offload limit
when active")
b57b62139e53 ("nfp: flower: read extra feature support from fw")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765373/+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 1765373] Re: nfp: flower: fixes for cmesg processing timeouts
Patch 1/4 of reference backport made against Ubuntu-4.15.0-15.16 tag of
git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
** Patch added:
"0001-nfp-bpf-don-t-allow-changing-MTU-above-BPF-offload-l.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765373/+attachment/5122516/+files/0001-nfp-bpf-don-t-allow-changing-MTU-above-BPF-offload-l.patch
--
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/1765373
Title:
nfp: flower: fixes for cmesg processing timeouts
Status in linux package in Ubuntu:
Incomplete
Bug description:
This is a backport request from Netronome for Ubuntu 18.04 LTS
This patch-set improves MTU handling for flower offload on Netronome
SmartNICs.
The max MTU is correctly capped and physical port MTU is communicated to the
FW
(and indirectly HW). This prevents the driver from incorrectly reporting a
larger
MTU than the HW is configured to handle.
The upstream commits, accepted for v4.17, are:
29a5dcae2790 ("nfp: flower: offload phys port MTU change")
167cebeffadd ("nfp: modify app MTU setting callbacks")
There are also a dependencies on:
ccbdc596f4f6 ("nfp: bpf: don't allow changing MTU above BPF offload limit
when active")
b57b62139e53 ("nfp: flower: read extra feature support from fw")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765373/+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 1760152] Re: nfp: request backport of ethtool flashing
Apologies for the slow response, I was on holidays last week.
I will get the kernel tested and log the results here.
--
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/1760152
Title:
nfp: request backport of ethtool flashing
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
Backport recently upstreamed changes to the nfp driver to allow flash updates
to be written to Netronome SmartNICs using ethtool.
f.e.
# ethtool -f netdev_name flash-nic.bin
This feature is not currently present in the Bionic kernel and the above
command results in the following error:
Error return + "Flashing failed: Operation not supported\n"
This feature is implemented by the following upstream commits.
7a7415659144 ("nfp: implement firmware flashing")
87a23801e502 ("nfp: extend NSP infrastructure for configurable timeouts")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760152/+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 1760152] [NEW] nfp: request backport of ethtool flashing
Public bug reported:
Backport recently upstreamed changes to the nfp driver to allow flash updates
to be written to Netronome SmartNICs using ethtool.
f.e.
# ethtool -f netdev_name flash-nic.bin
This feature is not currently present in the Bionic kernel and the above
command results in the following error:
Error return + "Flashing failed: Operation not supported\n"
This feature is implemented by the following upstream commits.
7a7415659144 ("nfp: implement firmware flashing")
87a23801e502 ("nfp: extend NSP infrastructure for configurable timeouts")
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1760152
Title:
nfp: request backport of ethtool flashing
Status in linux package in Ubuntu:
New
Bug description:
Backport recently upstreamed changes to the nfp driver to allow flash updates
to be written to Netronome SmartNICs using ethtool.
f.e.
# ethtool -f netdev_name flash-nic.bin
This feature is not currently present in the Bionic kernel and the above
command results in the following error:
Error return + "Flashing failed: Operation not supported\n"
This feature is implemented by the following upstream commits.
7a7415659144 ("nfp: implement firmware flashing")
87a23801e502 ("nfp: extend NSP infrastructure for configurable timeouts")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760152/+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 1752061] Re: nfp: prioritize stats updates
Hi,
we have successfully tested the new kernel image and the problem in
question no longer manifests.
--
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/1752061
Title:
nfp: prioritize stats updates
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
This is a backport request from Netronome for Ubuntu 18.04 LTS.
Description: Previously it was possible to interrupt processing stats updates
because they were handled in a work queue. Interrupting the stats updates could
lead to a situation where we backup the control message queue. This patch
moves the stats update processing out of the work queue to be processed as
soon as hardware sends a request.
The following fix for the above has been accepted into upstream for
v4.16. This ticket requests backporting it to Ubuntu 18.04 LTS.
01c15e93a78c ("nfp: flower: prioritize stats updates")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752061/+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 1752828] [NEW] nfp: fix disabling on hw-tc-offload in flower
Public bug reported: This is a backport request from Netronome for Ubuntu 18.04 LTS This patchset corrects the following behaviour: 1. Add TC filter to hardware while hw-tc-offload is on 2. Switch hw-tc-offload to off using ethtool 3. Filters added to hardware in step 1 are still active but can no longer be removed. The upstream solution to this problem is to prohibit switching hw-tc- offload to off when filters are present in hardware. The upstream commits, accepted for v4.16, are: d692403e5cf8 (“nfp: forbid disabling hw-tc-offload on representors while offload active”) 0b9de4ca853b (“nfp: don't advertise hw-tc-offload on non-port netdevs”) e3ac6c0737e2 (“nfp: bpf: require ETH table”) ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1752828 Title: nfp: fix disabling on hw-tc-offload in flower Status in linux package in Ubuntu: New Bug description: This is a backport request from Netronome for Ubuntu 18.04 LTS This patchset corrects the following behaviour: 1. Add TC filter to hardware while hw-tc-offload is on 2. Switch hw-tc-offload to off using ethtool 3. Filters added to hardware in step 1 are still active but can no longer be removed. The upstream solution to this problem is to prohibit switching hw-tc- offload to off when filters are present in hardware. The upstream commits, accepted for v4.16, are: d692403e5cf8 (“nfp: forbid disabling hw-tc-offload on representors while offload active”) 0b9de4ca853b (“nfp: don't advertise hw-tc-offload on non-port netdevs”) e3ac6c0737e2 (“nfp: bpf: require ETH table”) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752828/+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 1752818] [NEW] nfp: read ME frequency from vNIC ctrl memory
Public bug reported: This is a backport request from Netronome. The following kernel changes were recently upstreamed to correct assumptions about ME clock speed which may not be correct for a given Netronome SmartNIC. There is also a firmware portion of this fix which is pending release. It seems worthwhile updating the kernel so that it will behave correctly once that portion of the fix becomes available. The kernel commits are: 1d8ef0c07664 (“nfp: fix TLV offset calculation”) ce991ab6662a (“nfp: read ME frequency from vNIC ctrl memory”) 73a0329b057e (“nfp: add TLV capabilities to the BAR”) ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1752818 Title: nfp: read ME frequency from vNIC ctrl memory Status in linux package in Ubuntu: New Bug description: This is a backport request from Netronome. The following kernel changes were recently upstreamed to correct assumptions about ME clock speed which may not be correct for a given Netronome SmartNIC. There is also a firmware portion of this fix which is pending release. It seems worthwhile updating the kernel so that it will behave correctly once that portion of the fix becomes available. The kernel commits are: 1d8ef0c07664 (“nfp: fix TLV offset calculation”) ce991ab6662a (“nfp: read ME frequency from vNIC ctrl memory”) 73a0329b057e (“nfp: add TLV capabilities to the BAR”) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752818/+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 1752061] Re: nfp: prioritize stats updates
Thanks Joseph, we will test this.
--
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/1752061
Title:
nfp: prioritize stats updates
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
This is a backport request from Netronome for Ubuntu 18.04 LTS.
Description: Previously it was possible to interrupt processing stats updates
because they were handled in a work queue. Interrupting the stats updates could
lead to a situation where we backup the control message queue. This patch
moves the stats update processing out of the work queue to be processed as
soon as hardware sends a request.
The following fix for the above has been accepted into upstream for
v4.16. This ticket requests backporting it to Ubuntu 18.04 LTS.
01c15e93a78c ("nfp: flower: prioritize stats updates")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752061/+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 1752061] [NEW] nfp: prioritize stats updates
Public bug reported:
This is a backport request from Netronome for Ubuntu 18.04 LTS.
Description: Previously it was possible to interrupt processing stats updates
because they were handled in a work queue. Interrupting the stats updates could
lead to a situation where we backup the control message queue. This patch
moves the stats update processing out of the work queue to be processed as soon
as hardware sends a request.
The following fix for the above has been accepted into upstream for
v4.16. This ticket requests backporting it to Ubuntu 18.04 LTS.
01c15e93a78c ("nfp: flower: prioritize stats updates")
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1752061
Title:
nfp: prioritize stats updates
Status in linux package in Ubuntu:
New
Bug description:
This is a backport request from Netronome for Ubuntu 18.04 LTS.
Description: Previously it was possible to interrupt processing stats updates
because they were handled in a work queue. Interrupting the stats updates could
lead to a situation where we backup the control message queue. This patch
moves the stats update processing out of the work queue to be processed as
soon as hardware sends a request.
The following fix for the above has been accepted into upstream for
v4.16. This ticket requests backporting it to Ubuntu 18.04 LTS.
01c15e93a78c ("nfp: flower: prioritize stats updates")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752061/+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 1735271] Re: Update firmware for netronome SmartNICs
Updated Netronome firmware is present upstream as of (merge) commit bc2164d5ed78. This includes: * Flower firmware for flow offload, including hardware offload of OvS using TC flower * CoreNIC 2.0, previously Core NIC 1.0. CoreNIC firmware allows Netronome SmartNICs to provide features similar to more traditional, non-SmartNICs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1735271 Title: Update firmware for netronome SmartNICs Status in linux-firmware package in Ubuntu: New Bug description: Feature request for Bionic Update firmware for Netronome SmartNICs. It is planned to provide updated firmware to the linux-firmware project in the coming days and update this bug with the list of updated firmware accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1735271/+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 1735271] [NEW] Update firmware for netronome SmartNICs
Public bug reported: Feature request for Bionic Update firmware for Netronome SmartNICs. It is planned to provide updated firmware to the linux-firmware project in the coming days and update this bug with the list of updated firmware accordingly. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1735271 Title: Update firmware for netronome SmartNICs Status in linux-firmware package in Ubuntu: New Bug description: Feature request for Bionic Update firmware for Netronome SmartNICs. It is planned to provide updated firmware to the linux-firmware project in the coming days and update this bug with the list of updated firmware accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1735271/+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 1624267] Re: PCI quirk required for correct access to configuration space of NFP 4000/6000
Unfortunately I am not in a position to run apport-collect 1624267 on a machine affected by this problem. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1624267 Title: PCI quirk required for correct access to configuration space of NFP 4000/6000 Status in linux package in Ubuntu: Confirmed Bug description: The Netronome NFP 4000/6000 intelligent NICs have an erratum erratum where reading/writing to PCI config space addresses above 0x600 can cause the NFP to generate PCIe completion timeouts. This can result in a system hanging. This may be avoided by setting the PCI config size correctly and updating the PCI subsystem to honour config sizes between PCI_CFG_SPACE_EXP_SIZE (4096) and PCI_CFG_SPACE_SIZE (256). This problem is resolves in upstream linux since v4.5. Backports have also been requested to upstream linux stable back to v3.10 and have so far been included in v4.4.10, v4.1.32, v4.18.41 and queued up for v3.10 stable. I would like to request that the same backports be made to the Ubuntu 13.0 kernel for Trusty 14.04 LTS. They are as follows: commit c2e771b02792d222cbcd9617fe71482a64f52647 Author: Simon Horman <simon.hor...@netronome.com> Date: Fri Dec 11 11:30:12 2015 +0900 PCI: Limit config space size for Netronome NFP4000 Like the NFP6000, the NFP4000 as an erratum where reading/writing to PCI config space addresses above 0x600 can cause the NFP to generate PCIe completion timeouts. Limit the NFP4000's PF's config space size to 0x600 bytes as is already done for the NFP6000. The NFP4000's VF is 0x6004 (PCI_DEVICE_ID_NETRONOME_NFP6000_VF), the same device ID as the NFP6000's VF. Thus, its config space is already limited by the existing use of quirk_nfp6000(). Signed-off-by: Simon Horman <simon.hor...@netronome.com> Signed-off-by: Bjorn Helgaas <bhelg...@google.com> commit 69874ec233871a62e1bc8c89e643993af93a8630 Author: Simon Horman <simon.hor...@netronome.com> Date: Fri Dec 11 11:30:11 2015 +0900 PCI: Add Netronome NFP4000 PF device ID Add the device ID for the PF of the NFP4000. The device ID for the VF, 0x6003, is already present as PCI_DEVICE_ID_NETRONOME_NFP6000_VF. Signed-off-by: Simon Horman <simon.hor...@netronome.com> Signed-off-by: Bjorn Helgaas <bhelg...@google.com> commit 9f33a2ae59f24452c1076749deb615bccd435ca9 Author: Jason S. McMullan <jason.mcmul...@netronome.com> Date: Wed Sep 30 15:35:07 2015 +0900 PCI: Limit config space size for Netronome NFP6000 family The NFP6000 has an erratum where reading/writing to PCI config space addresses above 0x600 can cause the NFP to generate PCIe completion timeouts. Limit the NFP6000's config space size to 0x600 bytes. Signed-off-by: Jason S. McMullan <jason.mcmul...@netronome.com> [simon: edited changelog] Signed-off-by: Simon Horman <simon.hor...@netronome.com> Signed-off-by: Bjorn Helgaas <bhelg...@google.com> commit a755e169031dac9ebaed03302c4921687c271d62 Author: Jason S. McMullan <jason.mcmul...@netronome.com> Date: Wed Sep 30 15:35:06 2015 +0900 PCI: Add Netronome vendor and device IDs Device IDs for the Netronome NFP3200, NFP3240, NFP6000, and NFP6000 SR-IOV devices. Signed-off-by: Jason S. McMullan <jason.mcmul...@netronome.com> [simon: edited changelog] Signed-off-by: Simon Horman <simon.hor...@netronome.com> Signed-off-by: Bjorn Helgaas <bhelg...@google.com> commit c20aecf6963d1273d8f6d61c042b4845441ca592 Author: Jason S. McMullan <jason.mcmul...@netronome.com> Date: Wed Sep 30 15:35:05 2015 +0900 PCI: Support PCIe devices with short cfg_size If a device quirk modifies the pci_dev->cfg_size to be less than PCI_CFG_SPACE_EXP_SIZE (4096), but greater than PCI_CFG_SPACE_SIZE (256), the PCI sysfs interface truncates the readable size to PCI_CFG_SPACE_SIZE. Allow sysfs access to config space up to cfg_size, even if the device doesn't support the entire 4096-byte PCIe config space. Note that pci_read_config() and pci_write_config() limit access to dev->cfg_size even though pcie_config_attr contains 4096 (the maximum size). Signed-off-by: Jason S. McMullan <jason.mcmul...@netronome.com> [simon: edited changelog] Signed-off-by: Simon Horman <simon.hor...@netronome.com> [bhelgaas: more changelog edits] Signed-off-by: Bjorn Helgaas <bhelg...@google.com> To manage notifications about
[Kernel-packages] [Bug 1624267] [NEW] PCI quirk required for correct access to configuration space of NFP 4000/6000
Public bug reported:
The Netronome NFP 4000/6000 intelligent NICs have an erratum erratum where
reading/writing to PCI config space addresses above 0x600 can cause the NFP
to generate PCIe completion timeouts. This can result in a system hanging.
This may be avoided by setting the PCI config size correctly and
updating the PCI subsystem to honour config sizes between
PCI_CFG_SPACE_EXP_SIZE (4096) and PCI_CFG_SPACE_SIZE (256).
This problem is resolves in upstream linux since v4.5.
Backports have also been requested to upstream linux stable back to v3.10
and have so far been included in v4.4.10, v4.1.32, v4.18.41 and queued
up for v3.10 stable.
I would like to request that the same backports be made to the Ubuntu 13.0
kernel for Trusty 14.04 LTS. They are as follows:
commit c2e771b02792d222cbcd9617fe71482a64f52647
Author: Simon Horman <simon.hor...@netronome.com>
Date: Fri Dec 11 11:30:12 2015 +0900
PCI: Limit config space size for Netronome NFP4000
Like the NFP6000, the NFP4000 as an erratum where reading/writing to PCI
config space addresses above 0x600 can cause the NFP to generate PCIe
completion timeouts.
Limit the NFP4000's PF's config space size to 0x600 bytes as is already
done for the NFP6000.
The NFP4000's VF is 0x6004 (PCI_DEVICE_ID_NETRONOME_NFP6000_VF), the same
device ID as the NFP6000's VF. Thus, its config space is already limited
by the existing use of quirk_nfp6000().
Signed-off-by: Simon Horman <simon.hor...@netronome.com>
Signed-off-by: Bjorn Helgaas <bhelg...@google.com>
commit 69874ec233871a62e1bc8c89e643993af93a8630
Author: Simon Horman <simon.hor...@netronome.com>
Date: Fri Dec 11 11:30:11 2015 +0900
PCI: Add Netronome NFP4000 PF device ID
Add the device ID for the PF of the NFP4000. The device ID for the VF,
0x6003, is already present as PCI_DEVICE_ID_NETRONOME_NFP6000_VF.
Signed-off-by: Simon Horman <simon.hor...@netronome.com>
Signed-off-by: Bjorn Helgaas <bhelg...@google.com>
commit 9f33a2ae59f24452c1076749deb615bccd435ca9
Author: Jason S. McMullan <jason.mcmul...@netronome.com>
Date: Wed Sep 30 15:35:07 2015 +0900
PCI: Limit config space size for Netronome NFP6000 family
The NFP6000 has an erratum where reading/writing to PCI config space
addresses above 0x600 can cause the NFP to generate PCIe completion
timeouts.
Limit the NFP6000's config space size to 0x600 bytes.
Signed-off-by: Jason S. McMullan <jason.mcmul...@netronome.com>
[simon: edited changelog]
Signed-off-by: Simon Horman <simon.hor...@netronome.com>
Signed-off-by: Bjorn Helgaas <bhelg...@google.com>
commit a755e169031dac9ebaed03302c4921687c271d62
Author: Jason S. McMullan <jason.mcmul...@netronome.com>
Date: Wed Sep 30 15:35:06 2015 +0900
PCI: Add Netronome vendor and device IDs
Device IDs for the Netronome NFP3200, NFP3240, NFP6000, and NFP6000 SR-IOV
devices.
Signed-off-by: Jason S. McMullan <jason.mcmul...@netronome.com>
[simon: edited changelog]
Signed-off-by: Simon Horman <simon.hor...@netronome.com>
Signed-off-by: Bjorn Helgaas <bhelg...@google.com>
commit c20aecf6963d1273d8f6d61c042b4845441ca592
Author: Jason S. McMullan <jason.mcmul...@netronome.com>
Date: Wed Sep 30 15:35:05 2015 +0900
PCI: Support PCIe devices with short cfg_size
If a device quirk modifies the pci_dev->cfg_size to be less than
PCI_CFG_SPACE_EXP_SIZE (4096), but greater than PCI_CFG_SPACE_SIZE (256),
the PCI sysfs interface truncates the readable size to PCI_CFG_SPACE_SIZE.
Allow sysfs access to config space up to cfg_size, even if the device
doesn't support the entire 4096-byte PCIe config space.
Note that pci_read_config() and pci_write_config() limit access to
dev->cfg_size even though pcie_config_attr contains 4096 (the maximum
size).
Signed-off-by: Jason S. McMullan <jason.mcmul...@netronome.com>
[simon: edited changelog]
Signed-off-by: Simon Horman <simon.hor...@netronome.com>
[bhelgaas: more changelog edits]
Signed-off-by: Bjorn Helgaas <bhelg...@google.com>
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1624267
Title:
PCI quirk required for correct access to configuration space of NFP
4000/6000
Status in linux package in Ubuntu:
New
Bug description:
The Netronome NFP 4000/6000 intelligent NICs have an erratum erratum where
reading/writing to PCI config space addresses above 0x600 can cause the NFP
to generate PCIe completion timeouts. This can result in a system hanging.
This may be avoided by setting the PCI config size correctly and
