[Kernel-packages] [Bug 1931245] Re: driver/broadcom/bnxt: invalid dev_port
Sent backport for v5.4 stable. Greg replied, that backport is queued for
v4.9, v4.14, v4.19 and v5.4, so Focal will get it via regular stable
update
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Invalid
** Changed in: linux (Ubuntu Hirsute)
Status: New => Invalid
** Changed in: linux (Ubuntu Groovy)
Status: New => Invalid
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** No longer affects: linux (Ubuntu Groovy)
** No longer affects: linux (Ubuntu Hirsute)
** No longer affects: linux (Ubuntu Impish)
** Changed in: linux (Ubuntu)
Status: Invalid => In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
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/1931245
Title:
driver/broadcom/bnxt: invalid dev_port
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Bug description:
[SRU Justification]
[Impact]
With broadcom dual port NIC naming convention between port 1 and port
2 can be inconsistent
For example, if network port 1 of a device is named enp1s0f0, port 2
can end up with the name enp1s0f1d1 rather than enp1s0f1
Issue is due to an inconsistent port_dev and any scripts based on it
can have unexpected behavior
This has been fixed in v5.6 by the following upstream commit
- 1d86859fdf31("bnxt_en: Remove the setting of dev_port")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1d86859fdf31
The bug exists since the beginning of the driver.
== Fix ==
Backport the requested patches to Focal (5.4)
== Risk of Regression ==
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931245/+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 1931245] Re: driver/broadcom/bnxt: invalid dev_port
Correction: bug was fixed in v5.6.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Krzysztof Kozlowski (krzk)
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Assignee: Krzysztof Kozlowski (krzk)
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Krzysztof Kozlowski (krzk)
** Changed in: linux (Ubuntu Hirsute)
Assignee: (unassigned) => Krzysztof Kozlowski (krzk)
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Krzysztof Kozlowski (krzk)
** Changed in: linux (Ubuntu Impish)
Status: New => In Progress
** Description changed:
[SRU Justification]
[Impact]
With broadcom dual port NIC naming convention between port 1 and port 2
can be inconsistent
For example, if network port 1 of a device is named enp1s0f0, port 2 can
end up with the name enp1s0f1d1 rather than enp1s0f1
Issue is due to an inconsistent port_dev and any scripts based on it can
have unexpected behavior
- This has been fixed in v5.12 by the following upstream commit
- - 1d86859fdf31("bnxt_en: Remove the setting of dev_port")
+ This has been fixed in v5.6 by the following upstream commit
+ - 1d86859fdf31("bnxt_en: Remove the setting of dev_port")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1d86859fdf31
The bug exists since the beginning of the driver.
== Fix ==
Backport the requested patches to Focal (5.4)
== Risk of Regression ==
The patch is trivial, the potential regressions are low.
--
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/1931245
Title:
driver/broadcom/bnxt: invalid dev_port
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
New
Status in linux source package in Groovy:
New
Status in linux source package in Hirsute:
New
Status in linux source package in Impish:
In Progress
Bug description:
[SRU Justification]
[Impact]
With broadcom dual port NIC naming convention between port 1 and port
2 can be inconsistent
For example, if network port 1 of a device is named enp1s0f0, port 2
can end up with the name enp1s0f1d1 rather than enp1s0f1
Issue is due to an inconsistent port_dev and any scripts based on it
can have unexpected behavior
This has been fixed in v5.6 by the following upstream commit
- 1d86859fdf31("bnxt_en: Remove the setting of dev_port")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1d86859fdf31
The bug exists since the beginning of the driver.
== Fix ==
Backport the requested patches to Focal (5.4)
== Risk of Regression ==
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931245/+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 1931245] Re: driver/broadcom/bnxt: invalid dev_port
For the risk of regression - this paragraph should explain possible
failures, for example if something goes wrong. Even trivial patch can
cause some effects. This one as well.
--
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/1931245
Title:
driver/broadcom/bnxt: invalid dev_port
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
New
Status in linux source package in Groovy:
New
Status in linux source package in Hirsute:
New
Status in linux source package in Impish:
In Progress
Bug description:
[SRU Justification]
[Impact]
With broadcom dual port NIC naming convention between port 1 and port
2 can be inconsistent
For example, if network port 1 of a device is named enp1s0f0, port 2
can end up with the name enp1s0f1d1 rather than enp1s0f1
Issue is due to an inconsistent port_dev and any scripts based on it
can have unexpected behavior
This has been fixed in v5.12 by the following upstream commit
- 1d86859fdf31("bnxt_en: Remove the setting of dev_port")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1d86859fdf31
The bug exists since the beginning of the driver.
== Fix ==
Backport the requested patches to Focal (5.4)
== Risk of Regression ==
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931245/+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 1931245] Re: driver/broadcom/bnxt: invalid dev_port
** Project changed: canonical-identity-provider => linux (Ubuntu)
--
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/1931245
Title:
driver/broadcom/bnxt: invalid dev_port
Status in linux package in Ubuntu:
New
Bug description:
[SRU Justification]
[Impact]
With broadcom dual port NIC naming convention between port 1 and port
2 can be inconsistent
For example, if network port 1 of a device is named enp1s0f0, port 2
can end up with the name enp1s0f1d1 rather than enp1s0f1
Issue is due to an inconsistent port_dev and any scripts based on it
can have unexpected behavior
This has been fixed in v5.12 by the following upstream commit
- 1d86859fdf31("bnxt_en: Remove the setting of dev_port")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1d86859fdf31
The bug exists since the beginning of the driver.
== Fix ==
Backport the requested patches to Focal (5.4)
== Risk of Regression ==
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931245/+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
