As several different forums are discussing this issue,
I'm using this LP bug to continue investigation in to
current manifestation of this bug (after 4.15 kernel).
I suspect it's in one of the other places not fixed, as
my colleague Dan stated a while ago.
--
You received this bug notification
We are seeing definitely a problem on kernels after 4.15.0-159-generic,
which is the last known good kernel. 5.3* kernels are affected, but I
do not have data on most recent upstream.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Tags added: sts
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to become free. Usage count
Status in Linux:
Is anyone still seeing a similar issue on current mainline?
** Tags added: sts
--
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/1711407
Title:
unregister_netdevice: waiting for lo to
** Description changed:
SRU Justification:
[Impact]
- This bug in bcache [insert correct area] affects I/O performance on all
versions of the kernel [correct versions affected]. It is particularly negative
on ceph if used with bcache.
+ This bug in bcache affects I/O performance on all
** Tags added: seg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1906476
Title:
PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
sa_handle_get_from_db(zfsvfs->z_os,
** Tags added: sts
--
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/1907262
Title:
raid10: discard leads to corrupted file system
Status in linux package in Ubuntu:
Confirmed
Bug
Seen this as well -- although I don't believe it's causing any
problems that we know of -- sure does look right now like it's
only noise in the logs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Some of the 4.15 kernels fixed:
Bionic linux kernel: 4.15.0-109.110
Bionic linux-aws kernel: 4.15.0-1077.81
Xenial linux-hwe kernel: 4.15.0-107.108~16.04.1
Xenial linux-gcp kernel: 4.15.0-1078.88~16.04.1
--
You received this bug notification because you are a member of Kernel
Packages, which
Packages tested
linux-gcp (4.15.0-1078.88~16.04.1) xenial;
linux-hwe (4.15.0-107.108~16.04.1) xenial;
linux-gcp-4.15 (4.15.0-1078.88) bionic;
linux (4.15.0-107.108) bionic;
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Tested.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1879658
Title:
Cannot create ipvlans with >
** Changed in: linux (Ubuntu Bionic)
Importance: Medium => High
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Eoan)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Gavin Guo
Note that fix for all the above series are already released.
i.e, from Ubuntu-4.15.0-73.82.
--
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/1834322
Title:
Losing port aggregate with
Could anyone hitting this bug confirm it is a DUP
of LP Bug 1852077 and that latest releases fix this
issue?
The handling of the state changes/updates borked here
due to not just marking it as a DUP and closing this one.
I will close this next week otherwise.
** Changed in: linux (Ubuntu
Test kernel has been tested successfully so far by
original reporter and has fixed the Docker breakage
and so on.
--
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/1879658
Title:
Cannot
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
SRU request has been submitted.
If anyone would like to test, there are test images up on:
https://people.canonical.com/~nivedita/ipvlan-test-fix-278887/
You can 'wget' the files and then 'dpkg -i' the modules,
linux-image, modules-extra debs in that order, and reboot.
--
You received this
Public bug reported:
[IMPACT]
Setting an MTU larger than the default 1500 results in an
error on the recent (4.15.0-92+) Bionic/Xenial -hwe kernels
when attempting to create ipvlan interfaces:
# ip link add test0 mtu 9000 link eno1 type ipvlan mode l2
RTNETLINK answers: Invalid argument
This
The issue we have reported is easily avoided by specifying
the primary port to be the active interface of the bond.
On netplan-using systems:
Add the directive "primary: $interface" (e.g. "primary: p94s0f0")
to the "parameters:" section of the netplan config file.
--
You received this bug
Hello, diarmuid,
Re: original issue report, were you able to resolve your issue?
Please let us know.
--
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/1853638
Title:
BCM57416 NetXtreme-E
We are closing this LP bug for now as we aren't able to reproduce
in-house, and we cannot get access to a live testing repro env
at this time.
Here is what we know:
- There seems to be different performance for some tests when
the NIC is configured with active-backup bonding mode, between
Hi Malte,
Was this issue resolved for you?
There are several other possibilities that it could be - and
if it's still a problem with current mainline, please let
us know.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Edwin,
Do you happen to notice any IPv6 or LLDP or other link-local traffic
on the interfaces? (including backup interface).
The MTR loss % is purely a capture of their packets xmitted
and responses received, so for that UDP MTR test, this is saying
that UDP packets were lost, somewhere.
Additional observations.
MAAS is being used to deploy the system and configure
the bond interface and settings.
MAAS allows you to specify which is the primary interface, with
the other being the backup, for the active-backup bonding mode.
However, it does not appear to be working -it's not
Edwin, let me know if you can get in touch with me via the contact email
on my Launchpad page. Thanks for all the help!
--
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/1853638
Title:
ethtool-enp94s0f0
--
Settings for enp94s0f0:
Supported ports: [ FIBRE ]
Supported link modes: 1baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
** Attachment added: "ethtool -S for inactive interface enp94s0f0"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853638/+attachment/5327556/+files/ethtool-S-enp94s0f0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
"Bad" System/NIC:
NIC: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet Controller
System: Dell
Kernel: 5.3.0-28-generic #30~18.04.1-Ubuntu
(Note, this issue has been seen on prior kernels as well, upgraded
to latest to see if various problems were resolved)
Attaching stats/config files from
Good System/Good NIC (all configurations work) Comparison
NIC: NetXtreme II BCM57000 10 Gigabit Ethernet QLogic 57000
System: Dell
Kernel: 5.0.0-25-generic #26~18.04.1-Ubuntu
/proc/net/bonding/bond0
---
Ethernet
"Bad" Configuration for active-backup mode:
$ cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: enp94s0f1d1
We have narrowed it down to a flaw in a specific configuration setting
on this NIC, so we're comparing the good and bad configurations now.
Primary port: enp94s0f0
Secondary port: enp94s0f1d1
A] Good config for fault-tolerance (active-backup) bonding mode:
The second port on the NIC definitely works as the active
interface in an active-backup bonding configuration on the
other NICs.
At the moment, it's only this particular NIC that is seeing
this problem that we know of.
--
You received this bug notification because you are a member of Kernel
Hello Edwin,
Here is more information on the issue we are seeing wrt dropped
packets and other connectivity issues with this NIC.
The problem is *only* seen when the second port on the NIC is
chosen as the active interface of a active-backup configuration.
So on the "bad" system with the
Hey Edwin, sorry, I didn't see your last question.
I'll try and confirm but I've seen loss in both
directions but it's not clear whether that's significant
enough or not yet.
e.g., TCP traffic is retransmitted, so it could be segments
lost while outgoing or acks lost incoming.
4407
> NICs between systems? Are OS / kernel and driver
> versions the same on both systems?
Yes, identical distro release, kernel, and most of the software
stack (I have not obtained and examined the full sw stack).
Configuration of networking settings is also the same.
--
You received this bug
Thanks very much for helping on this, Edwin! Please let me
know if there's anything specific you need.
I'm asking them to disable any IPv6, LLDP traffic in their environment,
and retest and collect information again.
Also, I'd like to disable tpa, would this be at all useful:
modprobe bnx
> There are more than one variable at play here.
> Does the problem follow the NIC if you swap the
> NICs between systems? Are OS / kernel and driver
> versions the same on both systems?
Unfortunately, I've not been able to get them to try
permutations or switches, as yet, as this is still a
> The mtr packet loss is an interesting result. What mtr options did you
use? Is this a UDP or ICMP test?
The mtr command was:
mtr --no-dns --report --report-cycles 60 $IP_ADDR
so ICMP was going out.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Attachment added: "active interface ethtool-S"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1853638/+attachment/5324070/+files/ethtool-S-enp94s0f0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "backup interface ethtool-S"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1853638/+attachment/5324071/+files/ethtool-S-enp94s0f1d1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Note that iperf was identical whereas netperf and mtr showed
up differences (so it's possibly sporadic as well, not continuous)
1. iperf tcp test
--
GoodSystem.9.84 Gbits/sec
BadSystem18.37 Gbits/sec
BadSystem2...9.85 Gbits/sec
2. iperf udp test
Hello, Edwin,
We have two separate users/customers filing reports, and I can answer for
one of them. I'll ask the original poster separately as well to reply.
With respect to one of these situations, this is the following system:
Dell PowerEdge R440/0XP8V5, BIOS 2.2.11 06/14/2019
Note that a
(active interface)
> cat ethtool-S-enp94s0f1d1 | grep abort
[0]: tpa_aborts: 19775497
[1]: tpa_aborts: 26758635
[2]: tpa_aborts: 12008147
[3]: tpa_aborts: 15829167
[4]: tpa_aborts: 25099500
[5]: tpa_aborts: 3292554
[6]: tpa_aborts: 2863692
[7]: tpa_aborts:
We suspect this is a device (hw/fw) issue, however, not NetworkManager
or kernel (driver bnxt_en). I've added the kernel for the driver impact
(just in case, for now). This is really to eliminate all other causes
and confirm whether it's the device at root cause).
NIC
Product Name:
I have reports of the same device appearing to drop packets and incur
greater number of retransmissions under certain circumstances which
we're still trying to nail down.
I'm using this bug for now until proven to be a different problem.
This is causing issues in a production environment.
**
Fix has been committed to B, D, E. I've manually updated this
bug for now (it was not formally DUP'd to LP Bug 1852077.
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux (Ubuntu Eoan)
Importance: Undecided => High
** Changed in: linux (Ubuntu Disco)
FWIW, the fix has been committed to -stable:
"bonding: fix state transition issue in link monitoring"
Commit: 1899bb325149e481de31a4f32b59ea6f24e176ea
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/net/bonding?id=1899bb325149e481de31a4f32b59ea6f24e176ea
--
You
FWIW, the fix has been committed to -stable:
"bonding: fix state transition issue in link monitoring"
Commit: 1899bb325149e481de31a4f32b59ea6f24e176ea
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/net/bonding?id=1899bb325149e481de31a4f32b59ea6f24e176ea
** Tags
https://people.canonical.com/~phlin/kernel/lp-1852077-bonding/
There is a test kernel above (from that LP bug).
--
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/1834322
Title:
Losing
This is being handled as a DUP of LP Bug 1852077
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852077
** Changed in: linux (Ubuntu)
Status: Expired => In Progress
** Tags added: sts
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also
Still waiting on these patches being committed to all the Ubuntu trees.
Any ETA? Is this waiting on being picked up via -stable?
--
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/1852077
This issue has been tested and successfully verified:
Verification successful !
"...test appliance built with 4.15.0-58 was unusable ... hundreds of
"BUG: non-zero pgtables_bytes on freeing mm: -16384" in syslog, RestAPI
interface timeouts, failed to produce FFDC data using sosreport.
Build
** Tags added: sts
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Xenial)
Importance: High => Critical
** Changed in: linux (Ubuntu Bionic)
Importance: High =>
** Tags added: sts
** Tags added: linux
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
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/1840704
Title:
ZFS kernel modules
I'll update here once kernel is uploaded.
--
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/1840046
Title:
BUG: non-zero pgtables_bytes on freeing mm: -16384
Status in linux package in
I unduped it for test process clarity.
Trying to get the relevant people to test the fix.
--
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/1840046
Title:
BUG: non-zero pgtables_bytes on
** This bug is no longer a duplicate of bug 1837664
Bionic update: upstream stable patchset 2019-07-23
--
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/1840046
Title:
BUG: non-zero
*** This bug is a duplicate of bug 1837664 ***
https://bugs.launchpad.net/bugs/1837664
I'll unDUP it unless the kernel team says otherwise in IRC.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
*** This bug is a duplicate of bug 1837664 ***
https://bugs.launchpad.net/bugs/1837664
I'm not sure this bug should be DUP'd to the stable-release
bug. Might confuse the verification and handling triggers,
perhaps?
Will need to make sure the fix is tested once the fix is
uploaded.
--
You
Verified on Xenial
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1794232
Title:
Geneve tunnels
As the test kernel with the backported Xenial fix
has been up for almost 2 months now, I'm submitting
the SRU for Xenial, although I have not received
feedback from original reporter or others.
Backported patch for Xenial varies slightly from the
cherry-picked patch for B, C.
My testing has
** Tags added: sts
--
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/1779756
Title:
Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu
18.04)
Status in linux package in
** Tags added: sts
--
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/1814095
Title:
bnxt_en_po: TX timed out triggering Netdev Watchdog Timer
Status in linux package in Ubuntu:
** Tags added: sts
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic verification-done-cosmic
** Tags removed: verification-done-cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: sts
--
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/1794232
Title:
Geneve tunnels don't work when ipv6 is disabled
Status in linux package in Ubuntu:
Fix Released
Bionic, Cosmic kernels successfully tested.
I've updated the tags.
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which
Late update, but the original reporter did test the proposed
kernel on systems able to reproduce the problem and were
tested successfully.
We do not yet have a way of reproducing this on Xenial (i.e,
any 4.4 kernel). I'm still leaving this an open issue, will be
trying to do this and once we can
A 4.4 test kernel with the fix backported is available at:
https://people.canonical.com/~nivedita/geneve-xenial-test/
if anyone wishes to validate the 4.4 X solution.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Resubmitted SRU for B,C for this kernel cycle.
--
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/1794232
Title:
Geneve tunnels don't work when ipv6 is disabled
Status in linux package in
Submitted SRU request for Bionic, Cosmic.
Huge thanks for the testing, Matthew!
--
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/1794232
Title:
Geneve tunnels don't work when ipv6 is
** Tags added: cosmic xenial
--
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/1794232
Title:
Geneve tunnels don't work when ipv6 is disabled
Status in linux package in Ubuntu:
Fix
** Description changed:
SRU Justification
Impact: Cannot create geneve tunnels if ipv6 is disabled dynamically.
Fix:
Fixed by upstream commit in v5.0:
Commit: cf1c9ccba7308e48a68fa77f476287d9d614e4c7
"geneve: correctly handle ipv6.disable module parameter"
- Hence available
** Description changed:
+ SRU Justification
+
+ Impact: Cannot create geneve tunnels if ipv6 is disabled dynamically.
+
+ Fix:
+ Fixed by upstream commit in v5.0:
+ Commit: cf1c9ccba7308e48a68fa77f476287d9d614e4c7
+ "geneve: correctly handle ipv6.disable module parameter"
+
+ Hence available
** Description changed:
[Impact]
When attempting to create a geneve tunnel on Ubuntu 16.04 Xenial, in
an OS environment with open vswitch, where ipv6 has been disabled,
the create fails with the error :
“ovs-vsctl: Error detected while setting up 'geneve0': could not
add network
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Released
** Description changed:
[Impact]
When attempting to create a geneve tunnel on Ubuntu 16.04 Xenial, in
an OS environment with open vswitch, where ipv6 has been disabled,
the create fails with the error :
Importance: High
Status: In Progress
** Changed in: linux (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => Nivedita Singhvi (niveditasinghvi)
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned) => Nivedita
I have installed and booted to this kernel, and ensured no
new regression introduced, although I cannot repro the issue.
** Tags removed: 4.15.0-24-generic cosmic kernel verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
**
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
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/1820948
Title:
i40e xps management broken when > 64 queues/cpus
I'm still trying to confirm this for Xenial.
--
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/1820948
Title:
i40e xps management broken when > 64 queues/cpus
Status in linux package in
Submitted patches for SRU.
** Description changed:
[Impact]
Transmit packet steering (xps) settings don't work when
the number of queues (cpus) is higher than 64. This is
currently still an issue on the 4.15 kernel (Xenial -hwe
- and Bionic kernels).
+ and Bionic kernels).
It was
I am not sure we could deterministically provoke the
issue. At the very least to ensure no other regression
was introduced, I would run it under heavy network load.
The environment in question which saw the issue had
network load, contention for cpus and several other
issues occur.
The basic
Will be submitting SRU request early next week; trying to get
it into this next kernel release cycle.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Nivedita Singhvi (niveditasinghvi)
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
** C
Just briefly wanted to say that this is one we've discussed at
length -- we may not be able to get someone who has the right
NIC to test with it in time.
I'm sanity checking the kernel, but that is not exercising the
key change here.
If we could assume verification-done for our purposes
It's been reported by an external reporter and reproduced
internally.
--
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/1820948
Title:
i40e xps management broken when > 64 queues/cpus
Importance: High
Status: Confirmed
** Affects: linux (Ubuntu Bionic)
Importance: High
Assignee: Nivedita Singhvi (niveditasinghvi)
Status: Confirmed
** Tags: bionic
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Cha
Submitted SRU request
--
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/1779756
Title:
Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu
18.04)
Status in linux package in
** Tags added: bionic cosmic
--
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/1779756
Title:
Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu
18.04)
Status in linux
** Description changed:
- Today Ubuntu 16.04 LTS Enablement Stacks has moved from the Kernel 4.13
- to the Kernel 4.15.0-24-generic.
+ [Impact]
+ The i40e driver can get stalled on tx timeouts. This can happen when
+ DCB is enabled on the connected switch. This can also trigger a
+ second
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Nivedita Singhvi (niveditasinghvi)
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned) => Nivedita Singhvi (niveditasinghvi)
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
*
We have a user who has been successfully running under load
with the test kernel provided here which was patched with
the following two commits:
"i40e: Fix for Tx timeouts when interface is brought up if DCB is enabled"
Commit: fa38e30ac73fbb01d7e5d0fd1b12d412fa3ac3ee
"i40e: prevent overlapping
Terry,
We've had a lot of discussion over this bug. It does not have
a reliable reproducer, and I have not yet received any acks
on testing of the above.
Our thinking was that it was still better to patch it since
it has been seen by the mainline driver as well and we'd like
to avoid a
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Nivedita Singhvi (niveditasinghvi)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
+ [Impact]
+
+ The bnxt_en_bpo driver experienced tx timeouts causing the system to
+ experience network stalls and fail to send data and heartbeat packets.
+
The following 25Gb Broadcom NIC error was seen on Xenial
running the 4.4.0-141-generic kernel on an amd64
If anyone is interested and willing to test a 4.4 kernel
patched with the fix "bnxt_en: Fix TX timeout during netpoll"
backported to the bnxt_en_bpo driver, please find the packages
here:
http://people.canonical.com/~nivedita/bpo/
--
You received this bug notification because you are a member
Any update on a Bionic fix?
--
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/1779756
Title:
Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu
18.04)
Status in linux
** 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/1814095
Title:
bnxt_en_po: TX timed out triggering Netdev Watchdog
Due to earlier NIC flapping observed on systems for the
25Gb Broadcom NIC, with originally the following config,
the firmware was upgraded to avoid a known FW bug:
$ cat ethtool_-i_enp59s0f1d1
driver: bnxt_en_bpo
version: 1.8.1
firmware-version: 20.8.163/1.8.4 pkg 20.08.04.03
** Attachment added: "kern.log.excerpt-netdev-watchdog-timeout.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814095/+attachment/5234643/+files/kern.log.excerpt-netdev-watchdog-timeout.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
The following 25Gb Broadcom NIC error was seen on Xenial
running the 4.4.0-141-generic kernel on an amd64 host
seeing moderate-heavy network traffic (just once):
* The bnxt_en_po driver froze on a "TX timed out" error
and triggered the Netdev Watchdog timer under load.
*
1 - 100 of 120 matches
Mail list logo
