[Group.of.nepali.translators] [Bug 1840789] Re: bnx2x: fatal hardware error/reboot/tx timeout with LLDP enabled
This fix has already been released as part of the kernel stable updates.
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Opinion
** Changed in: linux (Ubuntu Xenial)
Status: Opinion => Fix Released
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1840789
Title:
bnx2x: fatal hardware error/reboot/tx timeout with LLDP enabled
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Disco:
Won't Fix
Status in linux source package in Eoan:
Fix Released
Bug description:
[Impact]
* The bnx2x driver may cause hardware faults (leading to
panic/reboot) and other behaviors as transmit timeouts,
after commit 3968d38917eb ("bnx2x: Fix Multi-Cos.") is
introduced.
* This issue has been observed by an user shortly
after starting docker & kubelet, with adapters:
- Broadcom NetXtreme II BCM57800 [14e4:168a] from Dell [1028:1f5c]
- Broadcom NetXtreme II BCM57840 [14e4:16a1] from Dell [1028:1f79]
* If options to ignore hardware faults are used
(erst_disable=1 hest_disable=1 ghes.disable=1)
the system doesn't panic/reboot and continues
on to timeout on adapter stats, then transmit
timeouts, spewing some adapter firmware dumps,
but the network interface is non-functional.
* The issue only happened when LLDP is enabled
on the network switches, and crashdump shows
the bnx2x driver is stuck/waits for firmware
to complete the stop traffic command in LLDP
handling. Workaround used is to disable LLDP
in the network switches/ports.
* Analysis of the driver and firmware dumps
didn't help significantly towards finding
the root cause.
* Upstream/mainline recently just reverted the
patch, due to similar problem reports, while
looking for the root cause/proper fix.
[Test Case]
* No reproducible test case found outside
the user's systems/cluster, where it is
enough to start docker & kubelet & wait.
* The user verified test kernels for Xenial
and Bionic - the problem does not happen;
build-tested on Disco.
[Regression Potential]
* Users who significantly use/apply the non-default
traffic class (tc) / class of service (cos) might
possibly see performance changes (if any at all)
in such applications, however that's unclear now.
* This is a recent revert upstream (v5.3-rc'ish),
so there's chance things might change in this area.
* Nonetheless, the patch is authored by the driver
vendor, and made its way into stable kernels
(e.g., v5.2.8 which made Eoan/19.10 recently).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840789/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1840789] Re: bnx2x: fatal hardware error/reboot/tx timeout with LLDP enabled
Ubuntu 19.04 reached end of life on January 23, 2020. I am therefore
marking this bug 'wontfix' for that release.
** Changed in: linux (Ubuntu Disco)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1840789
Title:
bnx2x: fatal hardware error/reboot/tx timeout with LLDP enabled
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Incomplete
Status in linux source package in Bionic:
Incomplete
Status in linux source package in Disco:
Won't Fix
Status in linux source package in Eoan:
Fix Released
Bug description:
[Impact]
* The bnx2x driver may cause hardware faults (leading to
panic/reboot) and other behaviors as transmit timeouts,
after commit 3968d38917eb ("bnx2x: Fix Multi-Cos.") is
introduced.
* This issue has been observed by an user shortly
after starting docker & kubelet, with adapters:
- Broadcom NetXtreme II BCM57800 [14e4:168a] from Dell [1028:1f5c]
- Broadcom NetXtreme II BCM57840 [14e4:16a1] from Dell [1028:1f79]
* If options to ignore hardware faults are used
(erst_disable=1 hest_disable=1 ghes.disable=1)
the system doesn't panic/reboot and continues
on to timeout on adapter stats, then transmit
timeouts, spewing some adapter firmware dumps,
but the network interface is non-functional.
* The issue only happened when LLDP is enabled
on the network switches, and crashdump shows
the bnx2x driver is stuck/waits for firmware
to complete the stop traffic command in LLDP
handling. Workaround used is to disable LLDP
in the network switches/ports.
* Analysis of the driver and firmware dumps
didn't help significantly towards finding
the root cause.
* Upstream/mainline recently just reverted the
patch, due to similar problem reports, while
looking for the root cause/proper fix.
[Test Case]
* No reproducible test case found outside
the user's systems/cluster, where it is
enough to start docker & kubelet & wait.
* The user verified test kernels for Xenial
and Bionic - the problem does not happen;
build-tested on Disco.
[Regression Potential]
* Users who significantly use/apply the non-default
traffic class (tc) / class of service (cos) might
possibly see performance changes (if any at all)
in such applications, however that's unclear now.
* This is a recent revert upstream (v5.3-rc'ish),
so there's chance things might change in this area.
* Nonetheless, the patch is authored by the driver
vendor, and made its way into stable kernels
(e.g., v5.2.8 which made Eoan/19.10 recently).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840789/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1840789] Re: bnx2x: fatal hardware error/reboot/tx timeout with LLDP enabled
This fix is already present in Eoan and Unstable:
~/git/ubuntu-eoan$ git log --oneline origin/master-next --
drivers/net/ethernet/broadcom/bnx2x/ | head | grep cos
1c41d7b7cf60 bnx2x: Disable multi-cos feature.
~/git/ubuntu-eoan$ git describe --contains 1c41d7b7cf60
Ubuntu-5.2.0-12.13~51
~/git/ubuntu-unstable$ git log --oneline origin/master --
drivers/net/ethernet/broadcom/bnx2x/ | head | grep cos
d1f0b5dce8fd bnx2x: Disable multi-cos feature.
~/git/ubuntu-unstable$ git describe --contains d1f0b5dce8fd
Ubuntu-5.3.0-4.5~313^2~91
** Description changed:
- Description/patches to be provided this week.
+ [Impact]
+
+ * The bnx2x driver may cause hardware faults (leading to
+panic/reboot) and other behaviors as transmit timeouts,
+after commit 3968d38917eb ("bnx2x: Fix Multi-Cos.") is
+introduced.
+
+ * This issue has been observed by an user shortly
+after starting docker & kubelet, with adapters:
+- Broadcom NetXtreme II BCM57800 [14e4:168a] from Dell [1028:1f5c]
+- Broadcom NetXtreme II BCM57840 [14e4:16a1] from Dell [1028:1f79]
+
+ * If options to ignore hardware faults are used
+(erst_disable=1 hest_disable=1 ghes.disable=1)
+the system doesn't panic/reboot and continues
+on to timeout on adapter stats, then transmit
+timeouts, spewing some adapter firmware dumps,
+but the network interface is non-functional.
+
+ * The issue only happened when LLDP is enabled
+on the network switches, and crashdump shows
+the bnx2x driver is stuck/waits for firmware
+to complete the stop traffic command in LLDP
+handling. Workaround used is to disable LLDP
+in the network switches/ports.
+
+ * Analysis of the driver and firmware dumps
+didn't help significantly towards finding
+the root cause.
+
+ * Upstream/mainline recently just reverted the
+patch, due to similar problem reports, while
+looking for the root cause/proper fix.
+
+ [Test Case]
+
+ * No reproducible test case found outside
+the user's systems/cluster, where it is
+enough to start docker & kubelet & wait.
+
+ * The user verified test kernels for Xenial
+and Bionic - the problem does not happen.
+
+ [Regression Potential]
+
+ * Users who significantly use/apply the non-default
+traffic class (tc) / class of service (cos) might
+possibly see performance changes (if any at all)
+in such applications, however that's unclear now.
+
+ * This is a recent revert upstream (v5.3-rc'ish),
+so there's chance things might change in this area.
+
+ * Nonetheless, the patch is authored by the driver
+vendor, and made its way into stable kernels
+(e.g., v5.2.8 which made Eoan/19.10 recently).
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Disco)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Description changed:
[Impact]
- * The bnx2x driver may cause hardware faults (leading to
-panic/reboot) and other behaviors as transmit timeouts,
-after commit 3968d38917eb ("bnx2x: Fix Multi-Cos.") is
-introduced.
+ * The bnx2x driver may cause hardware faults (leading to
+ panic/reboot) and other behaviors as transmit timeouts,
+ after commit 3968d38917eb ("bnx2x: Fix Multi-Cos.") is
+ introduced.
- * This issue has been observed by an user shortly
-after starting docker & kubelet, with adapters:
-- Broadcom NetXtreme II BCM57800 [14e4:168a] from Dell [1028:1f5c]
-- Broadcom NetXtreme II BCM57840 [14e4:16a1] from Dell [1028:1f79]
+ * This issue has been observed by an user shortly
+ after starting docker & kubelet, with adapters:
+ - Broadcom NetXtreme II BCM57800 [14e4:168a] from Dell [1028:1f5c]
+ - Broadcom NetXtreme II BCM57840 [14e4:16a1] from Dell [1028:1f79]
- * If options to ignore hardware faults are used
-(erst_disable=1 hest_disable=1 ghes.disable=1)
-the system doesn't panic/reboot and continues
-on to timeout on adapter stats, then transmit
-timeouts, spewing some adapter firmware dumps,
-but the network interface is non-functional.
+ * If options to ignore hardware faults
