** Changed in: linux (Ubuntu)
Status: Triaged => 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/1771480
Title:
WARNING: CPU: 28 PID: 34085 at /build/linux-
This bug was fixed in the package linux - 3.13.0-153.203
---
linux (3.13.0-153.203) trusty; urgency=medium
* linux: 3.13.0-153.203 -proposed tracker (LP: #1776819)
* CVE-2018-3665 (x86)
- x86/fpu: Print out whether we are doing lazy/eager FPU context switches
- x86/fpu:
ubuntu@lp1771480:~$ uname -a
Linux lp1771480 3.13.0-151-generic #201-Ubuntu SMP Wed May 30 14:22:13 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@lp1771480:~$ dmesg | grep -m 1 -A 2 dev_disable_lro
[3.811702] WARNING: CPU: 2 PID: 1209 at
/build/linux-qbUwJB/linux-3.13.0/net/core/dev.c:1433
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-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu Trusty)
Status: Triaged => Fix Committed
--
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/1771480
Title:
WARNING: CPU: 28 PID: 34085 at /build/linux-
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Trusty)
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
** Description changed:
- I have multiple instances of this dev_disable_lro error in kern.log. Also
seeing this:
- systemd-udevd[1452]: timeout: killing 'bridge-network-interface' [2765]
- <4>May 1 22:56:42 xxx kernel: [ 404.520990] bonding: bond0: Warning: No
802.3ad response from the link
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
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/1771480
The dev_disable_lro warning is happening due to some logic issues in the
features code. The LRO on the VLAN (bond0.200, e.g.) that's being
warned about does end up being disabled by a NETDEV_FEAT_CHANGE callback
when the underlying bond0's features are updated, so the warning is
spurious.
The warning message:
"failed to disable LRO!"
is coming from the function dev_disable_lro():
/**
* dev_disable_lro - disable Large Receive Offload on a device
* @dev: device
*
* Disable Large Receive Offload (LRO) on a net device. Must be
* called under RTNL. This is
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771480/+attachment/5140100/+files/kern.log
--
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/1771480
This occurred during the deployment of the DPDK compute. The DPDK was
not deployed. The bond0 and bond1 configuration appears to have failed.
---8<---
Preliminary analysis: the LRO appears to be off after the kernel traces,
despite the message. I am inquiring as to the nature of
12 matches
Mail list logo
