[Bug 1463846] Re: if ip is specified on cmdline, networking should be brought up in initramfs
I just wanted to link it with the upstream issue on Debian bug tracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789067 ** Bug watch added: Debian Bug tracker #789067 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789067 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463846 Title: if ip is specified on cmdline, networking should be brought up in initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1463846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709818] Re: Failed to lock byte 100
Affects Artful and Bionic Here is published fix for qemu: https://lists.gnu.org/archive/html/qemu-devel/2017-07/msg06405.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709818 Title: Failed to lock byte 100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1709818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755268] Re: Kernel panic when using KVM and mlx4_en driver (when bonding and sriov enabled)
OK, this is my meesage that I wrote to kernel's netdev list: https://www.mail-archive.com/netdev@vger.kernel.org/msg223827.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755268 Title: Kernel panic when using KVM and mlx4_en driver (when bonding and sriov enabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755268] Re: Kernel panic when using KVM and mlx4_en driver (when bonding and sriov enabled)
** Summary changed: - Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled) + Kernel panic when using KVM and mlx4_en driver (when bonding and sriov enabled) ** Description changed: # System information # - # uname -a - Linux m5c37 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux + # uname -a + Linux m5c37 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux - # cat /etc/os-release - NAME="Ubuntu" - VERSION="16.04.4 LTS (Xenial Xerus)" - ID=ubuntu - ID_LIKE=debian - PRETTY_NAME="Ubuntu 16.04.4 LTS" - VERSION_ID="16.04" - HOME_URL="http://www.ubuntu.com/; - SUPPORT_URL="http://help.ubuntu.com/; - BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; - VERSION_CODENAME=xenial - UBUNTU_CODENAME=xenial + # cat /etc/os-release + NAME="Ubuntu" + VERSION="16.04.4 LTS (Xenial Xerus)" + ID=ubuntu + ID_LIKE=debian + PRETTY_NAME="Ubuntu 16.04.4 LTS" + VERSION_ID="16.04" + HOME_URL="http://www.ubuntu.com/; + SUPPORT_URL="http://help.ubuntu.com/; + BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; + VERSION_CODENAME=xenial + UBUNTU_CODENAME=xenial - # ethtool -i eno1 - driver: mlx4_en - version: 4.3-1.0.1 - firmware-version: 2.42.5004 - expansion-rom-version: - bus-info: :11:00.0 - supports-statistics: yes - supports-test: yes - supports-eeprom-access: no - supports-register-dump: no - supports-priv-flags: yes + # ethtool -i eno1 + driver: mlx4_en + version: 4.3-1.0.1 + firmware-version: 2.42.5004 + expansion-rom-version: + bus-info: :11:00.0 + supports-statistics: yes + supports-test: yes + supports-eeprom-access: no + supports-register-dump: no + supports-priv-flags: yes - # ethtool -i bond0 - driver: bonding - version: 3.7.1 - firmware-version: 2 - expansion-rom-version: - bus-info: - supports-statistics: no - supports-test: no - supports-eeprom-access: no - supports-register-dump: no - supports-priv-flags: no + # ethtool -i bond0 + driver: bonding + version: 3.7.1 + firmware-version: 2 + expansion-rom-version: + bus-info: + supports-statistics: no + supports-test: no + supports-eeprom-access: no + supports-register-dump: no + supports-priv-flags: no - # ethtool -i vmbr0 - driver: bridge - version: 2.3 - firmware-version: N/A - expansion-rom-version: - bus-info: N/A - supports-statistics: no - supports-test: no - supports-eeprom-access: no - supports-register-dump: no - supports-priv-flags: no + # ethtool -i vmbr0 + driver: bridge + version: 2.3 + firmware-version: N/A + expansion-rom-version: + bus-info: N/A + supports-statistics: no + supports-test: no + supports-eeprom-access: no + supports-register-dump: no + supports-priv-flags: no Mellanox driver was installed from http://content.mellanox.com/ofed/MLNX_OFED-4.3-1.0.1.0/MLNX_OFED_LINUX-4.3-1.0.1.0-ubuntu16.04-x86_64.tgz - ./mlnxofedinstall --kernel 4.13.0-36-generic --without-dkms --add- + ./mlnxofedinstall --kernel 4.13.0-36-generic --without-dkms --add- kernel-support # Steps for reproduce # This is my /etc/network/interfaces file: + auto lo + iface lo inet loopback - auto lo - iface lo inet loopback + auto openibd + iface openibd inet manual + pre-up /etc/init.d/openibd start + pre-down /etc/init.d/openibd force-stop - auto openibd - iface openibd inet manual - pre-up /etc/init.d/openibd start - pre-down /etc/init.d/openibd force-stop + auto bond0 + iface bond0 inet manual + pre-up ip link add bond0 type bond || true + pre-up ip link set bond0 down + pre-up ip link set bond0 type bond mode active-backup arp_interval 2000 arp_ip_target 10.36.0.1 arp_validate 3 primary eno1 + pre-up ip link set eno1 down + pre-up ip link set eno1d1 down + pre-up ip link set eno1 master bond0 + pre-up ip link set eno1d1 master bond0 + pre-up ip link set bond0 up + pre-down ip link del bond0 - auto bond0 - iface bond0 inet manual - pre-up ip link add bond0 type bond || true - pre-up ip link set bond0 down - pre-up ip link set bond0 type bond mode active-backup arp_interval 2000 arp_ip_target 10.36.0.1 arp_validate 3 primary eno1 - pre-up ip link set eno1 down - pre-up ip link set eno1d1 down - pre-up ip link set eno1 master bond0 - pre-up ip link set eno1d1 master bond0 - pre-up ip link set bond0 up -
[Bug 1755268] Re: Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled)
Additional I've also tested latest hwe kernel (4.13.0-37-generic) and build-in driver, the same problem here: [ 1011.070739] kvm [16361]: vcpu0, guest rIP: 0x810644d8 disabled perfctr wrmsr: 0xc2 data 0x [ 1011.528347] cache_from_obj: Wrong slab cache. kmalloc-256 but object is from kmalloc-192 [ 1011.927642] general protection fault: [#1] SMP PTI [ 1012.185439] cache_from_obj: Wrong slab cache. kmalloc-256 but object is from kmalloc-192 driver version: # ethtool -i eno1 driver: mlx4_en version: 4.0-0 firmware-version: 2.42.5004 expansion-rom-version: bus-info: :11:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no supports-priv-flags: yes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755268 Title: Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755268] Re: Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled)
Hi, I can't build new mellanox drivers for new kernel, so I used default one: # ethtool -i eno1 driver: mlx4_en version: 4.0-0 firmware-version: 2.42.5004 expansion-rom-version: bus-info: :11:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no supports-priv-flags: yes After creating virtual machine, my kernel was stuck with these messages: [ 2170.511433] kvm [28464]: vcpu0, guest rIP: 0x810644d8 disabled perfctr wrmsr: 0xc2 data 0x [ 2170.963166] [ cut here ] ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Artful) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755268 Title: Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755268] Re: Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled)
Hi Joseph, thanks for your answer. Currnetly I have two various hardware configuration: - HPE ProLiant m710p Server Cartridge (have no this problem) - HPE ProLiant m710x Server Cartridge (have this problem) > Did this issue start happening after an update/upgrade? > Was there a prior kernel version where you were not having this particular > problem? Well, I uses debootstrap script for install all needed software automatically and build image with base system. After that I uses this image for boot my nodes via PXE. So each boot I have system that installed from scratch. I've tested the next kernels: - Ubuntu 16.04 with stock kernel: 4.4.0-116-generic - Ubuntu 16.04 with hwe kernel: 4.13.0-36-generic - Ubuntu 16.04 with pve kernel: 4.13.13-6-pve - Debian 9 with pve kernel: 4.13.13-6-pve - Debian 9 with stock kernel: 4.9.0-6-amd64 All of them have this problem, but stock kernels can drops after some time. (I had no this error only on debian with 4.9.0-6-amd64 but presume it exists there because I'm not tested it properly) Another thing, that if I do this steps AFTER the system is boot up: rmmod mlx4_en mlx4_ib mlx4_core modprobe mlx4_core num_vfs=1 port_type_array=2,2 probe_vf=1 systemctl restart networking Everything starts working fine. > Please test the latest v4.16 kernel[0]. Ok, I'll do this -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755268 Title: Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755268] Re: Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled)
** Attachment added: "lspci -v output" https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1755268/+attachment/5081271/+files/lspci-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755268 Title: Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755268] Re: Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled)
I was teted right now, the problem occurs also on stock kernel. # uname -a Linux m5c43 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Seems bug connected only with specific hardware, I'll provide more information about this. I uses HP Moonshot x710x xartridge: # lspci 00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 0a) 00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 0a) 00:02.0 VGA compatible controller: Intel Corporation Device 193a (rev 09) 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31) 00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31) 00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev f1) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1) 00:1c.3 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #4 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1) 00:1d.5 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #14 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) 01:00.0 System peripheral: Hewlett-Packard Company Integrated Lights-Out Standard Slave Instrumentation & System Support (rev 06) 01:00.1 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200EH (rev 01) 01:00.2 System peripheral: Hewlett-Packard Company Integrated Lights-Out Standard Management Processor Support and Messaging (rev 06) 01:00.4 USB controller: Hewlett-Packard Company Integrated Lights-Out Standard Virtual USB Controller (rev 03) 0e:00.0 Non-Volatile memory controller: Intel Corporation Device f1a5 (rev 03) 11:00.0 Ethernet controller: Mellanox Technologies MT27520 Family [ConnectX-3 Pro] 11:00.1 Ethernet controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] # ethtool -i eno1 driver: mlx4_en version: 4.3-1.0.1 firmware-version: 2.40.5540 expansion-rom-version: bus-info: :11:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no supports-priv-flags: yes # mst status MST modules: MST PCI module loaded MST PCI configuration module loaded MST devices: /dev/mst/mt4103_pci_cr0 - PCI direct access. domain:bus:dev.fn=:11:00.0 bar=0x7f10 size=0x10 Chip revision is: 00 /dev/mst/mt4103_pciconf0 - PCI configuration cycles access. domain:bus:dev.fn=:11:00.0 addr.reg=88 data.reg=92 Chip revision is: 00 # ibv_devinfo hca_id: mlx4_1 transport: InfiniBand (0) fw_ver: 2.40.5540 node_guid: 0014:0500:d300:bc52 sys_image_guid: f403:4303:00fd:102d vendor_id: 0x02c9 vendor_part_id: 4100 hw_ver: 0x0 board_id: HP_1690110017 phys_port_cnt: 2 Device ports: port: 1 state: PORT_DOWN (1) max_mtu:4096 (5) active_mtu: 1024 (3) sm_lid: 0 port_lid: 0 port_lmc: 0x00 link_layer: Ethernet port: 2 state: PORT_DOWN (1) max_mtu:4096 (5) active_mtu: 1024 (3) sm_lid: 0 port_lid: 0 port_lmc: 0x00 link_layer: Ethernet hca_id: mlx4_0 transport: InfiniBand (0) fw_ver: 2.40.5540 node_guid:
[Bug 1755268] Re: Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled)
** Attachment added: "Dmesg output (before kernel panic)" https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1755268/+attachment/5081272/+files/dmesg.txt ** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755268 Title: Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755268] Re: Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled)
I'm tried to use simple modules loading instead /etc/init.d/openibd script: rmmod mlx4_en mlx4_core modprobe mlx4_core num_vfs=1 port_type_array=2,2 probe_vf=1 The result the same: [ 193.469331] mlx4_core :11:00.0: bond for multifunction failed [ 193.770126] cache_from_obj: Wrong slab cache. kmalloc-256 but object is from kmalloc-192 [ 194.170171] mlx4_en: eno1d1: Fail to bond device [ 194.170178] nf_reject_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables xt_set ip_set_list_set ip_set_hash_net veth beegfs(OE) dummy nf_conntrack_netlink xt_nat xt_tcpudp xt_recent ip_set nfnetlink ip_vs rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc fscache xt_comment xt_mark netconsole mlx4_ib(OE) mlx4_en(OE) mlx4_core(OE) ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack libcrc32c br_netfilter 8021q garp mrp ib_core(OE) mlx_compat(OE) bridge stp llc bonding ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 hpilo crypto_simd [ 194.170482] glue_helper cryptd intel_cstate mei_me ipmi_si ipmi_devintf ipmi_msghandler intel_rapl_perf shpchp mei acpi_power_meter mac_hid ie31200_edac knem(OE) autofs4 overlay nbd ptp pps_core i915 mgag200 video ttm i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm nvme ahci nvme_core libahci devlink [last unloaded: mlx4_core] [ 194.170550] CPU: 0 PID: 7 Comm: ksoftirqd/0 Tainted: GW OE 4.13.0-36-generic #40~16.04.1-Ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755268 Title: Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1755268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755268] [NEW] Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled)
Public bug reported: # System information # # uname -a Linux m5c37 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.4 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.4 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial # ethtool -i eno1 driver: mlx4_en version: 4.3-1.0.1 firmware-version: 2.42.5004 expansion-rom-version: bus-info: :11:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no supports-priv-flags: yes # ethtool -i bond0 driver: bonding version: 3.7.1 firmware-version: 2 expansion-rom-version: bus-info: supports-statistics: no supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no # ethtool -i vmbr0 driver: bridge version: 2.3 firmware-version: N/A expansion-rom-version: bus-info: N/A supports-statistics: no supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no Mellanox driver was installed from http://content.mellanox.com/ofed/MLNX_OFED-4.3-1.0.1.0/MLNX_OFED_LINUX-4.3-1.0.1.0-ubuntu16.04-x86_64.tgz ./mlnxofedinstall --kernel 4.13.0-36-generic --without-dkms --add- kernel-support # Steps for reproduce # This is my /etc/network/interfaces file: auto lo iface lo inet loopback auto openibd iface openibd inet manual pre-up /etc/init.d/openibd start pre-down /etc/init.d/openibd force-stop auto bond0 iface bond0 inet manual pre-up ip link add bond0 type bond || true pre-up ip link set bond0 down pre-up ip link set bond0 type bond mode active-backup arp_interval 2000 arp_ip_target 10.36.0.1 arp_validate 3 primary eno1 pre-up ip link set eno1 down pre-up ip link set eno1d1 down pre-up ip link set eno1 master bond0 pre-up ip link set eno1d1 master bond0 pre-up ip link set bond0 up pre-down ip link del bond0 auto vmbr0 iface vmbr0 inet static address 10.36.128.217 netmask 255.255.0.0 gateway 10.36.0.1 bridge_ports bond0 bridge_stp off bridge_fd 0 I execute these commands: wget http://dl-cdn.alpinelinux.org/alpine/v3.7/releases/x86_64/alpine-virt-3.7.0-x86_64.iso -O alpine.iso qemu-system-x86_64 -boot d -cdrom alpine.iso -m 512 -nographic -device e1000,netdev=net0 -netdev tap,id=net0 And after few moments I have hang kernel, and theese messages in console: [74390.187908] mlx4_core :11:00.0: bond for multifunction failed [74390.486476] mlx4_en: eno1d1: Fail to bond device [74390.750758] cache_from_obj: Wrong slab cache. kmalloc-256 but object is from kmalloc-192 [74391.152326] general protection fault: [#1] SMP PTI [74391.410424] cache_from_obj: Wrong slab cache. kmalloc-256 but object is from kmalloc-192 kernel trace log in attachment ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Mar 12 19:59:16 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "kernel_trace2.log" https://bugs.launchpad.net/bugs/1755268/+attachment/5077342/+files/kernel_trace2.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755268 Title: Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1755268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665921] Re: OverlayFS with readonly NFS lower layer. Operation not supported for non-root files.
I confirm, It seems that is not overlayfs problem. The problem occurs only with glusterfs backed storage (on nfs server). I tested this internal gluster nfs server, and ganesha nfs server, nfs-kernel-server is not supported by glusterfs. With nfs-kernel-server and ext4 no any problems. Even readonly mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665921 Title: OverlayFS with readonly NFS lower layer. Operation not supported for non-root files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665921] Re: OverlayFS with readonly NFS lower layer. Operation not supported for non-root files.
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665921 Title: OverlayFS with readonly NFS lower layer. Operation not supported for non-root files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665921] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1665921/+attachment/4821714/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665921 Title: OverlayFS with readonly NFS lower layer. Operation not supported for non-root files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665921] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1665921/+attachment/4821711/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665921 Title: OverlayFS with readonly NFS lower layer. Operation not supported for non-root files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665921] Re: OverlayFS with readonly NFS lower layer. Operation not supported for non-root files.
apport information ** Tags added: apport-collected xenial ** Description changed: Step to reproduse: - Crete dircetory with other directories and files. - Chown some files in this directory, set any non-root permissions. - Export nfs share with 'ro' permissions. - Mount nfs share. - Mount ovrelayfs with nfs as lowerdir - Try to read theese non-root files or directories: Example for overlay mount: # ls -l /var/lib/libvirt total 16 drwx--x--x 2 root root 4096 Oct 10 07:33 boot drwx--x--x 2 root root 4096 Oct 10 07:33 images drwxr-x--- 3 libvirt-qemu kvm 4096 Jan 11 21:49 qemu drwx-- 2 root root 4096 Oct 10 07:33 sanlock # ls -l /var/lib/libvirt/qemu/ ls: cannot open directory '/var/lib/libvirt/qemu/': Operation not supported And for nfs mount: # ls -l /rofs/var/lib/libvirt total 16 drwx--x--x 2 root root 4096 Oct 10 07:33 boot drwx--x--x 2 root root 4096 Oct 10 07:33 images drwxr-x--- 3 libvirt-qemu kvm 4096 Jan 11 21:49 qemu drwx-- 2 root root 4096 Oct 10 07:33 sanlock # ls -l /rofs/var/lib/libvirt/qemu/ total 4 drwxr-xr-x 3 root root 4096 Jan 11 21:49 channel If I reset permission, it helps: # chown libvirt-qemu:kvm /var/lib/libvirt/qemu # ls -l /var/lib/libvirt/qemu/ total 4 drwxr-xr-x 3 root root 4096 Jan 11 21:49 channel My mounts (from /proc/mounts) 192.168.101.61:/data/opt/ltsp/amd64 /rofs nfs ro,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nolock,proto=tcp,port=2049,timeo=7,retrans=10,sec=sys,local_lock=all,addr=192.168.101.61 0 0 overlay / overlay rw,relatime,lowerdir=/rofs,upperdir=/cow/up,workdir=/cow/work 0 0 I tested it nfs3 and nfs4 mount, with this kenels: # uname -a Linux controller03 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # uname -a Linux m1c18n1 4.8.0-36-generic #36~16.04.1-Ubuntu SMP Sun Feb 5 09:39:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux + --- + AlsaDevices: + total 0 + crw-rw+ 1 root audio 116, 1 Feb 11 2016 seq + crw-rw+ 1 root audio 116, 33 Feb 11 2016 timer + AplayDevices: aplay: device_list:268: no soundcards found... + ApportVersion: 2.20.1-0ubuntu2.5 + Architecture: amd64 + ArecordDevices: arecord: device_list:268: no soundcards found... + AudioDevicesInUse: Error: [Errno 2] No such file or directory + CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. + DistroRelease: Ubuntu 16.04 + IwConfig: Error: [Errno 2] No such file or directory + Lsusb: + Bus 001 Device 002: ID 8087:8000 Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: HP ProLiant m710p Server Cartridge + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=vmlinuz-4.8.0-36-generic ro initrd=initrd.img-4.8.0-36-generic init=/sbin/init-ltsp forcepae console=tty1 console=ttyS0,9600 root=/dev/nfs boot=nfs nfsroot=/data/opt/ltsp/amd64 BOOTIF=01-94-57-a5-d3-b9-a6 + ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 + 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.8.0-36-generic N/A + linux-backports-modules-4.8.0-36-generic N/A + linux-firmware1.157.6 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial + Uname: Linux 4.8.0-36-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 04/06/2016 + dmi.bios.vendor: HP + dmi.bios.version: H06 + dmi.board.vendor: HP + dmi.chassis.type: 25 + dmi.chassis.vendor: HP + dmi.modalias: dmi:bvnHP:bvrH06:bd04/06/2016:svnHP:pnProLiantm710pServerCartridge:pvr:rvnHP:rn:rvr:cvnHP:ct25:cvr: + dmi.product.name: ProLiant m710p Server Cartridge + dmi.sys.vendor: HP ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1665921/+attachment/4821709/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665921 Title: OverlayFS with readonly NFS lower layer. Operation not supported for non-root files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665921] dmi.board.asset.tag.gz
apport information ** Attachment added: "dmi.board.asset.tag.gz" https://bugs.launchpad.net/bugs/1665921/+attachment/4821717/+files/dmi.board.asset.tag.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665921 Title: OverlayFS with readonly NFS lower layer. Operation not supported for non-root files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665921] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1665921/+attachment/4821716/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665921 Title: OverlayFS with readonly NFS lower layer. Operation not supported for non-root files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665921] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1665921/+attachment/4821715/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665921 Title: OverlayFS with readonly NFS lower layer. Operation not supported for non-root files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665921] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1665921/+attachment/4821712/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665921 Title: OverlayFS with readonly NFS lower layer. Operation not supported for non-root files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665921] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1665921/+attachment/4821713/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665921 Title: OverlayFS with readonly NFS lower layer. Operation not supported for non-root files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665921] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1665921/+attachment/4821710/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665921 Title: OverlayFS with readonly NFS lower layer. Operation not supported for non-root files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665921] [NEW] OverlayFS with readonly NFS lower layer. Operation not supported for non-root files.
Public bug reported: Step to reproduse: - Crete dircetory with other directories and files. - Chown some files in this directory, set any non-root permissions. - Export nfs share with 'ro' permissions. - Mount nfs share. - Mount ovrelayfs with nfs as lowerdir - Try to read theese non-root files or directories: Example for overlay mount: # ls -l /var/lib/libvirt total 16 drwx--x--x 2 root root 4096 Oct 10 07:33 boot drwx--x--x 2 root root 4096 Oct 10 07:33 images drwxr-x--- 3 libvirt-qemu kvm 4096 Jan 11 21:49 qemu drwx-- 2 root root 4096 Oct 10 07:33 sanlock # ls -l /var/lib/libvirt/qemu/ ls: cannot open directory '/var/lib/libvirt/qemu/': Operation not supported And for nfs mount: # ls -l /rofs/var/lib/libvirt total 16 drwx--x--x 2 root root 4096 Oct 10 07:33 boot drwx--x--x 2 root root 4096 Oct 10 07:33 images drwxr-x--- 3 libvirt-qemu kvm 4096 Jan 11 21:49 qemu drwx-- 2 root root 4096 Oct 10 07:33 sanlock # ls -l /rofs/var/lib/libvirt/qemu/ total 4 drwxr-xr-x 3 root root 4096 Jan 11 21:49 channel If I reset permission, it helps: # chown libvirt-qemu:kvm /var/lib/libvirt/qemu # ls -l /var/lib/libvirt/qemu/ total 4 drwxr-xr-x 3 root root 4096 Jan 11 21:49 channel My mounts (from /proc/mounts) 192.168.101.61:/data/opt/ltsp/amd64 /rofs nfs ro,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nolock,proto=tcp,port=2049,timeo=7,retrans=10,sec=sys,local_lock=all,addr=192.168.101.61 0 0 overlay / overlay rw,relatime,lowerdir=/rofs,upperdir=/cow/up,workdir=/cow/work 0 0 I tested it nfs3 and nfs4 mount, with this kenels: # uname -a Linux controller03 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # uname -a Linux m1c18n1 4.8.0-36-generic #36~16.04.1-Ubuntu SMP Sun Feb 5 09:39:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665921 Title: OverlayFS with readonly NFS lower layer. Operation not supported for non-root files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652946] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1652946/+attachment/4797759/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652946 Title: Vlan on physical interface breaks TCP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652946] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1652946/+attachment/4797761/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652946 Title: Vlan on physical interface breaks TCP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652946] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1652946/+attachment/4797763/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652946 Title: Vlan on physical interface breaks TCP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652946] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1652946/+attachment/4797760/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652946 Title: Vlan on physical interface breaks TCP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652946] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1652946/+attachment/4797762/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652946 Title: Vlan on physical interface breaks TCP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652946] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1652946/+attachment/4797757/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652946 Title: Vlan on physical interface breaks TCP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652946] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1652946/+attachment/4797758/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652946 Title: Vlan on physical interface breaks TCP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652946] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1652946/+attachment/4797756/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652946 Title: Vlan on physical interface breaks TCP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652946] Re: Vlan on physical interface breaks TCP
apport information ** Tags added: apport-collected xenial ** Description changed: ### More info: http://serverfault.com/questions/820689/tcp-handshake-error-syn-and-syn-ack-packets-are-not-recognised/ ### Kernel version ```bash # uname -a Linux docker-host 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ``` ### Step to reproduce: - I use proxmox hypervisor and create virtual machine with virtio nic - Take ubuntu-server 16.04.1 https://www.ubuntu.com/download/server/thank-you?version=16.04.1=amd64 - Install in minimal installation - Execute: ```bash # ip link add link ens18 name ens18.111 type vlan id 111 # ip addr add 192.168.111.80/24 dev ens18.111 # ip link set ens18.111 up # ping 192.168.111.1 PING 192.168.111.1 (192.168.111.1) 56(84) bytes of data. 64 bytes from 192.168.111.1: icmp_seq=1 ttl=64 time=17.9 ms 64 bytes from 192.168.111.1: icmp_seq=2 ttl=64 time=18.8 ms 64 bytes from 192.168.111.1: icmp_seq=3 ttl=64 time=18.5 ms ^C --- 192.168.111.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 17.932/18.455/18.841/0.414 m # nslookup > server 192.168.111.1 Default server: 192.168.111.1 Address: 192.168.111.1#53 > google.com Server: 192.168.111.1 Address: 192.168.111.1#53 Non-authoritative answer: Name: google.com Address: 173.194.222.139 Name: google.com Address: 173.194.222.113 Name: google.com Address: 173.194.222.100 Name: google.com Address: 173.194.222.102 Name: google.com Address: 173.194.222.138 Name: google.com Address: 173.194.222.101 > type cv Server: 192.168.111.1 Address: 192.168.111.1#53 ** server can't find type: NXDOMAIN > google.com ;; connection timed out; no servers could be reached ^C ``` I tested this issue on arch linux iso and it's work properly ```bash # uname -a Linux archiso 4.8.11-1-ARCH #1 SMP PREEMPT SUN Nov 27 09:26:14 CET 2016 x86_64 FNU/Linux ``` + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Dec 29 02:29 seq + crw-rw 1 root audio 116, 33 Dec 29 02:29 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.4 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=/dev/mapper/docker--host-swap + InstallationDate: Installed on 2016-12-28 (0 days ago) + InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) + IwConfig: Error: [Errno 2] No such file or directory + Lsusb: + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: QEMU Standard PC (i440FX + PIIX, 1996) + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + LANGUAGE=en_US:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 cirrusdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=/dev/mapper/docker--host-root ro + ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-31-generic N/A + linux-backports-modules-4.4.0-31-generic N/A + linux-firmware1.157.4 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial xenial + Uname: Linux 4.4.0-31-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: 04/01/2014 + dmi.bios.vendor: SeaBIOS + dmi.bios.version: rel-1.7.5.1-0-g8936dbb-20141113_115728-nilsson.home.kraxel.org + dmi.chassis.type: 1 + dmi.chassis.vendor: QEMU + dmi.chassis.version: pc-i440fx-2.2 + dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.7.5.1-0-g8936dbb-20141113_115728-nilsson.home.kraxel.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.2:cvnQEMU:ct1:cvrpc-i440fx-2.2: + dmi.product.name: Standard PC (i440FX + PIIX, 1996) + dmi.product.version: pc-i440fx-2.2 + dmi.sys.vendor: QEMU ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1652946/+attachment/4797755/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652946 Title: Vlan on physical interface breaks TCP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652946] [NEW] Vlan on physical interface breaks TCP
Public bug reported: ### More info: http://serverfault.com/questions/820689/tcp-handshake-error-syn-and-syn-ack-packets-are-not-recognised/ ### Kernel version ```bash # uname -a Linux docker-host 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ``` ### Step to reproduce: - I use proxmox hypervisor and create virtual machine with virtio nic - Take ubuntu-server 16.04.1 https://www.ubuntu.com/download/server/thank-you?version=16.04.1=amd64 - Install in minimal installation - Execute: ```bash # ip link add link ens18 name ens18.111 type vlan id 111 # ip addr add 192.168.111.80/24 dev ens18.111 # ip link set ens18.111 up # ping 192.168.111.1 PING 192.168.111.1 (192.168.111.1) 56(84) bytes of data. 64 bytes from 192.168.111.1: icmp_seq=1 ttl=64 time=17.9 ms 64 bytes from 192.168.111.1: icmp_seq=2 ttl=64 time=18.8 ms 64 bytes from 192.168.111.1: icmp_seq=3 ttl=64 time=18.5 ms ^C --- 192.168.111.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 17.932/18.455/18.841/0.414 m # nslookup > server 192.168.111.1 Default server: 192.168.111.1 Address: 192.168.111.1#53 > google.com Server: 192.168.111.1 Address:192.168.111.1#53 Non-authoritative answer: Name: google.com Address: 173.194.222.139 Name: google.com Address: 173.194.222.113 Name: google.com Address: 173.194.222.100 Name: google.com Address: 173.194.222.102 Name: google.com Address: 173.194.222.138 Name: google.com Address: 173.194.222.101 > type cv Server: 192.168.111.1 Address:192.168.111.1#53 ** server can't find type: NXDOMAIN > google.com ;; connection timed out; no servers could be reached ^C ``` I tested this issue on arch linux iso and it's work properly ```bash # uname -a Linux archiso 4.8.11-1-ARCH #1 SMP PREEMPT SUN Nov 27 09:26:14 CET 2016 x86_64 FNU/Linux ``` ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652946 Title: Vlan on physical interface breaks TCP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652946] Re: Vlan on physical interface breaks TCP
At the moment I tried to reproduce this error in ubuntu again and I did not succeed. But something is clearly wrong. :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652946 Title: Vlan on physical interface breaks TCP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
