This bug was fixed in the package linux - 4.4.0-208.240
---
linux (4.4.0-208.240) xenial; urgency=medium
* xenial/linux: 4.4.0-208.240 -proposed tracker (LP: #1922069)
* linux ADT test failure with linux/4.4.0-207.239 -
ubuntu_qrt_kernel_security.test-kernel-security.py (LP:
This bug was fixed in the package linux - 4.15.0-141.145
---
linux (4.15.0-141.145) bionic; urgency=medium
* bionic/linux: 4.15.0-141.145 -proposed tracker (LP: #1919536)
* binary assembly failures with CONFIG_MODVERSIONS present (LP: #1919315)
- [Packaging] quiet (nomially)
Verified for Bionic following the same test procedure from comment #13, running
on the current -proposed kernel:
ubuntu@snorlax:~$ uname -rv
4.15.0-141-generic #145-Ubuntu SMP Wed Mar 24 18:08:07 UTC 2021
I had to adjust the tx_desc_addr probes, subtracting 0x4 from both offsets and
changing
Verified for Xenial following the same test procedure from comment #13, running
on the current -proposed kernel:
ubuntu@snorlax:~/kprobe$ uname -rv
4.4.0-207-generic #239-Ubuntu SMP Thu Mar 25 02:59:26 UTC 2021
The offsets don't seem to have changed on any of the probes, so I've
used the same
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
[Impact]
The i40e driver sometimes causes a "malicious device" event that the firmware
detects, which causes the firmware to reset the NIC, causing an interruption in
the network connection - which can cause further problems, e.g. if the
interface is in a bond; the
I'm attaching kprobes for the Xenial kernels. These are based on the
4.4.0-203/204 versions.
I followed the same test setup for Bionic, as described in the previous
comment, and also had similar results. The netdev watchdog seems to take good
care of any hung queues, so in the end PF resets
Given that we're could be changing reset behavior that might be expected
from the firmware, I wrote a quick set of kprobes to force the firmware
to raise MDD events and test out the patched kernel from the PPA.
I tried to force faulty TX descriptors according to "Table 7-138. Tx
Descriptor
10 matches
Mail list logo
