[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 nf_conntrack_ipv6,nf_conntrack_ipv4,nf_nat,nf_nat_ipv6,nf_nat_ipv4,openvswitch libcrc32c 16384 5 nf_conntrack,nf_nat,openvswitch,xfs,raid456 as soon as a loaded the openvswitch kernel module the nf_conntrack_* modules where loaded as well. ** Changed in: charm-neutron-openvswitch Status: New => Incomplete ** 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/1834213 Title: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances Status in OpenStack neutron-openvswitch charm: Incomplete Status in linux package in Ubuntu: New Bug description: With an environment running Xenial-Queens, and having just upgraded the linux-image-generic kernel for MDS patching, a few of our hypervisor hosts that were rebooted (3 out of 100) ended up dropping IP (tcp/udp) ingress traffic. It turns out that nf_conntrack module was loaded, but nf_conntrack_ipv4 was not loading, and the traffic was being dropped by this rule: table=72, n_packets=214989, priority=50,ct_state=+inv+trk actions=resubmit(,93) The ct_state "inv" means invalid conntrack state, which the manpage describes as: The state is invalid, meaning that the connection tracker couldn’t identify the connection. This flag is a catch- all for problems in the connection or the connection tracker, such as: • L3/L4 protocol handler is not loaded/unavailable. With the Linux kernel datapath, this may mean that the nf_conntrack_ipv4 or nf_conntrack_ipv6 modules are not loaded. • L3/L4 protocol handler determines that the packet is malformed. • Packets are unexpected length for protocol. It appears that there may be an issue when patching the OS of a hypervisor not running instances may fail to update initrd to load nf_conntrack_ipv4 (and/or _ipv6). I couldn't find anywhere in the charm code that this would be loaded unless the charm's "harden" option is used on nova-compute charm (see charmhelpers contrib/host templates). It is unset in our environment, so we are not using any special module probing. Did nf_conntrack_ipv4 get split out from nf_conntrack in recent kernel upgrades or is it possible that the charm should define a modprobe file if we have the OVS firewall driver configured? To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1834213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834213 Title: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances Status in OpenStack neutron-openvswitch charm: Incomplete Status in linux package in Ubuntu: New Bug description: With an environment running Xenial-Queens, and having just upgraded the linux-image-generic kernel for MDS patching, a few of our hypervisor hosts that were rebooted (3 out of 100) ended up dropping IP (tcp/udp) ingress traffic. It turns out that nf_conntrack module was loaded, but nf_conntrack_ipv4 was not loading, and the traffic was being dropped by this rule: table=72, n_packets=214989, priority=50,ct_state=+inv+trk actions=resubmit(,93) The ct_state "inv" means invalid conntrack state, which the manpage describes as: The state is invalid, meaning that the connection tracker couldn’t identify the connection. This flag is a catch- all for problems in the connection or the connection tracker, such as: • L3/L4 protocol handler is not loaded/unavailable. With the Linux kernel datapath, this may mean that the nf_conntrack_ipv4 or nf_conntrack_ipv6 modules are not loaded. • L3/L4 protocol handler determines that the packet is malformed. • Packets are unexpected length for protocol. It appears that there may be an issue when patching the OS of a hypervisor not running instances may fail to update initrd to load nf_conntrack_ipv4 (and/or _ipv6). I couldn't find anywhere in the charm code that this would be loaded unless the charm's "harden" option is used on nova-compute charm (see charmhelpers contrib/host templates). It is unset in our environment, so we are not using any special module probing. Did nf_conntrack_ipv4 get split out from nf_conntrack in recent kernel upgrades or is it possible that the charm should define a modprobe file if we have the OVS firewall driver configured? To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1834213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 in Ubuntu. https://bugs.launchpad.net/bugs/1813244 Title: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386 Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: SRU Justification: [Impact] * Flow action buffer can be incorrectly resized to contain the newly added action entries: the buffer is always resized multiplying the previous size by 2, but this might be not enough if the requested size is bigger than previous_size*2, causing a buffer overflow * The fix correctly resizes the buffer to prevent the buffer overflow * Despite the subject this bug can be triggered potentially on any architecture, but it is very likely to happen on i386 running the following test case [Test Case] * run this openvswitch test case: https://launchpadlibrarian.net/416589265/lp1262692 [Fix] * Instead of resizing the buffer by a factor of 2, use max(current_size * 2, current_size + requested_size) [Regression Potential] * Fix has been tested on the affected platform and verified using slub_debug. The patch has been queued up for -stable by David Miller, it will be included upstream for the next merge window. It is also a very small patch (a one-liner basically), so backport changes are minimal. [Original bug report] This issue was found after leaving a SUT to run overnight (was testing the ubuntu_cts_kernel test 13 hours ago before this happens). Can't tell if this is a regression, as I haven't find a way to reproduce it. But I do see similar reports on the Internet [1] After checking the systemd service timers, it looks like this is caused by the logrotate.service: $ sudo systemctl list-timers --all NEXT LEFT LAST PASSEDUNIT ACTIVATES Fri 2019-01-25 06:18:58 UTC 1h 40min left Thu 2019-01-24 06:34:15 UTC 22h ago apt-daily-upgrade.timer apt-daily-upgrade.service Fri 2019-01-25 09:15:54 UTC 4h 37min left Fri 2019-01-25 03:43:24 UTC 55min ago apt-daily.timer apt-daily.service Fri 2019-01-25 17:02:47 UTC 12h left Fri 2019-01-25 04:20:17 UTC 18min ago motd-news.timer motd-news.service Sat 2019-01-26 00:00:00 UTC 19h left Fri 2019-01-25 00:00:37 UTC 4h 38min ago logrotate.timer logrotate.service Sat 2019-01-26 04:02:38 UTC 23h left Fri 2019-01-25 04:02:38 UTC 36min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv Mon 2019-01-28 00:00:00 UTC 2 days left Wed 2019-01-23 10:44:18 UTC 1 day 17h ago fstrim.timer fstrim.service n/a n/a n/a n/a snapd.snap-repair.timer snapd.snap-repair.service 7 timers listed. After this happens, you won't be able to reboot it with the command. $ sudo reboot sudo: unable to resolve host onza: Resource temporarily unavailable Killed Here is the error message, please refer to the attachment for a complete syslog: Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files... Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel paging request at 6db23a14 Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = Jan 25 00:00:37 onza kernel: [45282.968650] Oops: [#1] SMP Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240 Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 3f 01 Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 350d EDX: 350c Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP: f461fd9c ESP: f461fd74 Jan 25 00:00:37 onza kernel: [45283.024304] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010206 Jan 25 00:00:37 onza kernel: [45283.031245] CR0: 80050033 CR2: 6db23a14 CR3: 29d304a0 CR4: 06f0 Jan 25 00:00:37 onza kernel: [45283.037770] Call Trace: Jan 25 00:00:37 onza kernel: [45283.040395] ? ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.045255] ext4_htree_stor
[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 6db23a14" on Cosmic i386 Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: SRU Justification: [Impact] * Flow action buffer can be incorrectly resized to contain the newly added action entries: the buffer is always resized multiplying the previous size by 2, but this might be not enough if the requested size is bigger than previous_size*2, causing a buffer overflow * The fix correctly resizes the buffer to prevent the buffer overflow * Despite the subject this bug can be triggered potentially on any architecture, but it is very likely to happen on i386 running the following test case [Test Case] * run this openvswitch test case: https://launchpadlibrarian.net/416589265/lp1262692 [Fix] * Instead of resizing the buffer by a factor of 2, use max(current_size * 2, current_size + requested_size) [Regression Potential] * Fix has been tested on the affected platform and verified using slub_debug. The patch has been queued up for -stable by David Miller, it will be included upstream for the next merge window. It is also a very small patch (a one-liner basically), so backport changes are minimal. [Original bug report] This issue was found after leaving a SUT to run overnight (was testing the ubuntu_cts_kernel test 13 hours ago before this happens). Can't tell if this is a regression, as I haven't find a way to reproduce it. But I do see similar reports on the Internet [1] After checking the systemd service timers, it looks like this is caused by the logrotate.service: $ sudo systemctl list-timers --all NEXT LEFT LAST PASSEDUNIT ACTIVATES Fri 2019-01-25 06:18:58 UTC 1h 40min left Thu 2019-01-24 06:34:15 UTC 22h ago apt-daily-upgrade.timer apt-daily-upgrade.service Fri 2019-01-25 09:15:54 UTC 4h 37min left Fri 2019-01-25 03:43:24 UTC 55min ago apt-daily.timer apt-daily.service Fri 2019-01-25 17:02:47 UTC 12h left Fri 2019-01-25 04:20:17 UTC 18min ago motd-news.timer motd-news.service Sat 2019-01-26 00:00:00 UTC 19h left Fri 2019-01-25 00:00:37 UTC 4h 38min ago logrotate.timer logrotate.service Sat 2019-01-26 04:02:38 UTC 23h left Fri 2019-01-25 04:02:38 UTC 36min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv Mon 2019-01-28 00:00:00 UTC 2 days left Wed 2019-01-23 10:44:18 UTC 1 day 17h ago fstrim.timer fstrim.service n/a n/a n/a n/a snapd.snap-repair.timer snapd.snap-repair.service 7 timers listed. After this happens, you won't be able to reboot it with the command. $ sudo reboot sudo: unable to resolve host onza: Resource temporarily unavailable Killed Here is the error message, please refer to the attachment for a complete syslog: Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files... Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel paging request at 6db23a14 Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = Jan 25 00:00:37 onza kernel: [45282.968650] Oops: [#1] SMP Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240 Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 3f 01 Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 350d EDX: 350c Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP: f461fd9c ESP: f461fd74 Jan 25 00:00:37 onza kernel: [45283.024304] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010206 Jan 25 00:00:37 onza kernel: [45283.031245] CR0: 80050033 CR2: 6db23a14 CR3: 29d304a0 CR4: 06f0 Jan 25 00:00:37 onza kernel: [45283.037770] Call Trace: Jan 25 00:00:37 onza kernel: [45283.040395] ? ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.045255] ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.049951] htree_dirblock_to_tree+0xd2/0x230 Jan 25 00:00:37 onza kernel: [452
[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 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - disco: unable to enable ufw + disco: unable to enable ufw under -virtual 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: disco: unable to enable ufw under -virtual kernel Status in linux package in Ubuntu: New Status in ufw package in Ubuntu: New Bug description: Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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: disco: unable to enable ufw under -virtual kernel Status in linux package in Ubuntu: Incomplete Status in ufw package in Ubuntu: New Bug description: Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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: unable to enable ufw under -virtual kernel Status in linux package in Ubuntu: Incomplete Status in ufw package in Ubuntu: New Bug description: Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 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: unable to enable ufw under -virtual kernel Status in linux package in Ubuntu: Incomplete Status in ufw package in Ubuntu: New Bug description: Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y Firewall is active and enabled on system startup $ sudo iptables-save # Generated by iptables-save v1.6.1 on Wed Apr 10 16:15:01 2019 *filter :INPUT DROP [0:0] :FORWARD DROP [0:0] :OUTPUT ACCEPT [0:0] :ufw-after-forward - [0:0] :ufw-after-input - [0:0] :ufw-after-logging-forward - [0:0] :ufw-after-logging-input - [0:0] :ufw-after-logging-output - [0:0] :ufw-after-output - [0:0] :ufw-before-forward - [0:0] :ufw-before-input - [0:0] :ufw-before-logging-forward - [0:0] :ufw-before-logging-input - [0:0] :ufw-before-logging-output - [0:0] :ufw-before-output - [0:0] :ufw-logging-allow - [0:0] :ufw-logging-deny - [0:0] :ufw-not-local - [0:0] :ufw-reject-forward - [0:0] :ufw-reject-input - [0:0] :ufw-reject-output - [0:0] :ufw-skip-to-policy-forward - [0:0] :ufw-skip-to-policy-input - [0:0] :ufw-skip-to-policy-output - [0:0] :ufw-track-forward - [0:0] :ufw-track-input - [0:0] :ufw-track-output - [0:0] :ufw-user-forward - [0:0] :ufw-user-input - [0:0] :ufw-user-limit - [0:0] :ufw-user-limit-accept - [0:0] :ufw-user-logging-forward - [0:0] :ufw-user-logging-input - [0:0] :ufw-user-logging-output - [0:0] :ufw-user-output - [0:0] -A INPUT -j ufw-before-logging-input -A INPUT -j ufw-before-input -A INPUT -j ufw-after-input -A INPUT -j ufw-after-logging-input -A INPUT -j ufw-reject-input -A INPUT -j ufw-track-input -A FORWARD -j ufw-before-logging-forward -A FORWARD -j ufw-before-forward -A FORWARD -j ufw-after-forward -A FORWARD -j ufw-after-logging-forward -A FORWARD -j ufw-reject-forward -A FORWARD -j ufw-track-forward -A OUTPUT -j ufw-before-logging-output -A OUTPUT -j ufw-before-output -A OUTPUT -j ufw-after-output -A OUTPUT -j ufw-after-logging-output -A OUTPUT -j ufw-reject-output -A OUTPUT -j ufw-track-output -A ufw-after-input -p udp -m udp --dport 137 -j ufw-skip-to-policy-input -A ufw-after-input -p udp -m udp --dport 138 -j ufw-skip-to-policy-input -A ufw-after-input -p tcp -m tcp --dport 139 -j ufw-skip-to-policy-input -A ufw-after-input -p tcp -m tcp --dport 445 -j ufw-skip-to-policy-input -A ufw-after-input -p udp -m udp --dport 67 -j ufw-skip-to-policy-input -A ufw-after-input -p udp -m udp --dport 68 -j ufw-skip-to-policy-input -A ufw-after-input -m addrtype --dst-type BROADCAST -j ufw-skip-to-policy-input -A ufw-after-logging-forward -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix "[UFW BLOCK] " -A ufw-after-logging-input -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix "[UFW BLOCK] " -A ufw-before-forward -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A ufw-before-forward -p icmp -m icmp --icmp-type 3 -j ACCEPT -A ufw-before-forward -p icmp -m icmp --icmp-type 11 -j ACCEPT -A ufw-before-forward -p icmp -m icmp --icmp-type 12 -j ACCEPT -A ufw-before-forward -p icmp -m icmp --icmp-type 8 -j ACCEPT -A ufw-before-forward -j ufw-user-forward -A ufw-before-input -i lo -j ACCEPT -A ufw-before-input -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A ufw-before-input -m conntrack --ctstate INVALID -j ufw-logging-deny -A ufw-before-input -m conntrack --ctstate INVALID -j DROP -A ufw-before-input -p icmp -m icmp --icmp-type 3 -j ACCEPT -A ufw-before-input -p icmp -m icmp --icmp-type 11 -j ACCEPT -A ufw-before-input -p icmp -m icmp --icmp-type 12 -j ACCEPT -A ufw-before-input -p icmp -m icmp --icmp-type 8 -j ACCEPT -A ufw-before-input -p udp -m udp --sport 67 --dport 68 -j ACCEPT -A ufw-before-input -j ufw-not-local -A ufw-before-input -d 224.0.0.251/32 -p udp -m udp --dport 5353 -j ACCEPT -A ufw-before-input -d 239.255.255.250/32 -p udp -m udp --dport 1900 -j ACCEPT -A ufw-before-input -j ufw-user-input -A ufw-before-output -o lo -j ACCEPT -A ufw-before-output -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A ufw-before-output -j ufw-user-output -A ufw-logging-allow -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix "[UFW ALLOW] " -A ufw-logging-deny -m conntrack --ctstate INVALID -m limit --limit 3/min --limit-burst 10 -j RETURN -A ufw-logging-deny -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix "[UFW BLOCK] " -A ufw-not-local -m addrtype --dst-type LOCAL -j RETURN -A ufw-not-local -m addrtype --dst-type MULTICAST -j RETURN -A ufw-not-local -m addrtype --dst-type BROADCAST -j RETURN -A ufw-not-local -m limit --limit 3/min --limit-burst 10 -j ufw-logging-deny -A ufw-not-local -j DROP -A ufw-skip-to-policy-forward -j DROP -A ufw-skip-to-policy-input -j DROP -A ufw-skip-to-policy-output -j ACCEPT -A ufw-track-output -p tcp -m conntrack --ctstate NEW -j ACCEPT -A ufw-track-output -p udp -m conntrack --ctstate NEW -j ACCEPT -A ufw-user-limit -m limit --limit 3/min -j LOG --log-p
[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. https://bugs.launchpad.net/bugs/1875863 Title: ceph -- Unable to mount ceph volume on s390x Status in Ubuntu on IBM z Systems: Incomplete Status in ceph package in Ubuntu: Invalid Status in linux package in Ubuntu: New Bug description: When mounting a ceph volume, mount operation fails with an IO error. The problem is always reproducible. Identified potential root cause as kernel endian bug: In the function handle_session() variable @features always contains little endian order of bytes. Just because The feature mask sent by the MDS is little-endian (bits are packed bytewise from left to right in encode_supported_features()). However, test_bit(), called to check features availability, assumes the host order of bytes in that variable. This leads to problems on big endian architectures. Specifically it is impossible to mount ceph volume on s390. A fixup was proposed to convert little-endian order of bytes to the host one. That fixup was modified by ceph maintainers to use existing unpacking means for the conversion. The resulted patch attached. Related discussion in the ceph-development mailing list: https://marc.info/?l=ceph-devel&m=158815357301332&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1875863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 in: charm-nova-compute Status: Triaged => Invalid -- 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/1815844 Title: iscsi multipath dm-N device only used on first volume attachment Status in OpenStack nova-compute charm: Invalid Status in OpenStack Compute (nova): Invalid Status in os-brick: Invalid Status in linux package in Ubuntu: New Bug description: With nova-compute from cloud:xenial-queens and use-multipath=true iscsi multipath is configured and the dm-N devices used on the first attachment but subsequent attachments only use a single path. The back-end storage is a Purestorage array. The multipath.conf is attached The issue is easily reproduced as shown below: jog@pnjostkinfr01:~⟫ openstack volume create pure2 --size 10 --type pure +-+--+ | Field | Value| +-+--+ | attachments | [] | | availability_zone | nova | | bootable| false| | consistencygroup_id | None | | created_at | 2019-02-13T23:07:40.00 | | description | None | | encrypted | False| | id | e286161b-e8e8-47b0-abe3-4df411993265 | | migration_status| None | | multiattach | False| | name| pure2| | properties | | | replication_status | None | | size| 10 | | snapshot_id | None | | source_volid| None | | status | creating | | type| pure | | updated_at | None | | user_id | c1fa4ae9a0b446f2ba64eebf92705d53 | +-+--+ jog@pnjostkinfr01:~⟫ openstack volume show pure2 ++--+ | Field | Value| ++--+ | attachments| [] | | availability_zone | nova | | bootable | false| | consistencygroup_id| None | | created_at | 2019-02-13T23:07:40.00 | | description| None | | encrypted | False| | id | e286161b-e8e8-47b0-abe3-4df411993265 | | migration_status | None | | multiattach| False| | name | pure2| | os-vol-host-attr:host | cinder@cinder-pure#cinder-pure | | os-vol-mig-status-attr:migstat | None | | os-vol-mig-status-attr:name_id | None | | os-vol-tenant-attr:tenant_id | 9be499fd1eee48dfb4dc6faf3cc0a1d7 | | properties | | | replication_status | None | | size | 10 | | snapshot_id| None | | source_volid | None | | status | available| | type | pure | | updated_at | 2019-02-13T23:07:41.00 | | user_id| c1fa4ae9a0b446f2ba64eebf92705d53 | ++--+ Add the volume to an instance: jog@pnjostkinfr01:~⟫ openstack serv
[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. https://bugs.launchpad.net/bugs/1851819 Title: bond: An illegal loopback occurred on slave Status in linux package in Ubuntu: Confirmed Bug description: 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: [ 2087.912308] bond1: (slave enp3s0f0): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.912308] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] bond1: (slave enp3s0f1): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic-hwe-18.04-edge 5.3.0.19.85 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 8 10:54:32 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 12:09:42.042338 IP 172.16.0.2.bootps > 172.16.3.231.bootpc: BOOTP/DHCP, Reply, length 328 12:09:42.042673 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:2d:b5:eb (oui Unknown), length 309 12:09:42.155942 IP6 :: > ff02::1:ff2d:b5eb: ICMP6, neighbor solicitation, who has fe80::f816:3eff:fe2d:b5eb, length 32 12:09:42.207925 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 12:09:43.167942 IP6 fe80::f816:3eff:fe2d:b5eb > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 12:09:43.170786 IP6 fe80::f816:3eff:fe2d:b5eb > ip6-allrouters: ICMP6, router solicitation, length 16 12:09:43.202982 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:2d:b5:eb (oui Unknown), length 309 12:09:43.679928 IP6 fe80::f816:3eff:fe2d:b5eb > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 12:09:46.934638 IP6 fe80::f816:3eff:fe2d:b5eb > ip6-allrouters: ICMP6, router solicitation, length 16 12:09:47.575319 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:2d:b5:eb (oui Unknown), length 309 REQUEST/REPLY is seen - however the REPLY must never get to the VM. As the REPLY is unicast, that gets pushed to an offloaded flow rule so subsequent REPLY packets would not been seen on the hypervisor. -- 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 description: 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 bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP bond1.2925.node-lepaute.maas.55067 > bond1.2925.node-laveran.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 172.16.0.2.bootps > 172.16.2.236.bootpc: BOOTP/DHCP, Reply, length 328 The response is send from the gateway unit to the compute unit, but is never seen in the tcpdump. If hardware encap is disabled on the two underlying ports/the card, traffic flow is seen and all instances correctly DHCP configure on boot. sudo ethtool -K enp3s0f0 hw-tc-offload off sudo ethtool -K enp3s0f1 hw-tc-offload off ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 22 12:29:20 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8
[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 linux package in Ubuntu: New Bug description: 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: [ 2087.912308] bond1: (slave enp3s0f0): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.912308] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] bond1: (slave enp3s0f1): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic-hwe-18.04-edge 5.3.0.19.85 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 8 10:54:32 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 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 description: 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: [ 2087.912308] bond1: (slave enp3s0f0): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.912308] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] bond1: (slave enp3s0f1): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic-hwe-18.04-edge 5.3.0.19.85 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 8 10:54:32 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 Title: bond: An illegal loopback occurred on slave Status in linux package in Ubuntu: Confirmed Bug description: 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: [ 2087.912308] bond1: (slave enp3s0f0): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.912308] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] bond1: (slave enp3s0f1): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic-hwe-18.04-edge 5.3.0.19.85 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 8 10:54:32 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1851819 Title: bond: An illegal loopback occurred on slave Status in linux package in Ubuntu: Confirmed Bug description: 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: [ 2087.912308] bond1: (slave enp3s0f0): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.912308] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] bond1: (slave enp3s0f1): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic-hwe-18.04-edge 5.3.0.19.85 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 8 10:54:32 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1851819 Title: bond: An illegal loopback occurred on slave Status in linux package in Ubuntu: Confirmed Bug description: 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: [ 2087.912308] bond1: (slave enp3s0f0): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.912308] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] bond1: (slave enp3s0f1): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic-hwe-18.04-edge 5.3.0.19.85 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 8 10:54:32 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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: [ 2087.912308] bond1: (slave enp3s0f0): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.912308] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] bond1: (slave enp3s0f1): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic-hwe-18.04-edge 5.3.0.19.85 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 8 10:54:32 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Nov 19 16:45 seq + crw-rw 1 root audio 116, 33 Nov 19 16:45 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 18.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: + Bus 002 Device 002: ID 8087:8002 Intel Corp. + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub + Bus 001 Device 002: ID 8087:800a Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Dell Inc. PowerEdge R630 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen-256color + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: 0 mgag200drmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 + ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-23-generic N/A + linux-backports-modules-5.3.0-23-generic N/A + linux-firmware1.173.12 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic uec-images + Uname: Linux 5.3.0-23-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 11/08/2016 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 2.3.4 + dmi.board.name: 02C2CP + dmi.board.vendor: Dell Inc. + dmi.board.version: A03 + dmi.chassis.type: 23 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: + dmi.product.name: PowerEdge R630 + dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 + dmi.sys.vendor: Dell Inc. ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1851819/+attachment/5307066/+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/1851819 Title: bond: An illegal loopback occurred on slave Status in linux package in Ubuntu: Confirmed Bug description: 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: [ 2087.912308] bond1: (slave enp3s0f0): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.912308] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] bond1: (slave enp3s0f1): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic-hwe-18.04-edge 5.3.0.19.85 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 8 10:54:32 2019 ProcEnviron: TERM=screen-
[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. https://bugs.launchpad.net/bugs/1851819 Title: bond: An illegal loopback occurred on slave Status in linux package in Ubuntu: Confirmed Bug description: 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: [ 2087.912308] bond1: (slave enp3s0f0): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.912308] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] bond1: (slave enp3s0f1): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic-hwe-18.04-edge 5.3.0.19.85 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 8 10:54:32 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1851819 Title: bond: An illegal loopback occurred on slave Status in linux package in Ubuntu: Confirmed Bug description: 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: [ 2087.912308] bond1: (slave enp3s0f0): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.912308] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] bond1: (slave enp3s0f1): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic-hwe-18.04-edge 5.3.0.19.85 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 8 10:54:32 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1851819 Title: bond: An illegal loopback occurred on slave Status in linux package in Ubuntu: Confirmed Bug description: 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: [ 2087.912308] bond1: (slave enp3s0f0): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.912308] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] bond1: (slave enp3s0f1): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic-hwe-18.04-edge 5.3.0.19.85 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 8 10:54:32 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1851819 Title: bond: An illegal loopback occurred on slave Status in linux package in Ubuntu: Confirmed Bug description: 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: [ 2087.912308] bond1: (slave enp3s0f0): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.912308] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] bond1: (slave enp3s0f1): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic-hwe-18.04-edge 5.3.0.19.85 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 8 10:54:32 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1853592 Title: hw-tc-offload not reliable with VXLAN Status in linux package in Ubuntu: New Bug description: 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 bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP bond1.2925.node-lepaute.maas.55067 > bond1.2925.node-laveran.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 172.16.0.2.bootps > 172.16.2.236.bootpc: BOOTP/DHCP, Reply, length 328 The response is send from the gateway unit to the compute unit, but is never seen in the tcpdump. If hardware encap is disabled on the two underlying ports/the card, traffic flow is seen and all instances correctly DHCP configure on boot. sudo ethtool -K enp3s0f0 hw-tc-offload off sudo ethtool -K enp3s0f1 hw-tc-offload off ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 22 12:29:20 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1853592 Title: hw-tc-offload not reliable with VXLAN Status in linux package in Ubuntu: New Bug description: 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 bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP bond1.2925.node-lepaute.maas.55067 > bond1.2925.node-laveran.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 172.16.0.2.bootps > 172.16.2.236.bootpc: BOOTP/DHCP, Reply, length 328 The response is send from the gateway unit to the compute unit, but is never seen in the tcpdump. If hardware encap is disabled on the two underlying ports/the card, traffic flow is seen and all instances correctly DHCP configure on boot. sudo ethtool -K enp3s0f0 hw-tc-offload off sudo ethtool -K enp3s0f1 hw-tc-offload off ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 22 12:29:20 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP bond1.2925.node-lepaute.maas.55067 > bond1.2925.node-laveran.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 172.16.0.2.bootps > 172.16.2.236.bootpc: BOOTP/DHCP, Reply, length 328 The response is send from the gateway unit to the compute unit, but is never seen in the tcpdump. If hardware encap is disabled on the two underlying ports/the card, traffic flow is seen and all instances correctly DHCP configure on boot. sudo ethtool -K enp3s0f0 hw-tc-offload off sudo ethtool -K enp3s0f1 hw-tc-offload off ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 22 12:29:20 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-collected bionic third-party-packages uec-images ** Package changed: linux-signed-hwe-edge (Ubuntu) => linux (Ubuntu) ** Tags added: apport-collected ** Description changed: 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 bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP
[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 Title: hw-tc-offload not reliable with VXLAN Status in linux package in Ubuntu: New Bug description: 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 bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP bond1.2925.node-lepaute.maas.55067 > bond1.2925.node-laveran.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 172.16.0.2.bootps > 172.16.2.236.bootpc: BOOTP/DHCP, Reply, length 328 The response is send from the gateway unit to the compute unit, but is never seen in the tcpdump. If hardware encap is disabled on the two underlying ports/the card, traffic flow is seen and all instances correctly DHCP configure on boot. sudo ethtool -K enp3s0f0 hw-tc-offload off sudo ethtool -K enp3s0f1 hw-tc-offload off ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 22 12:29:20 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1853592 Title: hw-tc-offload not reliable with VXLAN Status in linux package in Ubuntu: New Bug description: 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 bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP bond1.2925.node-lepaute.maas.55067 > bond1.2925.node-laveran.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 172.16.0.2.bootps > 172.16.2.236.bootpc: BOOTP/DHCP, Reply, length 328 The response is send from the gateway unit to the compute unit, but is never seen in the tcpdump. If hardware encap is disabled on the two underlying ports/the card, traffic flow is seen and all instances correctly DHCP configure on boot. sudo ethtool -K enp3s0f0 hw-tc-offload off sudo ethtool -K enp3s0f1 hw-tc-offload off ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 22 12:29:20 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 Title: hw-tc-offload not reliable with VXLAN Status in linux package in Ubuntu: New Bug description: 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 bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP bond1.2925.node-lepaute.maas.55067 > bond1.2925.node-laveran.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 172.16.0.2.bootps > 172.16.2.236.bootpc: BOOTP/DHCP, Reply, length 328 The response is send from the gateway unit to the compute unit, but is never seen in the tcpdump. If hardware encap is disabled on the two underlying ports/the card, traffic flow is seen and all instances correctly DHCP configure on boot. sudo ethtool -K enp3s0f0 hw-tc-offload off sudo ethtool -K enp3s0f1 hw-tc-offload off ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 22 12:29:20 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1853592 Title: hw-tc-offload not reliable with VXLAN Status in linux package in Ubuntu: New Bug description: 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 bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP bond1.2925.node-lepaute.maas.55067 > bond1.2925.node-laveran.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 172.16.0.2.bootps > 172.16.2.236.bootpc: BOOTP/DHCP, Reply, length 328 The response is send from the gateway unit to the compute unit, but is never seen in the tcpdump. If hardware encap is disabled on the two underlying ports/the card, traffic flow is seen and all instances correctly DHCP configure on boot. sudo ethtool -K enp3s0f0 hw-tc-offload off sudo ethtool -K enp3s0f1 hw-tc-offload off ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 22 12:29:20 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1853592 Title: hw-tc-offload not reliable with VXLAN Status in linux package in Ubuntu: New Bug description: 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 bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP bond1.2925.node-lepaute.maas.55067 > bond1.2925.node-laveran.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 172.16.0.2.bootps > 172.16.2.236.bootpc: BOOTP/DHCP, Reply, length 328 The response is send from the gateway unit to the compute unit, but is never seen in the tcpdump. If hardware encap is disabled on the two underlying ports/the card, traffic flow is seen and all instances correctly DHCP configure on boot. sudo ethtool -K enp3s0f0 hw-tc-offload off sudo ethtool -K enp3s0f1 hw-tc-offload off ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 22 12:29:20 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1853592 Title: hw-tc-offload not reliable with VXLAN Status in linux package in Ubuntu: New Bug description: 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 bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP bond1.2925.node-lepaute.maas.55067 > bond1.2925.node-laveran.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 172.16.0.2.bootps > 172.16.2.236.bootpc: BOOTP/DHCP, Reply, length 328 The response is send from the gateway unit to the compute unit, but is never seen in the tcpdump. If hardware encap is disabled on the two underlying ports/the card, traffic flow is seen and all instances correctly DHCP configure on boot. sudo ethtool -K enp3s0f0 hw-tc-offload off sudo ethtool -K enp3s0f1 hw-tc-offload off ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 22 12:29:20 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1853592 Title: hw-tc-offload not reliable with VXLAN Status in linux package in Ubuntu: New Bug description: 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 bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP bond1.2925.node-lepaute.maas.55067 > bond1.2925.node-laveran.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 172.16.0.2.bootps > 172.16.2.236.bootpc: BOOTP/DHCP, Reply, length 328 The response is send from the gateway unit to the compute unit, but is never seen in the tcpdump. If hardware encap is disabled on the two underlying ports/the card, traffic flow is seen and all instances correctly DHCP configure on boot. sudo ethtool -K enp3s0f0 hw-tc-offload off sudo ethtool -K enp3s0f1 hw-tc-offload off ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 22 12:29:20 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 Bug description: 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 bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP bond1.2925.node-lepaute.maas.55067 > bond1.2925.node-laveran.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 172.16.0.2.bootps > 172.16.2.236.bootpc: BOOTP/DHCP, Reply, length 328 The response is send from the gateway unit to the compute unit, but is never seen in the tcpdump. If hardware encap is disabled on the two underlying ports/the card, traffic flow is seen and all instances correctly DHCP configure on boot. sudo ethtool -K enp3s0f0 hw-tc-offload off sudo ethtool -K enp3s0f1 hw-tc-offload off ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 22 12:29:20 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 VXLAN Status in linux package in Ubuntu: Confirmed Bug description: 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 bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP bond1.2925.node-lepaute.maas.55067 > bond1.2925.node-laveran.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 172.16.0.2.bootps > 172.16.2.236.bootpc: BOOTP/DHCP, Reply, length 328 The response is send from the gateway unit to the compute unit, but is never seen in the tcpdump. If hardware encap is disabled on the two underlying ports/the card, traffic flow is seen and all instances correctly DHCP configure on boot. sudo ethtool -K enp3s0f0 hw-tc-offload off sudo ethtool -K enp3s0f1 hw-tc-offload off ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 22 12:29:20 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1853592 Title: hw-tc-offload not reliable with VXLAN Status in linux package in Ubuntu: Confirmed Bug description: 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 bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP bond1.2925.node-lepaute.maas.55067 > bond1.2925.node-laveran.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 172.16.0.2.bootps > 172.16.2.236.bootpc: BOOTP/DHCP, Reply, length 328 The response is send from the gateway unit to the compute unit, but is never seen in the tcpdump. If hardware encap is disabled on the two underlying ports/the card, traffic flow is seen and all instances correctly DHCP configure on boot. sudo ethtool -K enp3s0f0 hw-tc-offload off sudo ethtool -K enp3s0f1 hw-tc-offload off ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 22 12:29:20 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 reliable with VXLAN Status in linux package in Ubuntu: Confirmed Bug description: 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 bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP bond1.2925.node-lepaute.maas.55067 > bond1.2925.node-laveran.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 172.16.0.2.bootps > 172.16.2.236.bootpc: BOOTP/DHCP, Reply, length 328 The response is send from the gateway unit to the compute unit, but is never seen in the tcpdump. If hardware encap is disabled on the two underlying ports/the card, traffic flow is seen and all instances correctly DHCP configure on boot. sudo ethtool -K enp3s0f0 hw-tc-offload off sudo ethtool -K enp3s0f1 hw-tc-offload off ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 22 12:29:20 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 description: 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: [ 2087.912308] bond1: (slave enp3s0f0): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.912308] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] bond1: (slave enp3s0f1): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic-hwe-18.04-edge 5.3.0.19.85 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 8 10:54:32 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 description: 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 bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP bond1.2925.node-lepaute.maas.55067 > bond1.2925.node-laveran.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 172.16.0.2.bootps > 172.16.2.236.bootpc: BOOTP/DHCP, Reply, length 328 The response is send from the gateway unit to the compute unit, but is never seen in the tcpdump. If hardware encap is disabled on the two underlying ports/the card, traffic flow is seen and all instances correctly DHCP configure on boot. sudo ethtool -K enp3s0f0 hw-tc-offload off sudo ethtool -K enp3s0f1 hw-tc-offload off ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 22 12:29:20 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 package in Ubuntu: Confirmed Bug description: 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 bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP bond1.2925.node-lepaute.maas.55067 > bond1.2925.node-laveran.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 172.16.0.2.bootps > 172.16.2.236.bootpc: BOOTP/DHCP, Reply, length 328 The response is send from the gateway unit to the compute unit, but is never seen in the tcpdump. If hardware encap is disabled on the two underlying ports/the card, traffic flow is seen and all instances correctly DHCP configure on boot. sudo ethtool -K enp3s0f0 hw-tc-offload off sudo ethtool -K enp3s0f1 hw-tc-offload off ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 22 12:29:20 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1853592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. Dump terminated ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Fri Oct 25 14:55:36 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- 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 mellanox devices in switchdev mode Status in iproute2 package in Ubuntu: New Bug description: 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. Dump terminated ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Fri Oct 25 14:55:36 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 mellanox devices in switchdev mode Status in iproute2 package in Ubuntu: New Bug description: 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. Dump terminated ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Fri Oct 25 14:55:36 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1849856 Title: ip commands error with mellanox devices in switchdev mode Status in iproute2 package in Ubuntu: New Bug description: 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. Dump terminated ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Fri Oct 25 14:55:36 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 appeared when using the proposed 5.3 hwe edge kernel: [ 694.027106] infiniband (null): mlx5_ib_alloc_counters:5452:(pid 47479): couldn't allocate queue counter for port 128, err -12 (128 being the pertinent value) ** 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 iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1849856 Title: ip commands error with mellanox devices in switchdev mode Status in iproute2 package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: 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. Dump terminated ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Fri Oct 25 14:55:36 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 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 mellanox devices in switchdev mode Status in iproute2 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: 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. Dump terminated ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Fri Oct 25 14:55:36 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 error with mellanox devices in switchdev mode Status in iproute2 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: 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. Dump terminated ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Fri Oct 25 14:55:36 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1853592 Title: hw-tc-offload not reliable with VXLAN Status in linux package in Ubuntu: Confirmed Bug description: 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 bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP bond1.2925.node-lepaute.maas.55067 > bond1.2925.node-laveran.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 172.16.0.2.bootps > 172.16.2.236.bootpc: BOOTP/DHCP, Reply, length 328 The response is send from the gateway unit to the compute unit, but is never seen in the tcpdump. If hardware encap is disabled on the two underlying ports/the card, traffic flow is seen and all instances correctly DHCP configure on boot. sudo ethtool -K enp3s0f0 hw-tc-offload off sudo ethtool -K enp3s0f1 hw-tc-offload off ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 22 12:29:20 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 on slave Status in linux package in Ubuntu: Confirmed Bug description: 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: [ 2087.912308] bond1: (slave enp3s0f0): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.912308] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] bond1: (slave enp3s0f1): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic-hwe-18.04-edge 5.3.0.19.85 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 8 10:54:32 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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, 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 description: 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: [ 2087.912308] bond1: (slave enp3s0f0): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.912308] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] bond1: (slave enp3s0f1): An illegal loopback occurred on slave Nov 8 10:57:51 node-laveran kernel: [ 2087.917329] Check the configuration to verify that all adapters are connected to 802.3ad complian t switch ports ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic-hwe-18.04-edge 5.3.0.19.85 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 8 10:54:32 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834213 Title: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances Status in OpenStack neutron-openvswitch charm: Fix Committed Status in neutron: New Status in linux package in Ubuntu: Confirmed Bug description: With an environment running Xenial-Queens, and having just upgraded the linux-image-generic kernel for MDS patching, a few of our hypervisor hosts that were rebooted (3 out of 100) ended up dropping IP (tcp/udp) ingress traffic. It turns out that nf_conntrack module was loaded, but nf_conntrack_ipv4 was not loading, and the traffic was being dropped by this rule: table=72, n_packets=214989, priority=50,ct_state=+inv+trk actions=resubmit(,93) The ct_state "inv" means invalid conntrack state, which the manpage describes as: The state is invalid, meaning that the connection tracker couldn’t identify the connection. This flag is a catch- all for problems in the connection or the connection tracker, such as: • L3/L4 protocol handler is not loaded/unavailable. With the Linux kernel datapath, this may mean that the nf_conntrack_ipv4 or nf_conntrack_ipv6 modules are not loaded. • L3/L4 protocol handler determines that the packet is malformed. • Packets are unexpected length for protocol. It appears that there may be an issue when patching the OS of a hypervisor not running instances may fail to update initrd to load nf_conntrack_ipv4 (and/or _ipv6). I couldn't find anywhere in the charm code that this would be loaded unless the charm's "harden" option is used on nova-compute charm (see charmhelpers contrib/host templates). It is unset in our environment, so we are not using any special module probing. Did nf_conntrack_ipv4 get split out from nf_conntrack in recent kernel upgrades or is it possible that the charm should define a modprobe file if we have the OVS firewall driver configured? To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1834213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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: New ** Changed in: nova (Ubuntu) Importance: Undecided => Medium -- 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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Incomplete Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Fix Released
Status in clamav package in Ubuntu:
Triaged
Status in controlaula package in Ubuntu:
Invalid
Status in epoptes package in Ubuntu:
New
Status in ethtool package in Ubuntu:
Triaged
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
Won't Fix
Status in ifmetric package in Ubuntu:
Won't Fix
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
Invalid
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
Triaged
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
New
Status in openvpn package in Ubuntu:
New
Status in openvswitch package in Ubuntu:
Triaged
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Released
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
Won't Fix
Status in vzctl package in Ubuntu:
Triaged
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1773165 Title: openvswitch-datapath-dkms kernel module is not getting loaded Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial Kernel version: 4.4.0-127-generic OVS version: 2.7.0 # Issue description openvswitch-datapath-dkms kernelmodule is not getting loaded # Error from dmesg [10863.380564] openvswitch: module verification failed: signature and/or required key missing - tainting kernel [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) #Error from syslog May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not insert 'openvswitch': Exec format error May 24 08:37:06 dev65 openvswitch-switch[18336]: * Inserting openvswitch module #installation logs: Selecting previously unselected package openvswitch-datapath-dkms. (Reading database ... 84707 files and directories currently installed.) Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ... Unpacking openvswitch-datapath-dkms (2.7.0-1) ... Setting up openvswitch-datapath-dkms (2.7.0-1) ... Creating symlink /var/lib/dkms/openvswitch/2.7.0/source -> /usr/src/openvswitch-2.7.0 DKMS: add completed. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area(bad exit status: 2) ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C datapath/linux.. cleaning build area(bad exit status: 2) DKMS: build completed. openvswitch: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-geneve.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-gre.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-lisp.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-stt.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-vxlan.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ depmod DKMS: install completed. #Dpkg status dpkg -l | grep openvswitch ii openvswitch-common 2.7.0-1 amd64Open vSwitch common components ii openvswitch-datapath-dkms2.7.0-1 all Open vSwitch datapath module source - DKMS version ii openvswitch-switch 2.7.0-1 amd64Open vSwitch switch implementations ii python-openvswitch 2.6.1-0ubuntu5.2~cloud0 all Python bindings for Open vSwitch #lsmod status No modules are listing for openvswitch-datapath-dkms #modprobe error modprobe openvswitch modprobe: ERROR: could not insert 'openvswitch': Exec format error --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-127-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[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: openvswitch-datapath-dkms kernel module is not getting loaded Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial Kernel version: 4.4.0-127-generic OVS version: 2.7.0 # Issue description openvswitch-datapath-dkms kernelmodule is not getting loaded # Error from dmesg [10863.380564] openvswitch: module verification failed: signature and/or required key missing - tainting kernel [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) #Error from syslog May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not insert 'openvswitch': Exec format error May 24 08:37:06 dev65 openvswitch-switch[18336]: * Inserting openvswitch module #installation logs: Selecting previously unselected package openvswitch-datapath-dkms. (Reading database ... 84707 files and directories currently installed.) Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ... Unpacking openvswitch-datapath-dkms (2.7.0-1) ... Setting up openvswitch-datapath-dkms (2.7.0-1) ... Creating symlink /var/lib/dkms/openvswitch/2.7.0/source -> /usr/src/openvswitch-2.7.0 DKMS: add completed. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area(bad exit status: 2) ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C datapath/linux.. cleaning build area(bad exit status: 2) DKMS: build completed. openvswitch: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-geneve.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-gre.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-lisp.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-stt.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-vxlan.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ depmod DKMS: install completed. #Dpkg status dpkg -l | grep openvswitch ii openvswitch-common 2.7.0-1 amd64Open vSwitch common components ii openvswitch-datapath-dkms2.7.0-1 all Open vSwitch datapath module source - DKMS version ii openvswitch-switch 2.7.0-1 amd64Open vSwitch switch implementations ii python-openvswitch 2.6.1-0ubuntu5.2~cloud0 all Python bindings for Open vSwitch #lsmod status No modules are listing for openvswitch-datapath-dkms #modprobe error modprobe openvswitch modprobe: ERROR: could not insert 'openvswitch': Exec format error --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-127-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Devi
[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
the following performance metrics (using the sysbench fileio rndrw
benchmark):
Xenial
4 threads:
45.77 MiB/sec read
30.52 MiB/sec write
48 threads (matching core count):
138.72 MiB/sec read
92.52 MiB/sec write
Bionic
4 threads:
29.51 MiB/sec
19.67 MiB/sec
48 threads (matching core count):
41.35 MiB/sec
27.59 MiB/sec
After tuning (disabling the congested_{read|write}_threshold_us and
disabling sequential cutoff)
Xenial
48 threads (matching core count):
153.60 MiB/sec
102.40 MiB/sec
Bionic
48 threads (matching core count):
161.49 MiB/sec
107.67 MiB/sec
suggestion is this might be something todo with the move from deadline to cfq
as the default IO scheduler between 4.4 and 4.13 but as you can see
the baseline vanilla performance is significantly slower.
As a further reference point, the IO performance on the NVMe device
supporting the bcache device is:
4 threads:
554.56 MiB/sec read
369.71 MiB/sec write
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-generic 4.15.0.39.41
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 29 11:38 seq
crw-rw 1 root audio 116, 33 Nov 29 11:38 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Fri Nov 30 10:11:54 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 002: ID 8087:8002 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
Bus 001 Device 002: ID 8087:800a Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. PowerEdge R630
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic
root=UUID=a361a524-47eb-46c3-8a04-e5eaa65188c9 ro hugepages=103117 iommu=pt
intel_iommu=on
RelatedPackageVersions:
linux-restricted-modules-4.15.0-39-generic N/A
linux-backports-modules-4.15.0-39-generic N/A
linux-firmware 1.173.2
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/08/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.3.4
dmi.board.name: 02C2CP
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R630
dmi.sys.vendor: Dell Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: amd64 apport-bug bionic uec-images
--
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/1806015
Title:
bcache: performance regression without tuning under bionic
Status in linux package in Ubuntu:
Confirmed
Bug description:
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
the following performance metrics (using the sysbench fileio rndrw
benchmark):
Xenial
4 threads:
45.77 MiB/sec read
30.52 MiB/sec write
48 threads (matching core count):
138.72 MiB/sec read
92.52 MiB/sec write
Bionic
4 threads:
29.51 MiB/sec
19.67 MiB/sec
48 threads (matching core count):
41.35 MiB/sec
27.59 MiB/sec
After tuning (disabling the congested_{read|write}_threshold_us and
disabling sequential cutoff)
Xenial
48 threads (matching core count):
153.60 MiB/sec
102.40 MiB/sec
Bionic
48 threads (matching core count):
161.49 MiB/sec
107.67 MiB/sec
suggestion is this might be something todo with the move from deadline to cfq
as the default IO scheduler between 4.4 and 4.13 but as you can see
the baseline vanilla performance is significantly slower.
As a further reference point, the IO performance on the NVMe device
supporting the bcache devic
[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 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
the following performance metrics (using the sysbench fileio rndrw
benchmark):
Xenial
4 threads:
- 45.77 MiB/sec read
- 30.52 MiB/sec write
+ 45.77 MiB/sec read
+ 30.52 MiB/sec write
48 threads (matching core count):
- 138.72 MiB/sec read
- 92.52 MiB/sec write
+ 138.72 MiB/sec read
+ 92.52 MiB/sec write
Bionic
4 threads:
- 29.51 MiB/sec
- 19.67 MiB/sec
+ 29.51 MiB/sec
+ 19.67 MiB/sec
48 threads (matching core count):
- 41.35 MiB/sec
- 27.59 MiB/sec
+ 41.35 MiB/sec
+ 27.59 MiB/sec
-
- After tuning (disabling the congested_{read|write}_threshold_us and disabling
sequential cutoff)
+ After tuning (disabling the congested_{read|write}_threshold_us and
+ disabling sequential cutoff)
Xenial
48 threads (matching core count):
- 153.60 MiB/sec
- 102.40 MiB/sec
+ 153.60 MiB/sec
+ 102.40 MiB/sec
Bionic
48 threads (matching core count):
- 161.49 MiB/sec
- 107.67 MiB/sec
+ 161.49 MiB/sec
+ 107.67 MiB/sec
- suggestion is this might be something todo with the move from deadline
- to cfq as the default IO scheduler between 4.4 and 4.13 but as you can
- see the baseline vanilla performance is significantly slower.
+ suggestion is this might be something todo with the move from deadline to cfq
as the default IO scheduler between 4.4 and 4.13 but as you can see
+ the baseline vanilla performance is significantly slower.
+
+ As a further reference point, the IO performance on the NVMe device
+ supporting the bcache device is:
+
+ 4 threads:
+ 554.56 MiB/sec read
+ 369.71 MiB/sec write
+
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-generic 4.15.0.39.41
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
AlsaDevices:
- total 0
- crw-rw 1 root audio 116, 1 Nov 29 11:38 seq
- crw-rw 1 root audio 116, 33 Nov 29 11:38 timer
+ total 0
+ crw-rw 1 root audio 116, 1 Nov 29 11:38 seq
+ crw-rw 1 root audio 116, 33 Nov 29 11:38 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Fri Nov 30 10:11:54 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
- Bus 002 Device 002: ID 8087:8002 Intel Corp.
- Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
- Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
- Bus 001 Device 002: ID 8087:800a Intel Corp.
- Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Bus 002 Device 002: ID 8087:8002 Intel Corp.
+ Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
+ Bus 001 Device 002: ID 8087:800a Intel Corp.
+ Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. PowerEdge R630
PciMultimedia:
-
+
ProcEnviron:
- TERM=xterm-256color
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=
- LANG=C.UTF-8
- SHELL=/bin/bash
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=C.UTF-8
+ SHELL=/bin/bash
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic
root=UUID=a361a524-47eb-46c3-8a04-e5eaa65188c9 ro hugepages=103117 iommu=pt
intel_iommu=on
RelatedPackageVersions:
- linux-restricted-modules-4.15.0-39-generic N/A
- linux-backports-modules-4.15.0-39-generic N/A
- linux-firmware 1.173.2
+ linux-restricted-modules-4.15.0-39-generic N/A
+ linux-backports-modules-4.15.0-39-generic N/A
+ linux-firmware 1.173.2
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/08/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.3.4
dmi.board.name: 02C2CP
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R630
dmi.sys.vendor: Dell Inc.
--
You received this bug notification because you a
[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 4312): failed to allocate command entry [10149.734433] mlx5_core :81:00.1: cmd_work_handler:887:(pid 1339): failed to allocate command entry [10999.729161] mlx5_core :81:00.1: cmd_work_handler:887:(pid 200907): failed to allocate command entry [11016.570130] mlx5_core :81:00.1: cmd_work_handler:887:(pid 4378): failed to allocate command entry [11439.724920] mlx5_core :81:00.0: cmd_work_handler:887:(pid 4377): failed to allocate command entry ** 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/1907086 Title: hardware offloaded PCI devices don't have associated netlink interfaces Status in linux package in Ubuntu: New Status in nova package in Ubuntu: New Bug description: Over time the netlink interfaces for PCI devices of VF's of a Mellanox ConnectX 5 card disappear: # mlnx-switchdev-mode show :61:00.0eno1igb PF :61:00.1eno2igb PF :81:00.0enp129s0f0 mlx5_core PF :81:00.1enp129s0f1 mlx5_core PF :81:02.6enp129s0f0v20 mlx5_core VF of enp129s0f0 :81:03.2enp129s0f0v24 mlx5_core VF of enp129s0f0 # ip link [...] 103: enp129s0f1: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 04:3f:72:9f:35:8c brd ff:ff:ff:ff:ff:ff vf 0 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 1 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 2 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 3 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 4 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 5 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 6 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 7 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 8 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 9 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 10 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 11 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 12 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 13 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 14 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 15 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 16 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 17 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 18 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 19 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 20 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 21 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 22 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 23 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 24 link/ether 00:00:00:00:00:00 brd
[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 8280 WARNING nova.pci.utils [req-3392d882-bd3c-4146-88ab-30c92be51c4d - - - - -] No net device was found for VF :81:04.0: nova.exception.PciDeviceNotFoundById: PCI device :81:04.0 not found 2020-12-07 12:31:56.128 8280 WARNING nova.pci.utils [req-3392d882-bd3c-4146-88ab-30c92be51c4d - - - - -] No net device was found for VF :81:08.5: nova.exception.PciDeviceNotFoundById: PCI device :81:08.5 not found 2020-12-07 12:31:56.129 8280 WARNING nova.pci.utils [req-3392d882-bd3c-4146-88ab-30c92be51c4d - - - - -] No net device was found for VF :81:0a.7: nova.exception.PciDeviceNotFoundById: PCI device :81:0a.7 not found 2020-12-07 12:31:56.130 8280 WARNING nova.pci.utils [req-3392d882-bd3c-4146-88ab-30c92be51c4d - - - - -] No net device was found for VF :81:0b.7: nova.exception.PciDeviceNotFoundById: PCI device :81:0b.7 not found 2020-12-07 12:31:56.132 8280 WARNING nova.pci.utils [req-3392d882-bd3c-4146-88ab-30c92be51c4d - - - - -] No net device was found for VF :81:03.1: nova.exception.PciDeviceNotFoundById: PCI device :81:03.1 not found 2020-12-07 12:31:56.135 8280 WARNING nova.pci.utils [req-3392d882-bd3c-4146-88ab-30c92be51c4d - - - - -] No net device was found for VF :81:0b.6: nova.exception.PciDeviceNotFoundById: PCI device :81:0b.6 not found 2020-12-07 12:31:56.140 8280 WARNING nova.pci.utils [req-3392d882-bd3c-4146-88ab-30c92be51c4d - - - - -] No net device was found for VF :81:01.6: nova.exception.PciDeviceNotFoundById: PCI device :81:01.6 not found 2020-12-07 12:31:56.142 8280 WARNING nova.pci.utils [req-3392d882-bd3c-4146-88ab-30c92be51c4d - - - - -] No net device was found for VF :81:01.3: nova.exception.PciDeviceNotFoundById: PCI device :81:01.3 not found 2020-12-07 12:31:56.143 8280 WARNING nova.pci.utils [req-3392d882-bd3c-4146-88ab-30c92be51c4d - - - - -] No net device was found for VF :81:0b.2: nova.exception.PciDeviceNotFoundById: PCI device :81:0b.2 not found 2020-12-07 12:31:56.148 8280 WARNING nova.pci.utils [req-3392d882-bd3c-4146-88ab-30c92be51c4d - - - - -] No net device was found for VF :81:00.7: nova.exception.PciDeviceNotFoundById: PCI device :81:00.7 not found 2020-12-07 12:31:56.149 8280 WARNING nova.pci.utils [req-3392d882-bd3c-4146-88ab-30c92be51c4d - - - - -] No net device was found for VF :81:00.5: nova.exception.PciDeviceNotFoundById: PCI device :81:00.5 not found 2020-12-07 12:31:56.150 8280 WARNING nova.pci.utils [req-3392d882-bd3c-4146-88ab-30c92be51c4d - - - - -] No net device was found for VF :81:00.3: nova.exception.PciDeviceNotFoundById: PCI device :81:00.3 not found ** Tags added: ps5 -- 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/1907086 Title: hardware offloaded PCI devices don't have associated netlink interfaces Status in linux package in Ubuntu: New Status in nova package in Ubuntu: New Bug description: Over time the netlink interfaces for PCI devices of VF's of a Mellanox ConnectX 5 card disappear: # mlnx-switchdev-mode show :61:00.0eno1igb PF :61:00.1eno2igb PF :81:00.0enp129s0f0 mlx5_core PF :81:00.1enp129s0f1 mlx5_core PF :81:02.6enp129s0f0v20 mlx5_core VF of enp129s0f0 :81:03.2enp129s0f0v24 mlx5_core VF of enp129s0f0 # ip link [...] 103: enp129s0f1: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 04:3f:72:9f:35:8c brd ff:ff:ff:ff:ff:ff vf 0 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 1 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 2 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 3 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 4 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 5 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 6 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 7 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, que
[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. https://bugs.launchpad.net/bugs/1907086 Title: hardware offloaded PCI devices don't have associated netlink interfaces Status in linux package in Ubuntu: Incomplete Status in nova package in Ubuntu: New Bug description: Over time the netlink interfaces for PCI devices of VF's of a Mellanox ConnectX 5 card disappear: # mlnx-switchdev-mode show :61:00.0eno1igb PF :61:00.1eno2igb PF :81:00.0enp129s0f0 mlx5_core PF :81:00.1enp129s0f1 mlx5_core PF :81:02.6enp129s0f0v20 mlx5_core VF of enp129s0f0 :81:03.2enp129s0f0v24 mlx5_core VF of enp129s0f0 # ip link [...] 103: enp129s0f1: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 04:3f:72:9f:35:8c brd ff:ff:ff:ff:ff:ff vf 0 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 1 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 2 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 3 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 4 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 5 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 6 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 7 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 8 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 9 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 10 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 11 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 12 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 13 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 14 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 15 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 16 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 17 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 18 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 19 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 20 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 21 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 22 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 23 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 24 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 25 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 26 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 27 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 28 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof checking off, link-state auto, trust off, query_rss off vf 29 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff, spoof
[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386
Only seen on i386; all other archs pass 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 destroying interfaces on i386 Status in linux package in Ubuntu: New Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386
See the same without proposed (i.e. I don't think its the version of ovs in proposed that's causing this problem). -- 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 destroying interfaces on i386 Status in linux package in Ubuntu: New Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1736390] [NEW] openvswitch: kernel opps destroying interfaces on i386
Public bug reported: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: Reproducable on bionic using the autopkgtest's from openvswitch on i386: - Dec 5 11:41:05 autopkgtest kernel: [ 41.392680] device ovs-system left promiscuous mode - Dec 5 11:41:05 autopkgtest kernel: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) - Dec 5 11:41:05 autopkgtest kernel: [ 41.421000] IP: igmp_group_dropped+0x21/0x220 - Dec 5 11:41:05 autopkgtest kernel: [ 41.421246] *pdpt = 1d62c001 *pde = - Dec 5 11:41:05 autopkgtest kernel: [ 41.421248] - Dec 5 11:41:05 autopkgtest kernel: [ 41.421659] Oops: [#1] SMP - Dec 5 11:41:05 autopkgtest kernel: [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy - Dec 5 11:41:05 autopkgtest kernel: [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu - Dec 5 11:41:05 autopkgtest kernel: [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 - Dec 5 11:41:05 autopkgtest kernel: [ 41.424849] Workqueue: netns cleanup_net - Dec 5 11:41:05 autopkgtest kernel: [ 41.425071] task: db8fba80 task.stack: dba1 - Dec 5 11:41:05 autopkgtest kernel: [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 - Dec 5 11:41:05 autopkgtest kernel: [ 41.425656] EFLAGS: 00010202 CPU: 0 - Dec 5 11:41:05 autopkgtest kernel: [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 - Dec 5 11:41:05 autopkgtest kernel: [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 - Dec 5 11:41:05 autopkgtest kernel: [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 - Dec 5 11:41:05 autopkgtest kernel:
[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386
** 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/1736390 Title: openvswitch: kernel opps destroying interfaces on i386 Status in linux package in Ubuntu: Confirmed Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1737033 Title: upgrading linux-image package to 4.4.0-103.126 breaks Ceph network file system connection Status in ceph package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Status in ceph source package in Xenial: Invalid Status in linux source package in Xenial: Fix Released Bug description: After clients have upgraded to 4.4.0-103.126 they can no longer connect to the Ceph network. Using the Grub menu to boot the previous kernel fixes the issue. The error in dmesg is: [ 46.811897] FS-Cache: Loaded [ 46.843670] Key type ceph registered [ 46.844177] libceph: loaded (mon/osd proto 15/24) [ 46.863107] FS-Cache: Netfs 'ceph' registered for caching [ 46.863116] ceph: loaded (mds proto 32) [ 46.884392] libceph: client3354099 fsid 2efbeab1-4903-4c4c-8365-6778afecbcbd [ 46.886856] libceph: mon0 10.10.2.111:6789 session established [ 46.897487] ceph: problem parsing mds trace -5 [ 46.897491] ceph: mds parse_reply err -5 [ 46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1) All clients are running ceph client version: ii ceph-fs-common10.2.9-0ubuntu0.16.04.1 Server nodes are running 10.2.6 packages as supplied by Ceph. All 10.2.* versions are compatible. Using the previous kernel allows the connection to work. --- ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1310 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=9e3c38ba-10bd-4183-b073-68d9d9a30a9b IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic root=UUID=5a37e891-beb9-477f-b934-3c05651acf68 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-103-generic N/A linux-backports-modules-4.4.0-103-generic N/A linux-firmware 1.157.14 RfKill: Tags: xenial xenial Uname: Linux 4.4.0-103-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1737033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive pike series: Fix Released Status in Ubuntu Cloud Archive queens series: Fix Released Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Fix Released Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: Fix Released Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: Fix Released Bug description: [Impact] OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. [Test Case] Deploy OpenStack Pike (xenial + pike UCA or artful) Create tenant networks using GRE segmentation Boot instances Instance networking will be broken/slow gre_sys devices will be set to mtu=1472 on hypervisor hosts. [Regression Potential] Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 add-apt-repository cloud-archive:pike-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-pike-needed to verification-pike-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-pike-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/pike Status: In Progress => Fix Committed ** Tags added: verification-pike-needed -- 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 ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: Fix Committed Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: Fix Committed Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: [Impact] OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. [Test Case] Deploy OpenStack Pike (xenial + pike UCA or artful) Create tenant networks using GRE segmentation Boot instances Instance networking will be broken/slow gre_sys devices will be set to mtu=1472 on hypervisor hosts. [Regression Potential] Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 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 devices Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] GRE overlay networks can't carry traffic with MTU > 1500 [Test Case] 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 gre_sys device will be configured with MTU 1472. sudo ip link set gre_sys mtu 65000 will fail with EINVAL. [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 GRE overlay networking) and the ip tools. The kernel will error with: gre_sys: Invalid MTU 65000 requested, hw max 1500 The side effect of this is that if overlay networks are configured with high MTUs, the gre devices fragment the packets and networking is generally slow/broken. This is resolved as part of the upcoming 4.15 kernel under: https://github.com/torvalds/linux/commit/cfddd4c33c254954927942599d299b3865743146 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 resolution of bug 1743746 which prevents an increase in the MTU of the gre devices. ** Tags removed: verification-pike-needed ** Tags added: verification-pike-done -- 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 ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: Fix Committed Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: Fix Committed Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: [Impact] OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. [Test Case] Deploy OpenStack Pike (xenial + pike UCA or artful) Create tenant networks using GRE segmentation Boot instances Instance networking will be broken/slow gre_sys devices will be set to mtu=1472 on hypervisor hosts. [Regression Potential] Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 Ubuntu: In Progress Status in openvswitch package in Ubuntu: Confirmed Status in linux source package in Artful: In Progress Status in openvswitch source package in Artful: Confirmed Status in linux source package in Bionic: In Progress Status in openvswitch source package in Bionic: Confirmed Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 add-apt-repository cloud-archive:queens-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-queens-needed to verification-queens-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-queens-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/queens Status: In Progress => Fix Committed ** Tags added: verification-queens-needed -- 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 ovs 2.8.x Status in Ubuntu Cloud Archive: Fix Committed Status in Ubuntu Cloud Archive pike series: Fix Committed Status in Ubuntu Cloud Archive queens series: Fix Committed Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Fix Released Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: Fix Committed Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: Fix Released Bug description: [Impact] OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. [Test Case] Deploy OpenStack Pike (xenial + pike UCA or artful) Create tenant networks using GRE segmentation Boot instances Instance networking will be broken/slow gre_sys devices will be set to mtu=1472 on hypervisor hosts. [Regression Potential] Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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, 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 Ubuntu: In Progress Status in openvswitch package in Ubuntu: Invalid Status in linux source package in Artful: In Progress Status in openvswitch source package in Artful: Invalid Status in linux source package in Bionic: In Progress Status in openvswitch source package in Bionic: Invalid Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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: Ubuntu Description:Ubuntu 17.10 Release:17.10 Codename: artful $ uname -a Linux juju-9b0cd0-artful-proposed-19 4.13.0-35-generic #39-Ubuntu SMP Mon Feb 12 11:06:39 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- 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 devices Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] GRE overlay networks can't carry traffic with MTU > 1500 [Test Case] 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 gre_sys device will be configured with MTU 1472. sudo ip link set gre_sys mtu 65000 will fail with EINVAL. [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 GRE overlay networking) and the ip tools. The kernel will error with: gre_sys: Invalid MTU 65000 requested, hw max 1500 The side effect of this is that if overlay networks are configured with high MTUs, the gre devices fragment the packets and networking is generally slow/broken. This is resolved as part of the upcoming 4.15 kernel under: https://github.com/torvalds/linux/commit/cfddd4c33c254954927942599d299b3865743146 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: Fix Committed Status in Ubuntu Cloud Archive pike series: Fix Committed Status in Ubuntu Cloud Archive queens series: Fix Committed Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Fix Released Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: Fix Committed Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: Fix Released Bug description: [Impact] OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. [Test Case] Deploy OpenStack Pike (xenial + pike UCA or artful) Create tenant networks using GRE segmentation Boot instances Instance networking will be broken/slow gre_sys devices will be set to mtu=1472 on hypervisor hosts. [Regression Potential] Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 so we can easily find any regressions. -- 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 ovs 2.8.x Status in Ubuntu Cloud Archive: Fix Committed Status in Ubuntu Cloud Archive pike series: Fix Released Status in Ubuntu Cloud Archive queens series: Fix Committed Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Fix Released Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: Fix Released Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: Fix Released Bug description: [Impact] OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. [Test Case] Deploy OpenStack Pike (xenial + pike UCA or artful) Create tenant networks using GRE segmentation Boot instances Instance networking will be broken/slow gre_sys devices will be set to mtu=1472 on hypervisor hosts. [Regression Potential] Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 . * d/p/dpif-kernel-gre-mtu-workaround.patch, d/p/dpif-netlink-rtnl-Use-65000-instead-of-65535-as-tunnel-MTU.patch: Cherry pick in-flight fixes for workaround to correctly set MTU of GRE devices via netlink (LP: #1742505). ** Changed in: cloud-archive/pike 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 path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: Fix Committed Status in Ubuntu Cloud Archive pike series: Fix Released Status in Ubuntu Cloud Archive queens series: Fix Committed Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: Fix Released Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: Fix Released Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: Fix Released Bug description: [Impact] OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. [Test Case] Deploy OpenStack Pike (xenial + pike UCA or artful) Create tenant networks using GRE segmentation Boot instances Instance networking will be broken/slow gre_sys devices will be set to mtu=1472 on hypervisor hosts. [Regression Potential] Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Incomplete Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Incomplete Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Incomplete Status in openvswitch source package in Bionic: In Progress Bug description: Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. @James - do you think you could test a super-recent mainline kernel build from [2] in regard to this issue? [1]: https://github.com/torvalds/linux/commit/cfddd4c33c254954927942599d299b3865743146 [2]: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc8/"; This kernel fix resolves a secondary issue I saw with the 4.13 kernel where the workaround we used for 4.4 did not work - the kernel was applying a 1500 max limit to all GRE devices. This was fixed in [1] which I've confirmed on my test but the original OVS bug still exists - gre_sys is still configured with MTU 1472, implying the IFLA_MTU value provided via netlink is being ignored by the kernel. ** Changed in: linux (Ubuntu Artful) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Bionic) 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/1742505 Title: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 when using path_mtu > 1500 with ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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; the remote_ip can be anything but is obviously not functional. -- 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 ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 GRE overlay networking) and the ip tools. The kernel will error with: gre_sys: Invalid MTU 65000 requested, hw max 1500 The side effect of this is that if overlay networks are configured with high MTUs, the gre devices fragment the packets and networking is generally slow/broken. This is resolved as part of the upcoming 4.15 kernel under: https://github.com/torvalds/linux/commit/cfddd4c33c254954927942599d299b3865743146 ** 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/1743746 Title: 4.13: unable to increase MTU configuration for GRE devices Status in linux package in Ubuntu: New Bug description: [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 GRE overlay networking) and the ip tools. The kernel will error with: gre_sys: Invalid MTU 65000 requested, hw max 1500 The side effect of this is that if overlay networks are configured with high MTUs, the gre devices fragment the packets and networking is generally slow/broken. This is resolved as part of the upcoming 4.15 kernel under: https://github.com/torvalds/linux/commit/cfddd4c33c254954927942599d299b3865743146 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 creates tunnel devices for GRE overlay networking) and the ip tools. The kernel will error with: - gre_sys: Invalid MTU 65000 requested, hw max 1500 + gre_sys: Invalid MTU 65000 requested, hw max 1500 The side effect of this is that if overlay networks are configured with high MTUs, the gre devices fragment the packets and networking is generally slow/broken. This is resolved as part of the upcoming 4.15 kernel under: https://github.com/torvalds/linux/commit/cfddd4c33c254954927942599d299b3865743146 ** Description changed: [Impact] GRE overlay networks can't carry traffic with MTU > 1500 [Test Case] + 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 + + gre_sys device will be configured with MTU 1472. + + sudo ip link set gre_sys mtu 65000 + + will fail with EINVAL. [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 GRE overlay networking) and the ip tools. The kernel will error with: gre_sys: Invalid MTU 65000 requested, hw max 1500 The side effect of this is that if overlay networks are configured with high MTUs, the gre devices fragment the packets and networking is generally slow/broken. This is resolved as part of the upcoming 4.15 kernel under: https://github.com/torvalds/linux/commit/cfddd4c33c254954927942599d299b3865743146 -- 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 devices Status in linux package in Ubuntu: New Bug description: [Impact] GRE overlay networks can't carry traffic with MTU > 1500 [Test Case] 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 gre_sys device will be configured with MTU 1472. sudo ip link set gre_sys mtu 65000 will fail with EINVAL. [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 GRE overlay networking) and the ip tools. The kernel will error with: gre_sys: Invalid MTU 65000 requested, hw max 1500 The side effect of this is that if overlay networks are configured with high MTUs, the gre devices fragment the packets and networking is generally slow/broken. This is resolved as part of the upcoming 4.15 kernel under: https://github.com/torvalds/linux/commit/cfddd4c33c254954927942599d299b3865743146 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 devices Status in linux package in Ubuntu: Confirmed Bug description: [Impact] GRE overlay networks can't carry traffic with MTU > 1500 [Test Case] 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 gre_sys device will be configured with MTU 1472. sudo ip link set gre_sys mtu 65000 will fail with EINVAL. [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 GRE overlay networking) and the ip tools. The kernel will error with: gre_sys: Invalid MTU 65000 requested, hw max 1500 The side effect of this is that if overlay networks are configured with high MTUs, the gre devices fragment the packets and networking is generally slow/broken. This is resolved as part of the upcoming 4.15 kernel under: https://github.com/torvalds/linux/commit/cfddd4c33c254954927942599d299b3865743146 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 with ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 1000 link/ether 3a:14:f5:6d:cd:93 brd ff:ff:ff:ff:ff:ff I was able to set the MTU of the gre_sys device to 65000. -- 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 devices Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Bug description: [Impact] GRE overlay networks can't carry traffic with MTU > 1500 [Test Case] 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 gre_sys device will be configured with MTU 1472. sudo ip link set gre_sys mtu 65000 will fail with EINVAL. [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 GRE overlay networking) and the ip tools. The kernel will error with: gre_sys: Invalid MTU 65000 requested, hw max 1500 The side effect of this is that if overlay networks are configured with high MTUs, the gre devices fragment the packets and networking is generally slow/broken. This is resolved as part of the upcoming 4.15 kernel under: https://github.com/torvalds/linux/commit/cfddd4c33c254954927942599d299b3865743146 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 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 ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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] + OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. + + [Test Case] + Deploy OpenStack Pike (xenial + pike UCA or artful) + Create tenant networks using GRE segmentation + Boot instances + Instance networking will be broken/slow + + gre_sys devices will be set to mtu=1472 on hypervisor hosts. + + [Regression Potential] + Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). + + + [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 -- 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 ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: [Impact] OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. [Test Case] Deploy OpenStack Pike (xenial + pike UCA or artful) Create tenant networks using GRE segmentation Boot instances Instance networking will be broken/slow gre_sys devices will be set to mtu=1472 on hypervisor hosts. [Regression Potential] Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743746] Re: 4.13: unable to increase MTU configuration for GRE devices
Thanks! -- 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 devices Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] GRE overlay networks can't carry traffic with MTU > 1500 [Test Case] 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 gre_sys device will be configured with MTU 1472. sudo ip link set gre_sys mtu 65000 will fail with EINVAL. [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 GRE overlay networking) and the ip tools. The kernel will error with: gre_sys: Invalid MTU 65000 requested, hw max 1500 The side effect of this is that if overlay networks are configured with high MTUs, the gre devices fragment the packets and networking is generally slow/broken. This is resolved as part of the upcoming 4.15 kernel under: https://github.com/torvalds/linux/commit/cfddd4c33c254954927942599d299b3865743146 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 which are disruptive to the data plane in an openstack cloud. -- 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 ovs 2.8.x Status in Ubuntu Cloud Archive: In Progress Status in Ubuntu Cloud Archive pike series: In Progress Status in Ubuntu Cloud Archive queens series: In Progress Status in neutron: Invalid Status in linux package in Ubuntu: Confirmed Status in openvswitch package in Ubuntu: In Progress Status in linux source package in Artful: Confirmed Status in openvswitch source package in Artful: In Progress Status in linux source package in Bionic: Confirmed Status in openvswitch source package in Bionic: In Progress Bug description: [Impact] OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe packet fragmentation/networking issues for traffic in overlay networks. [Test Case] Deploy OpenStack Pike (xenial + pike UCA or artful) Create tenant networks using GRE segmentation Boot instances Instance networking will be broken/slow gre_sys devices will be set to mtu=1472 on hypervisor hosts. [Regression Potential] Minimal; the fix to OVS works around an issue for GRE tunnel port setup via rtnetlink by performing a second request once the gre device is setup to set the MTU to a high value (65000). [Original Bug Report] Setup: Pike neutron 11.0.2-0ubuntu1.1~cloud0 OVS 2.8.0 Jumbo frames setttings per: https://docs.openstack.org/mitaka/networking-guide/config-mtu.html global_physnet_mtu = 9000 path_mtu = 9000 Symptoms: gre_sys MTU is 1472 Instances with MTUs > 1500 fail to communicate across GRE Temporary Workaround: ifconfig gre_sys MTU 9000 Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set back to default 1472. Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue. Previous behavior: With Ocata or Pike and OVS 2.6.x gre_sys MTU defaults to 65490 It remains at 65490 through restarts. This may be related to some combination of the following changes in OVS which seem to imply MTUs must be set in the ovs database for tunnel interfaces and patches: https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1 https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1742505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1096002] Re: Multipath does not work with EMC 5300 Storage
Reassigning to the Linux package as that's where this driver resides (libiscsi is a pure userspace implementation of the iSCSI client protocol). ** Package changed: libiscsi (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/1096002 Title: Multipath does not work with EMC 5300 Storage Status in linux package in Ubuntu: New Bug description: Hi, I setup one host installed Ubuntu 12.04 with kernel version 3.2.0.I connect the host with EMC Stroage of 5300 with FC directly. I wanted use the feature of multipath, but it does not work. The log is as below: the syslog is : Jan 4 15:32:29 cvknode133 kernel: [14788.818398] device-mapper: table: 252:2: multipath: error getting device Jan 4 15:32:29 cvknode133 kernel: [14788.826062] device-mapper: ioctl: error adding target to table Jan 4 15:32:29 cvknode133 multipathd: dm-2: remove map (uevent) Jan 4 15:32:29 cvknode133 multipathd: dm-2: devmap not registered, can't remove Jan 4 15:32:29 cvknode133 multipathd: dm-2: remove map (uevent) Jan 4 15:32:29 cvknode133 multipathd: dm-2: devmap not registered, can't remove Jan 4 15:32:29 cvknode133 kernel: [14788.828229] device-mapper: table: 252:2: multipath: error getting device Jan 4 15:32:29 cvknode133 kernel: [14788.835525] device-mapper: ioctl: error adding target to table Jan 4 15:32:29 cvknode133 multipathd: dm-2: remove map (uevent) Jan 4 15:32:29 cvknode133 multipathd: dm-2: devmap not registered, can't remove Jan 4 15:32:29 cvknode133 multipathd: dm-2: remove map (uevent) Jan 4 15:32:29 cvknode133 multipathd: dm-2: devmap not registered, can't remove Jan 4 15:32:29 cvknode133 kernel: [14788.839135] device-mapper: table: 252:2: multipath: error getting device Jan 4 15:32:29 cvknode133 kernel: [14788.846118] device-mapper: ioctl: error adding target to table Jan 4 15:32:29 cvknode133 multipathd: dm-2: remove map (uevent) Jan 4 15:32:29 cvknode133 multipathd: dm-2: devmap not registered, can't remove Jan 4 15:32:29 cvknode133 kernel: [14788.849331] device-mapper: table: 252:2: multipath: error getting device Jan 4 15:32:29 cvknode133 kernel: [14788.855998] device-mapper: ioctl: error adding target to table Jan 4 15:32:29 cvknode133 multipathd: dm-2: remove map (uevent) Jan 4 15:32:29 cvknode133 multipathd: dm-2: devmap not registered, can't remove Jan 4 15:32:29 cvknode133 udevd[19111]: inotify_add_watch(6, /dev/dm-2, 10) failed: No such file or directory Jan 4 15:32:29 cvknode133 multipathd: dm-2: remove map (uevent) Jan 4 15:32:29 cvknode133 multipathd: dm-2: devmap not registered, can't remove Jan 4 15:32:29 cvknode133 kernel: [14788.859838] sd 0:0:0:16385: emc: Invalid information section length 128 Jan 4 15:32:29 cvknode133 kernel: [14788.859842] sd 0:0:0:16385: emc: detected Clariion FC (Legacy), flags 1 Jan 4 15:32:29 cvknode133 kernel: [14788.859939] sd 0:0:0:16385: emc: Invalid failover mode 2 Jan 4 15:32:29 cvknode133 kernel: [14788.859942] sd 0:0:0:16385: emc: not attached Jan 4 15:32:29 cvknode133 kernel: [14788.866610] device-mapper: table: 252:2: multipath: error attaching hardware handler Jan 4 15:32:29 cvknode133 multipathd: dm-2: remove map (uevent) Jan 4 15:32:29 cvknode133 multipathd: dm-2: devmap not registered, can't remove Jan 4 15:32:29 cvknode133 kernel: [14788.879802] device-mapper: ioctl: error adding target to table Jan 4 15:32:29 cvknode133 multipathd: dm-2: remove map (uevent) Jan 4 15:32:29 cvknode133 multipathd: dm-2: devmap not registered, can't remove Jan 4 15:32:29 cvknode133 multipathd: dm-2: remove map (uevent) Jan 4 15:32:29 cvknode133 multipathd: dm-2: devmap not registered, can't remove Jan 4 15:32:29 cvknode133 kernel: [14788.882923] sd 0:0:0:16385: emc: Invalid information section length 128 Jan 4 15:32:29 cvknode133 kernel: [14788.882928] sd 0:0:0:16385: emc: detected Clariion FC (Legacy), flags 1 Jan 4 15:32:29 cvknode133 kernel: [14788.883019] sd 0:0:0:16385: emc: Invalid failover mode 2 Jan 4 15:32:29 cvknode133 kernel: [14788.883022] sd 0:0:0:16385: emc: not attached Jan 4 15:32:29 cvknode133 kernel: [14788.889542] device-mapper: table: 252:2: multipath: error attaching hardware handler Jan 4 15:32:29 cvknode133 kernel: [14788.903347] device-mapper: ioctl: error adding target to table Jan 4 15:32:29 cvknode133 udevd[19111]: inotify_add_watch(6, /dev/dm-2, 10) failed: No such file or directory Jan 4 15:32:29 cvknode133 multipathd: dm-2: remove map (uevent) Jan 4 15:32:29 cvknode133 multipathd: dm-2: devmap not registered, can't remove Jan 4 15:32:29 cvknode133 udevd[19111]: inotify_add_watch(6, /dev/dm-2, 10) failed: No such file or directory Jan 4 15:32:29 cvknode133 multipathd: dm-2: remove map (uevent) Jan 4 15:32:29 cvknode133 multipathd: dm-2:
[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386
>From autopkgtest histories: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- artful/artful/i386/o/openvswitch/20170904_183010_82746@/log.gz linux-generic is already the newest version (4.12.0.12.13). That was for the 2.8.0-0ubuntu1 upload during artful development. that said subsequent tests using: linux-generic is already the newest version (4.12.0.12.13). -- 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 destroying interfaces on i386 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386
OK so to summarize what's concrete here: Only impacts i386 Impacts both ovs 2.8.0 and 2.8.1 Impacts artful and 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/1736390 Title: openvswitch: kernel opps destroying interfaces on i386 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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. https://bugs.launchpad.net/bugs/1736390 Title: openvswitch: kernel opps destroying interfaces on i386 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386
Stacktrace from artful: Dec 13 12:06:09 artful-i386-testing kernel: [ 160.913030] BUG: unable to handle kernel NULL pointer dereference at (null) Dec 13 12:06:09 artful-i386-testing kernel: [ 160.915102] IP: igmp_group_dropped+0x21/0x220 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.916317] *pdpt = *pde = f000ff53f000ff53 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.916329] Dec 13 12:06:09 artful-i386-testing kernel: [ 160.917728] Oops: [#1] SMP Dec 13 12:06:09 artful-i386-testing kernel: [ 160.918345] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack ppdev kvm_intel kvm irqbypass crc32_pclmul input_leds serio_raw joydev parport_pc parport ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid aesni_intel hid aes_i586 crypto_simd cryptd virtio_blk psmouse virtio_net floppy Dec 13 12:06:09 artful-i386-testing kernel: [ 160.931511] CPU: 0 PID: 29 Comm: kworker/u2:1 Tainted: GW 4.13.0-16-generic #19-Ubuntu Dec 13 12:06:09 artful-i386-testing kernel: [ 160.933321] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.10.1-1ubuntu1~cloud0 04/01/2014 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.934970] Workqueue: netns cleanup_net Dec 13 12:06:09 artful-i386-testing kernel: [ 160.937847] task: f577c200 task.stack: f4c5a000 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.938694] EIP: igmp_group_dropped+0x21/0x220 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.940625] EFLAGS: 00010202 CPU: 0 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.941432] EAX: EBX: f2b32c60 ECX: f4c5be68 EDX: 0002 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.942712] ESI: EDI: f29c1700 EBP: f4c5bdc8 ESP: f4c5bd90 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.944471] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.945612] CR0: 80050033 CR2: CR3: 1ad8a000 CR4: 000406f0 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.946879] Call Trace: Dec 13 12:06:09 artful-i386-testing kernel: [ 160.949247] ? __wake_up+0x36/0x40 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.950074] ip_mc_down+0x27/0x90 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.951557] inetdev_event+0x398/0x4e0 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.953391] ? skb_dequeue+0x5b/0x70 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.954246] ? wireless_nlevent_flush+0x4c/0x90 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.955656] notifier_call_chain+0x4e/0x70 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.956814] raw_notifier_call_chain+0x11/0x20 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.957803] call_netdevice_notifiers_info+0x2a/0x60 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.958886] dev_close_many+0x9d/0xe0 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.962228] rollback_registered_many+0xd7/0x380 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.963690] unregister_netdevice_many.part.102+0x10/0x80 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.964981] default_device_exit_batch+0x134/0x160 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.966026] ? do_wait_intr_irq+0x80/0x80 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.966937] ops_exit_list.isra.8+0x4d/0x60 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.969310] cleanup_net+0x18e/0x260 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.973290] process_one_work+0x1a0/0x390 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.975236] worker_thread+0x37/0x440 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.976998] kthread+0xf3/0x110 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.977853] ? process_one_work+0x390/0x390 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.978803] ? kthread_create_on_node+0x20/0x20 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.980521] ret_from_fork+0x19/0x24 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.981350] Code: 90 90 90 90 90 90 90 90 90 90 66 66 66 66 90 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.987207] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:f4c5bd90 Dec 13 12:06:09 artful-i386-testing kernel: [ 160.988793] CR2: Dec 13 12:06:09 artful-i386-testing kernel: [ 160.989603] ---[ end trace 9fe78986aa6abc43 ]--- Dec 13 12:12:22 artful-i386-testing kernel: [0.00] random: get_random_bytes called from start_kernel+0x35/0x41e with crng_init=0 Dec 13 12:12:22 artful-i386-testing kernel: [0.00] Linux versi
[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. https://bugs.launchpad.net/bugs/1736390 Title: openvswitch: kernel opps destroying interfaces on i386 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack ppdev kvm_intel kvm irqbypass parport_pc input_leds parport joydev serio_raw ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crc32_pclmul pcbc hid_generic usbhid aesni_intel hid aes_i586 psmouse crypto_simd virtio_net cryptd virtio_blk floppy [ 118.081568] CPU: 0 PID: 29 Comm: kworker/u2:1 Tainted: GW 4.13.0-19-generic #22~16.04.1-Ubuntu [ 118.088041] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.10.1-1ubuntu1~cloud0 04/01/2014 [ 118.090334] Workqueue: netns cleanup_net [ 118.091146] task: f537e300 task.stack: f485a000 [ 118.092077] EIP: rtmsg_ifa+0x2d/0xe0 [ 118.092778] EFLAGS: 00010246 CPU: 0 [ 118.093654] EAX: EBX: f3674e00 ECX: EDX: 014000c0 [ 118.095002] ESI: EDI: f34dad80 EBP: f485bd94 ESP: f485bd7c [ 118.101126] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 118.102531] CR0: 80050033 CR2: CR3: 33df3860 CR4: 000406f0 [ 118.104276] Call Trace: [ 118.105159] __inet_del_ifa+0x129/0x270 [ 118.106192] ? igmpv3_clear_delrec+0x28/0xb0 [ 118.107392] inetdev_event+0x1ff/0x4e0 [ 118.113963] ? __schedule+0x41e/0x8d0 [ 118.115418] notifier_call_chain+0x4e/0x70 [ 118.117049] ? notifier_call_chain+0x4e/0x70 [ 118.118081] raw_notifier_call_chain+0x11/0x20 [ 118.119125] call_netdevice_notifiers_info+0x2a/0x60 [ 118.125600] rollback_registered_many+0x268/0x370 [ 118.127652] unregister_netdevice_many+0x16/0x80 [ 118.129980] ? unregister_netdevice_many+0x16/0x80 [ 118.136510] default_device_exit_batch+0x126/0x150 [ 118.138577] ? do_wait_intr_irq+0x80/0x80 [ 118.140326] ops_exit_list.isra.8+0x4d/0x60 [ 118.142126] cleanup_net+0x18e/0x270 [ 118.143731] process_one_work+0x118/0x390 [ 118.149200] worker_thread+0x37/0x410 [ 118.150881] kthread+0xdb/0x110 [ 118.152617] ? process_one_work+0x390/0x390 [ 118.154530] ? kthread_create_on_node+0x20/0x20 [ 118.161804] ret_from_fork+0x19/0x24 [ 118.163523] Code: 66 66 90 55 89 e5 57 56 53 89 d7 89 ce 83 ec 0c 85 c9 89 45 ec 0f 84 93 00 00 00 8b 41 08 89 45 f0 8b 47 0c 31 c9 ba c0 00 40 01 <8b> 00 8b 80 20 03 00 00 6a ff 89 45 e8 b8 60 00 00 00 e8 7c 3e [ 118.175426] EIP: rtmsg_ifa+0x2d/0xe0 SS:ESP: 0068:f485bd7c [ 118.177188] CR2: [ 118.178305] ---[ end trace d1d2a116a66e2f9d ]--- -- 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 destroying interfaces on i386 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netde
[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. https://bugs.launchpad.net/bugs/1736390 Title: openvswitch: kernel opps destroying interfaces on i386 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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 recirc_id(0),dp_hash(0/0),skb_priority(0/0),in_port(3),skb_mark(0/0),ct_state(0/0),ct_zone(0/0),ct_mark(0/0),ct_label(0/0),eth(src=76:bd:b5:1d:36:0f,dst=33:33:00:00:00:02),eth_type(0x86dd),ipv6(src=fe80::74bd:b5ff:fe1d:360f/::,dst=ff02::2/::,label=0/0,proto=58/0,tclass=0/0,hlimit=255/0,frag=no),icmpv6(type=133/0,code=0/0), actions:userspace(pid=0,slow_path(controller)) 2017-12-13T12:40:23.502Z|6|dpif(revalidator20)|WARN|system@ovs-system: failed to put[modify] (Invalid argument) ufid:526e564d-5dba-42da-b433-dbb77cddef23 recirc_id(0),dp_hash(0/0),skb_priority(0/0),in_port(10),skb_mark(0/0),ct_state(0/0),ct_zone(0/0),ct_mark(0/0),ct_label(0/0),eth(src=42:f1:94:53:48:5b,dst=33:33:00:00:00:02),eth_type(0x86dd),ipv6(src=fe80::40f1:94ff:fe53:485b/::,dst=ff02::2/::,label=0/0,proto=58/0,tclass=0/0,hlimit=255/0,frag=no),icmpv6(type=133/0,code=0/0), actions:userspace(pid=0,slow_path(controller)) 2017-12-13T12:40:23.505Z|00162|bridge|INFO|bridge s1: deleted interface s1 on port 65534 2017-12-13T12:40:23.505Z|00163|bridge|INFO|bridge s1: deleted interface s1-eth8 on port 8 2017-12-13T12:40:23.526Z|00164|bridge|INFO|bridge s2: deleted interface s2-eth4 on port 4 2017-12-13T12:40:23.526Z|00165|bridge|INFO|bridge s2: deleted interface s2-eth8 on port 8 2017-12-13T12:40:23.526Z|00166|bridge|INFO|bridge s2: deleted interface s2 on port 65534 2017-12-13T12:40:23.526Z|00167|bridge|INFO|bridge s2: deleted interface s2-eth6 on port 6 2017-12-13T12:40:23.526Z|00168|bridge|INFO|bridge s2: deleted interface s2-eth7 on port 7 2017-12-13T12:40:23.526Z|00169|bridge|INFO|bridge s2: deleted interface s2-eth2 on port 2 2017-12-13T12:40:23.527Z|00170|bridge|INFO|bridge s2: deleted interface s2-eth5 on port 5 2017-12-13T12:40:23.527Z|00171|bridge|INFO|bridge s2: deleted interface s2-eth3 on port 3 2017-12-13T12:40:23.527Z|00172|bridge|INFO|bridge s2: deleted interface s2-eth1 on port 1 2017-12-13T12:40:24.543Z|1|ovs_rcu(urcu5)|WARN|blocked 1005 ms waiting for main to quiesce 2017-12-13T12:40:25.539Z|2|ovs_rcu(urcu5)|WARN|blocked 2001 ms waiting for main to quiesce 2017-12-13T12:40:27.545Z|3|ovs_rcu(urcu5)|WARN|blocked 4007 ms waiting for main to quiesce 2017-12-13T12:40:31.542Z|4|ovs_rcu(urcu5)|WARN|blocked 8004 ms waiting for main to quiesce 2017-12-13T12:40:39.546Z|5|ovs_rcu(urcu5)|WARN|blocked 16008 ms waiting for main to quiesce -- 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 destroying interfaces on i386 Status in linux package in Ubuntu: Triaged Status in openvswitch package in Ubuntu: New Status in linux source package in Bionic: Triaged Status in openvswitch source package in Bionic: New Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.1
[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 root 16051 1 0 12:39 ?00:00:00 ovs-vswitchd: monitoring pid 16052 (healthy) root 16052 16051 0 12:39 ?00:00:00 [ovs-vswitchd] and root 17517 16216 0 12:40 pts/000:00:00 ovs-vsctl --if-exists del-br s1 -- --if-exists del-br s2 ** Also affects: openvswitch (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/1736390 Title: openvswitch: kernel opps destroying interfaces on i386 Status in linux package in Ubuntu: Triaged Status in openvswitch package in Ubuntu: New Status in linux source package in Bionic: Triaged Status in openvswitch source package in Bionic: New Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
