[Kernel-packages] [Bug 1963802] Re: lenovo x260: unable to suspend or power off cleanly

Worked around for now by disabling the security chip via the BIOS. -- 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/1963802 Title: lenovo x260: unable to suspend or power off cleanly

[Kernel-packages] [Bug 1963802] [NEW] lenovo x260: unable to suspend or power off cleanly

Public bug reported: Since upgrading to the new 5.15 kernel in Jammy development I've been unable to suspend or power of my x260 successfully. suspend - laptop appears to have suspended with the power led pulsing but then won't resume power off - laptop appears to have powered off but infact

[Kernel-packages] [Bug 1860987] Re: openvswitch: same tcp session encapsulated with different udp src port for ovs vxlan tunnel

Raising tasks for Linux as well - Groovy onwards is good so just focal and bionic targets now. -- 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/1860987 Title: openvswitch: same tcp

[Kernel-packages] [Bug 1860987] Re: openvswitch: same tcp session encapsulated with different udp src port for ovs vxlan tunnel

For reference - this should be usable on Focal with the HWE kernel (rather than the 5.4 release kernel). -- 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/1860987 Title: openvswitch: same

[Kernel-packages] [Bug 1860987] Re: openvswitch: same tcp session encapsulated with different udp src port for ovs vxlan tunnel

Commit that introduces the hash to the upcall to OVS: https://kernel.ubuntu.com/git/ubuntu/ubuntu- groovy.git/commit/include/uapi/linux/openvswitch.h?id=bd1903b7c4596ba6f7677d0dfefd05ba5876707d ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux

[Kernel-packages] [Bug 1914447] Re: geneve overlay network on vlan interface broken with offload enabled

Please can this be considered for Linux 5.4 as well. ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Importance: Medium => High -- You received this

[Kernel-packages] [Bug 1907086] Re: hardware offloaded PCI devices don't have associated netlink interfaces

This maybe due to some testing we've been doing on not-rebinding the VF representator ports back to the host once the card is switched into switchdev mode -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1907086] Re: hardware offloaded PCI devices don't have associated netlink interfaces

Nova reports the net devices as missing as well: 2020-12-07 12:31:56.123 8280 WARNING nova.pci.utils [req-3392d882-bd3c-4146-88ab-30c92be51c4d - - - - -] No net device was found for VF :81:09.3: nova.exception.PciDeviceNotFoundById: PCI device :81:09.3 not found 2020-12-07 12:31:56.125

[Kernel-packages] [Bug 1907086] Re: hardware offloaded PCI devices don't have associated netlink interfaces

Might be related: [ 9579.735931] mlx5_core :81:00.0: cmd_work_handler:887:(pid 4320): failed to allocate command entry [10069.733292] mlx5_core :81:00.0: cmd_work_handler:887:(pid 157001): failed to allocate command entry [10129.734360] mlx5_core :81:00.1: cmd_work_handler:887:(pid

[Kernel-packages] [Bug 1815844] Re: iscsi multipath dm-N device only used on first volume attachment

Marking charm task as invalid as this is a kernel issue with the xenial release kernel. Ubuntu/Linux bug task raised for further progression if updating to the latest HWE kernel on Xenial is not an option. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed

[Kernel-packages] [Bug 1875863] Re: ceph -- Unable to mount ceph volume on s390x

** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: ceph (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1853592] Re: hw-tc-offload not reliable with VXLAN

** Package changed: linux (Ubuntu) => openvswitch (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/1853592 Title: hw-tc-offload not reliable with VXLAN Status in openvswitch

[Kernel-packages] [Bug 1851819] Re: bond: An illegal loopback occurred on slave

With https://patchwork.ozlabs.org/patch/1224104/ and the secondary port link set to down I get reliable network connections to instances with offloaded ports. Upstream developers pointed me to a commit that might resolve this. -- You received this bug notification because you are a member of

[Kernel-packages] [Bug 1851819] Re: bond: An illegal loopback occurred on slave

Bug 1852077 - however that is marked fix released so I think something else is at fault. -- 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/1851819 Title: bond: An illegal loopback occurred

[Kernel-packages] [Bug 1853592] Re: hw-tc-offload not reliable with VXLAN

OpenStack related patch into OVS: https://patchwork.ozlabs.org/patch/1224104/ I've picked this ontop of the eoan packages and it appears to help resolve this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1853592] Re: hw-tc-offload not reliable with VXLAN

Further Debugging: tcpdump on representator port for a VM: 12:09:41.933101 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:2d:b5:eb (oui Unknown), length 297 12:09:41.939887 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28

[Kernel-packages] [Bug 1851819] Re: bond: An illegal loopback occurred on slave

Did a bit more testing; the error message is only seen when the card is in offload mode; when its in legacy mode (the default) the error message is not seen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1853592] Re: hw-tc-offload not reliable with VXLAN

** Tags added: hwoffload -- 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/1853592 Title: hw-tc-offload not reliable with VXLAN Status in linux package in Ubuntu: Confirmed Bug

[Kernel-packages] [Bug 1851819] Re: bond: An illegal loopback occurred on slave

** Tags added: hwoffload -- 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/1851819 Title: bond: An illegal loopback occurred on slave Status in linux package in Ubuntu: Confirmed Bug

[Kernel-packages] [Bug 1853592] Re: hw-tc-offload not reliable with VXLAN

I re-deployed without bonding (i.e. single port with VF's configured) and I still see the same issue - so bug 1851819 appears to not be related to this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1853592] Re: hw-tc-offload not reliable with VXLAN

Testing with VM's that are not using hardware offloaded ports i.e. pure openvswitch datapath in kernel. -- 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/1853592 Title: hw-tc-offload not

[Kernel-packages] [Bug 1853592] Re: hw-tc-offload not reliable with VXLAN

VM's without offloaded ports work fine with 'hw-tc-offload' enabled on the main PF port. -- 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/1853592 Title: hw-tc-offload not reliable with

[Kernel-packages] [Bug 1853592] Re: hw-tc-offload not reliable with VXLAN

This may be related to bug 1851819 -- 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/1853592 Title: hw-tc-offload not reliable with VXLAN Status in linux package in Ubuntu: Confirmed

[Kernel-packages] [Bug 1853592] ProcInterrupts.txt

apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1853592/+attachment/5307084/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1853592] ProcModules.txt

apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1853592/+attachment/5307085/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1853592] ProcCpuinfoMinimal.txt

apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1853592/+attachment/5307083/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1853592] CurrentDmesg.txt

apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1853592/+attachment/5307080/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1853592] WifiSyslog.txt

apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1853592/+attachment/5307087/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1853592] Lspci.txt

apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1853592/+attachment/5307081/+files/Lspci.txt -- 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/1853592

[Kernel-packages] [Bug 1853592] ProcCpuinfo.txt

apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1853592/+attachment/5307082/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1853592] [NEW] hw-tc-offload not reliable with VXLAN

Public bug reported: OpenStack Train OVS 2.12 Linux 5.3 from hwe edge Connect-X 5 running latest firmware from Mellanox. Overlay networking configured with VXLAN for project networking. Some instances successfully DHCP, some don't. For those that don't: compute: 11:51:24.926581 IP

[Kernel-packages] [Bug 1853592] UdevDb.txt

apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1853592/+attachment/5307086/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1853592] CRDA.txt

apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1853592/+attachment/5307079/+files/CRDA.txt -- 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/1853592

[Kernel-packages] [Bug 1851819] ProcModules.txt

apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1851819/+attachment/5307072/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1851819] CurrentDmesg.txt

apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1851819/+attachment/5307067/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1851819] ProcCpuinfoMinimal.txt

apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1851819/+attachment/5307070/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1851819] ProcInterrupts.txt

apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1851819/+attachment/5307071/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1851819] UdevDb.txt

apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1851819/+attachment/5307073/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1851819] Re: bond: An illegal loopback occurred on slave

apport information ** Tags added: apport-collected ** Description changed: Mellanox ConnectX 5 adapter configured with LACP bonding; adapters in switchdev (offload) mode with VF's configure on both ports. Kernel continually reports: Nov 8 10:57:51 node-laveran kernel: [

[Kernel-packages] [Bug 1851819] ProcCpuinfo.txt

apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1851819/+attachment/5307069/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1851819] WifiSyslog.txt

apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1851819/+attachment/5307074/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which

[Kernel-packages] [Bug 1851819] Lspci.txt

apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1851819/+attachment/5307068/+files/Lspci.txt -- 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/1851819

[Kernel-packages] [Bug 1851819] Re: bond: An illegal loopback occurred on slave

** Package changed: linux-meta-hwe-edge (Ubuntu) => 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/1851819 Title: bond: An illegal loopback occurred on slave Status in

[Kernel-packages] [Bug 1849856] Re: ip commands error with mellanox devices in switchdev mode

FWIW same is seem with the 5.3.0 kernel that's just appeared in HWE edge. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1849856 Title: ip commands

[Kernel-packages] [Bug 1849856] Re: ip commands error with mellanox devices in switchdev mode

@terrykrudd - I think there is a bug here somewhere as the card should support 127 VF's (and 1 PF) per port - setting the firmware to this limit results in this error. I'm not sure whether this problem is in the kernel driver code or in the underlying firmware. -- You received this bug

[Kernel-packages] [Bug 1849856] Re: ip commands error with mellanox devices in switchdev mode

Managed to figure out why this was happening - I had the NUM_VFS in the card firmware configured to 127 (the maximum value) - reducing this to a lower number allowed me to successfully switch the cards into switchdev mode at which point the ip tools all worked again. The clue that pointed to this

[Kernel-packages] [Bug 1849856] Re: ip commands error with mellanox devices in switchdev mode

strace from failing command ** Attachment added: "strace-iplink.txt" https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+attachment/5300860/+files/strace-iplink.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to

[Kernel-packages] [Bug 1849856] Re: ip commands error with mellanox devices in switchdev mode

Also tried with the iproute2 in bionic-backports - same result -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1849856 Title: ip commands error with

[Kernel-packages] [Bug 1849856] [NEW] ip commands error with mellanox devices in switchdev mode

Public bug reported: Kernel: using 5.0.0-23-generic from hwe-edge Configuring a mellanox connectx device with configured VF's into switchdev (rather than legacy) mode result in the ip cli tool erroring when trying to query the interface state: $ sudo ip link Error: Buffer too small for object.

[Kernel-packages] [Bug 1834213] Re: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances

Adding a neutron bug-task to get an upstream opinion on whether neutron should be loading these modules as the n-ovs-agent starts up. ** Also affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is

[Kernel-packages] [Bug 1834213] Re: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances

Ignore prior comment: $ lsmod | grep conntrack nf_conntrack_ipv6 20480 1 nf_conntrack_ipv4 16384 1 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 nf_defrag_ipv6 36864 2 nf_conntrack_ipv6,openvswitch nf_conntrack 131072 6

[Kernel-packages] [Bug 1834213] Re: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances

Raising a kernel bug task. Note my testing was on Bionic not Xenial. Drew - can you confirm which kernel version and packages you are using. ** Changed in: charm-neutron-openvswitch Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1823862] Re: disco: unable to use iptables/enable ufw under -virtual kernel

Tested with the kernel+modules linked in #22 I can confirm I was able to enable ufw and query the installed iptables rules: $ uname -a Linux juju-0f0cbd-disco-testing-38 5.0.0-10-generic #11+lp1823862v201904100938 SMP Wed Apr 10 14:40:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ sudo ufw

[Kernel-packages] [Bug 1823862] Re: disco: unable to enable ufw under -virtual kernel

Diff between two identical instances, one with -generic and one with -virtual. iptables* commands working find with -generic. ** Attachment added: "kernel-diff.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862/+attachment/5254621/+files/kernel-diff.txt -- You received this

[Kernel-packages] [Bug 1823862] Re: disco: unable to enable ufw under -virtual kernel

Dropping ufw from the test case - just running sudo iptables-save against the virtual kernel produces no output. -- 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/1823862 Title: disco:

[Kernel-packages] [Bug 1823862] Re: disco: unable to enable ufw under -virtual kernel

This might have some implications for fan usage on cloud instances as I see some fan-* rules post switch to generic kernel. -- 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/1823862 Title:

[Kernel-packages] [Bug 1823862] Re: disco: unable to enable ufw

OK I think I've figured it out; the cloud images use the -virtual kernel, which does not install linux-modules-extra-*. If I install the -generic kernel or just the extra modules and reboot, then iptables commands start working again. ** Changed in: ufw (Ubuntu) Status: Incomplete => New

[Kernel-packages] [Bug 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386

@juergh ok I'll propose a hint for disco them! -- 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/1813244 Title: systemd cause kernel trace "BUG: unable to handle kernel paging request at

[Kernel-packages] [Bug 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386

@arighi - will this fix go into disco soon? I have an OVS upload for a high fix blocked on failing tests on i386 - just need to know whether to update the hinter or wait for the fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux

[Kernel-packages] [Bug 1806015] [NEW] bcache: performance regression without tuning under bionic

Public bug reported: Whilst diagnosing a disk performance issue on our QA cloud, I did some performance testing of bcache fronted spindles to compare xenial (4.4 kernel) and bionic (4.14 kernel) installs on the same hardware. A vanilla install (with no tuning of bcache configuration) resulted in

[Kernel-packages] [Bug 1806015] Re: bcache: performance regression without tuning under bionic

Script used to tune bcache devices ** Attachment added: "tune-bcache" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806015/+attachment/5217652/+files/tune-bcache ** Description changed: Whilst diagnosing a disk performance issue on our QA cloud, I did some performance testing of

[Kernel-packages] [Bug 1773165] Re: openvswitch-datapath-dkms kernel module is not getting loaded

fwiw the 4.4 intree openvswitch module is recent and up-to-date so use of a ovs supplied dkms module should not be required. -- 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/1773165 Title:

[Kernel-packages] [Bug 1773165] Re: openvswitch-datapath-dkms kernel module is not getting loaded

Where is the openvswitch-switch-dkms package coming from? I don't recognise the package version as anything that's being shipped in Ubuntu? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

** Changed in: openvswitch (Ubuntu) Importance: Undecided => Wishlist ** Changed in: openvswitch (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu.

[Kernel-packages] [Bug 1766543] Re: instance deletion takes a while and blocks nova-compute

Raising a task for the kernel for an opinion on how to triage this problem further; Marking the nova task as Medium but leaving as New for now until we figure out what's going on - this is not a show stopped but is a pain. ** Also affects: linux (Ubuntu) Importance: Undecided Status:

[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

** Changed in: cloud-archive/queens Status: Fix Committed => 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/1742505 Title: gre_sys set to default 1472 when using

[Kernel-packages] [Bug 1737033] Re: upgrading linux-image package to 4.4.0-103.126 breaks Ceph network file system connection

** Changed in: ceph (Ubuntu) Status: Confirmed => Invalid ** Changed in: ceph (Ubuntu Xenial) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

This bug was fixed in the package openvswitch - 2.8.1-0ubuntu0.17.10.2~cloud0 --- openvswitch (2.8.1-0ubuntu0.17.10.2~cloud0) xenial-pike; urgency=medium . * New update for the Ubuntu Cloud Archive. . openvswitch (2.8.1-0ubuntu0.17.10.2) artful; urgency=medium . *

[Kernel-packages] [Bug 1742505] Update Released

The verification of the Stable Release Update for openvswitch has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update

[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

successfully tested with bug 1743746 ** Tags removed: verification-needed-artful verification-queens-needed ** Tags added: verification-done-artful verification-queens-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1743746] Re: 4.13: unable to increase MTU configuration for GRE devices

LGTM to artful-proposed: 15: gre_sys@NONE: mtu 65000 qdisc pfifo_fast master ovs-system state UNKNOWN mode DEFAULT group default qlen 1000 link/ether 92:92:4d:84:14:1d brd ff:ff:ff:ff:ff:ff $ lsb_release -a No LSB modules are available. Distributor ID:

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

Marking OVS tasks as invalid as we think this issue is in the kernel. ** Changed in: openvswitch (Ubuntu Artful) Status: Confirmed => Invalid ** Changed in: openvswitch (Ubuntu Bionic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of

[Kernel-packages] [Bug 1742505] Please test proposed package

Hello David, or anyone else affected, Accepted openvswitch into queens-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

@Joseph Any update on your bisecting? -- 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/1736390 Title: openvswitch: kernel oops destroying interfaces on i386 Status in linux package in

[Kernel-packages] [Bug 1743746] Re: 4.13: unable to increase MTU configuration for GRE devices

Appreciate the kernel team has been pretty busy the last few months; is there an ETA on when this fix might make it into the 4.13 kernels? I know we've pushed the HWE kernel version forward for xenial - so any OpenStack deployments using HWE with GRE tunnels will hit this problem. -- You

[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

Tested OK on Xenial with Pike UCA: 16: gre_sys@NONE: mtu 65000 qdisc pfifo_fast master ovs-system state UNKNOWN mode DEFAULT group default qlen 1000 link/ether 56:5c:6e:19:f5:4b brd ff:ff:ff:ff:ff:ff However testing on artful currently blocked pending

[Kernel-packages] [Bug 1742505] Please test proposed package

Hello David, or anyone else affected, Accepted openvswitch into pike-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo

[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

I've uploaded the fixes for this issue to bionic (currently in proposed awaiting builds across all archs) and for artful (stacked ontop of the current 2.8.1 stable release in proposed). I'd like todo this fix ontop of the 2.8.1 release, rather than have end- users deal with two sets of updates

[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

Leaving the kernel bug tasks open for now; there is an underlying issue in the kernel specific to GRE tunnel ports where the MTU passed during new device creation is not being used; the fixes to OVS workaround this issue rather than actually resolving it. ** Description changed: + [Impact] +

[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

I've re-tested with the proposed changes upstream; MTU is correctly set to 65000 for all tunnel types including GRE on 4.4 kernels; the kernel fix for bug 1743746 is required for support on >= Artful or if the HWE edge kernel is in use on Xenial. -- You received this bug notification because you

[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

Test packages for Artful and Xenial in: ppa:james-page/pike -- 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/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with

[Kernel-packages] [Bug 1743746] Re: 4.13: unable to increase MTU configuration for GRE devices

Hi Joseph I reconfirmed the bug on the current artful kernel, upgraded to your test kernel and I can confirm that the test kernel resolves the issue: 7: gre_sys@NONE: mtu 65000 qdisc pfifo_fast master ovs-system state UNKNOWN mode DEFAULT group default qlen

[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

Reference bug 1743746 for MTU hardware limitation in 4.13 kernel -- 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/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500

[Kernel-packages] [Bug 1743746] Re: 4.13: unable to increase MTU configuration for GRE devices

** 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/1743746 Title: 4.13: unable to increase MTU configuration for GRE

[Kernel-packages] [Bug 1743746] Re: 4.13: unable to increase MTU configuration for GRE devices

** Description changed: + [Impact] + GRE overlay networks can't carry traffic with MTU > 1500 + + [Test Case] + + [Regression Potential] + + + [Bug Report] + Under Linux 4.13 its not possible to configure GRE tunnel devices with a MTU larger than 1500; this impacts on Open vSwitch (which

[Kernel-packages] [Bug 1743746] [NEW] 4.13: unable to increase MTU configuration for GRE devices

Public bug reported: [Impact] GRE overlay networks can't carry traffic with MTU > 1500 [Test Case] [Regression Potential] [Bug Report] Under Linux 4.13 its not possible to configure GRE tunnel devices with a MTU larger than 1500; this impacts on Open vSwitch (which creates tunnel devices for

[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

Simple reproducer: sudo add-apt-repository cloud-archive:pike sudo apt update sudo apt install openvswitch-switch sudo ovs-vsctl add-br br-tun sudo ovs-vsctl add-port br-tun gre0 -- set interface gre0 type=gre options:remote_ip=10.100.1.1 this will cause ovs to create the gre_sys device in the

[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

ovs-dev ML thread: https://mail.openvswitch.org/pipermail/ovs-dev/2018-January/343069.html -- 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/1742505 Title: gre_sys set to default 1472

[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

Mirroring some of the thread on the ovs dev ML: >From Christina "Thanks Eric, that matches my findings, glad that there seems to be an accepted fix already. But it is fairly recent and only in since 4.15-rc8 levels afaik. But OTOH its description at [1] reads pretty much like my notes so far.

[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

Marking kernel tasks as confirmed as we have at least one related bug which we have confirmed is fixed under 4.15 (and looks like an easy pick for 4.13). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1742505 Title: gre_sys set to default 1472 when using path_mtu

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386

Thanks Greg Joseph - would it be possible to get a 4.13 kernel prepared with the patch identified picked? -- 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/1736390 Title: openvswitch:

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386

Looking at the test history - artful passed tests with 4.11 and 4.12 kernels with 2.8.0, but appears to have started failing sporadically when 4.13 entered the archive. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386

I don't have a data point for 4.11, but at 4.10 (as shipped in zesty) ovs 2.8.1 tests are OK. -- 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/1736390 Title: openvswitch: kernel opps

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386

root 16037 1 0 12:39 ?00:00:00 ovsdb-server: monitoring pid 16038 (healthy) root 16038 16037 0 12:39 ?00:00:00 ovsdb-server /etc/openvswitch/conf.db -vconsole:emer -vsyslog:err -vfile:info --remote=punix:/var/run/openvswitch/db.sock --private-key=db:Open_vSwitch

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386

More log output from ovs: 2017-12-13T12:40:23.502Z|5|dpif(revalidator20)|WARN|system@ovs-system: failed to put[modify] (Invalid argument) ufid:684991e8-860e-44eb-ab44-bd8bd41520e1

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386

And some more testing: xenial: ovs 2.8.1 + 4.4 - OK xenial: ovs 2.8.1 + 4.10 - OK so the issue appears to be the combination of ovs 2.8.1 (and 2.8.0) with the 4.13 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386

[ 118.059308] BUG: unable to handle kernel NULL pointer dereference at (null) [ 118.065034] IP: rtmsg_ifa+0x2d/0xe0 [ 118.065744] *pdpt = 3434e001 *pde = [ 118.067166] Oops: [#1] SMP [ 118.067863] Modules linked in: veth openvswitch nf_conntrack_ipv6

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386

And some more testing xenial: ovs 2.5.2 + 4.4/4.10/4.13 - OK xenial: ovs 2.8.1 + 4.13 - FAIL so maybe this is something that ovs is doing that's breaking the kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386

Testing with the mainline kernel I don't even get as far as the original error - the instance I'm testing with locks up as soon as the performance test is executed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

  1   2   3   >