[Kernel-packages] [Bug 1488815] Re: Kernel traces with skb_warn_bad_offload showing up during an AIO deployment on Ubuntu 14.04
** Changed in: openstack-ansible/trunk 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/1488815 Title: Kernel traces with skb_warn_bad_offload showing up during an AIO deployment on Ubuntu 14.04 Status in openstack-ansible: Fix Released Status in openstack-ansible juno series: Won't Fix Status in openstack-ansible kilo series: Fix Released Status in openstack-ansible trunk series: Fix Released Status in linux package in Ubuntu: Incomplete Status in qemu-kvm package in Ubuntu: New Bug description: Setting up an os-ansible-deployment AIO in a VM running in KVM results in kernel traces with skb_warn_bad_offload during the setup phase. This is happening regardless of the kernel (tested with 3.13, 3.16 and 3.19) on a fresh VM with no specific customization. Order of steps to reproduce: 1) launch image from ubuntu cloud catalog 2) apt-get diet-upgrade 3) apt-get install git linux-image-virtual-lts-vivid 4) git clone https://github.com/stackforge/os-ansible-deployment.git 5) cd os-ansible-deployment 6) git checkout kilo 7) ./scripts/bootstrap-ansible.sh 8) ./scripts/run-aio-build.sh This appears to be harmless as the deployment eventually succeeds. Here is a brief extract of the traces: Aug 26 07:57:27 test-osad kernel: [ 4695.687317] [ cut here ] Aug 26 07:57:27 test-osad kernel: [ 4695.687328] WARNING: CPU: 0 PID: 20433 at /build/linux-lts-vivid-BZwsXG/linux-lts-vivid-3.19.0/net/core/dev.c:2302 skb_warn_bad_offload+0xd5/0xe2() Aug 26 07:57:27 test-osad kernel: [ 4695.687332] : caps=(0x00801fdb78e9, 0x00801fdb78e9) len=4396 data_len=2920 gso_size=1448 gso_type=1 ip_summed=3 Aug 26 07:57:27 test-osad kernel: [ 4695.687334] Modules linked in: vhost_net vhost macvtap macvlan nbd iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ipt_REJECT nf_reject_ipv4 ip6table_filter ip6_tables dm_snapshot dm_bufio dm_multipath scsi_dh 8021q garp mrp veth ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_tcpudp bridge stp llc btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c vxlan ip6_udp_tunnel udp_tunnel iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter ip_tables x_tables dm_crypt kvm_amd ppdev kvm parport_pc parport serio_raw crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse floppy Aug 26 07:57:27 test-osad kernel: [ 4695.687390] CPU: 0 PID: 20433 Comm: ssh Tainted: GW 3.19.0-26-generic #28~14.04.1-Ubuntu Aug 26 07:57:27 test-osad kernel: [ 4695.687392] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 01/01/2011 Aug 26 07:57:27 test-osad kernel: [ 4695.687395] 81b3db38 880266e576f8 817aeed7 Aug 26 07:57:27 test-osad kernel: [ 4695.687399] 880266e57748 880266e57738 81074d8a 880266e57788 Aug 26 07:57:27 test-osad kernel: [ 4695.687402] 8803736ef4e8 88042caba000 0001 0003 Aug 26 07:57:27 test-osad kernel: [ 4695.687406] Call Trace: Aug 26 07:57:27 test-osad kernel: [ 4695.687414] [] dump_stack+0x45/0x57 Aug 26 07:57:27 test-osad kernel: [ 4695.687420] [] warn_slowpath_common+0x8a/0xc0 Aug 26 07:57:27 test-osad kernel: [ 4695.687424] [] warn_slowpath_fmt+0x46/0x50 Aug 26 07:57:27 test-osad kernel: [ 4695.687427] [] skb_warn_bad_offload+0xd5/0xe2 Aug 26 07:57:27 test-osad kernel: [ 4695.687434] [] skb_checksum_help+0x1ac/0x1c0 Aug 26 07:57:27 test-osad kernel: [ 4695.687441] [] checksum_tg+0x29/0x30 [xt_CHECKSUM] Aug 26 07:57:27 test-osad kernel: [ 4695.687446] [] ipt_do_table+0x2d9/0x6bd [ip_tables] Aug 26 07:57:27 test-osad kernel: [ 4695.687451] [] ? ipt_do_table+0x332/0x6bd [ip_tables] Aug 26 07:57:27 test-osad kernel: [ 4695.687455] [] ? ipt_do_table+0x332/0x6bd [ip_tables] Aug 26 07:57:27 test-osad kernel: [ 4695.687461] [] ? ip_fragment+0x8a0/0x8a0 Aug 26 07:57:27 test-osad kernel: [ 4695.687464] [] iptable_mangle_hook+0x66/0x140 [iptable_mangle] Aug 26 07:57:27 test-osad kernel: [ 4695.687467] [] ? ip_fragment+0x8a0/0x8a0 Aug 26 07:57:27 test-osad kernel: [ 4695.687470] [] nf_iterate+0x9a/0xb0 Aug 26 07:57:27 test-osad kernel: [ 4695.687472] [] ? ip_fragment+0x8a0/0x8a0 Aug 26 07:57:27 test-osad kernel: [ 4695.687475] [] nf_hook_slow+0x74/0x130 Aug 26 07:57:27 test-osad kernel: [ 4695.687477] [] ? ip_fragment+0x8a0/0x8a0 Aug 26 07:57:27 test-osad kernel: [ 4695.687479] [] ? ip_forward_options+0x1c0/0x1c0 Aug 26 07:57:27 test-osad kernel: [ 4695.687481] [] ip_output+0x92/0xa0 Aug 26 07:57:27 test-osad kernel: [ 4695.687484] [] ? __ip_local_out+0xaa/0xb0 Aug 26 07:57:27 test-osad kernel: [ 4695.6
[Kernel-packages] [Bug 1488815] Re: Kernel traces with skb_warn_bad_offload showing up during an AIO deployment on Ubuntu 14.04
** Changed in: openstack-ansible/kilo 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/1488815 Title: Kernel traces with skb_warn_bad_offload showing up during an AIO deployment on Ubuntu 14.04 Status in openstack-ansible: Fix Committed Status in openstack-ansible juno series: Won't Fix Status in openstack-ansible kilo series: Fix Released Status in openstack-ansible trunk series: Fix Committed Status in linux package in Ubuntu: Incomplete Status in qemu-kvm package in Ubuntu: New Bug description: Setting up an os-ansible-deployment AIO in a VM running in KVM results in kernel traces with skb_warn_bad_offload during the setup phase. This is happening regardless of the kernel (tested with 3.13, 3.16 and 3.19) on a fresh VM with no specific customization. Order of steps to reproduce: 1) launch image from ubuntu cloud catalog 2) apt-get diet-upgrade 3) apt-get install git linux-image-virtual-lts-vivid 4) git clone https://github.com/stackforge/os-ansible-deployment.git 5) cd os-ansible-deployment 6) git checkout kilo 7) ./scripts/bootstrap-ansible.sh 8) ./scripts/run-aio-build.sh This appears to be harmless as the deployment eventually succeeds. Here is a brief extract of the traces: Aug 26 07:57:27 test-osad kernel: [ 4695.687317] [ cut here ] Aug 26 07:57:27 test-osad kernel: [ 4695.687328] WARNING: CPU: 0 PID: 20433 at /build/linux-lts-vivid-BZwsXG/linux-lts-vivid-3.19.0/net/core/dev.c:2302 skb_warn_bad_offload+0xd5/0xe2() Aug 26 07:57:27 test-osad kernel: [ 4695.687332] : caps=(0x00801fdb78e9, 0x00801fdb78e9) len=4396 data_len=2920 gso_size=1448 gso_type=1 ip_summed=3 Aug 26 07:57:27 test-osad kernel: [ 4695.687334] Modules linked in: vhost_net vhost macvtap macvlan nbd iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ipt_REJECT nf_reject_ipv4 ip6table_filter ip6_tables dm_snapshot dm_bufio dm_multipath scsi_dh 8021q garp mrp veth ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_tcpudp bridge stp llc btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c vxlan ip6_udp_tunnel udp_tunnel iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter ip_tables x_tables dm_crypt kvm_amd ppdev kvm parport_pc parport serio_raw crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse floppy Aug 26 07:57:27 test-osad kernel: [ 4695.687390] CPU: 0 PID: 20433 Comm: ssh Tainted: GW 3.19.0-26-generic #28~14.04.1-Ubuntu Aug 26 07:57:27 test-osad kernel: [ 4695.687392] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 01/01/2011 Aug 26 07:57:27 test-osad kernel: [ 4695.687395] 81b3db38 880266e576f8 817aeed7 Aug 26 07:57:27 test-osad kernel: [ 4695.687399] 880266e57748 880266e57738 81074d8a 880266e57788 Aug 26 07:57:27 test-osad kernel: [ 4695.687402] 8803736ef4e8 88042caba000 0001 0003 Aug 26 07:57:27 test-osad kernel: [ 4695.687406] Call Trace: Aug 26 07:57:27 test-osad kernel: [ 4695.687414] [] dump_stack+0x45/0x57 Aug 26 07:57:27 test-osad kernel: [ 4695.687420] [] warn_slowpath_common+0x8a/0xc0 Aug 26 07:57:27 test-osad kernel: [ 4695.687424] [] warn_slowpath_fmt+0x46/0x50 Aug 26 07:57:27 test-osad kernel: [ 4695.687427] [] skb_warn_bad_offload+0xd5/0xe2 Aug 26 07:57:27 test-osad kernel: [ 4695.687434] [] skb_checksum_help+0x1ac/0x1c0 Aug 26 07:57:27 test-osad kernel: [ 4695.687441] [] checksum_tg+0x29/0x30 [xt_CHECKSUM] Aug 26 07:57:27 test-osad kernel: [ 4695.687446] [] ipt_do_table+0x2d9/0x6bd [ip_tables] Aug 26 07:57:27 test-osad kernel: [ 4695.687451] [] ? ipt_do_table+0x332/0x6bd [ip_tables] Aug 26 07:57:27 test-osad kernel: [ 4695.687455] [] ? ipt_do_table+0x332/0x6bd [ip_tables] Aug 26 07:57:27 test-osad kernel: [ 4695.687461] [] ? ip_fragment+0x8a0/0x8a0 Aug 26 07:57:27 test-osad kernel: [ 4695.687464] [] iptable_mangle_hook+0x66/0x140 [iptable_mangle] Aug 26 07:57:27 test-osad kernel: [ 4695.687467] [] ? ip_fragment+0x8a0/0x8a0 Aug 26 07:57:27 test-osad kernel: [ 4695.687470] [] nf_iterate+0x9a/0xb0 Aug 26 07:57:27 test-osad kernel: [ 4695.687472] [] ? ip_fragment+0x8a0/0x8a0 Aug 26 07:57:27 test-osad kernel: [ 4695.687475] [] nf_hook_slow+0x74/0x130 Aug 26 07:57:27 test-osad kernel: [ 4695.687477] [] ? ip_fragment+0x8a0/0x8a0 Aug 26 07:57:27 test-osad kernel: [ 4695.687479] [] ? ip_forward_options+0x1c0/0x1c0 Aug 26 07:57:27 test-osad kernel: [ 4695.687481] [] ip_output+0x92/0xa0 Aug 26 07:57:27 test-osad kernel: [ 4695.687484] [] ? __ip_local_out+0xaa/0xb0 Aug 26 07:57:27 test-osad kernel: [ 4695.
[Kernel-packages] [Bug 1285708] Re: FreeBSD Guest crash on boot due to xsave instruction issue
Quite right - our workaround was to switch to using the host capabilities instead of the compatibility fallback. However, the decision for a compatibility fallback was automatically made and included the above combination. I don't know where that bug should sit. -- 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/1285708 Title: FreeBSD Guest crash on boot due to xsave instruction issue Status in QEMU: Invalid Status in qemu-kvm: New Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: Won't Fix Status in “linux” source package in Trusty: In Progress Bug description: When trying to boot a working FreeBSD 9.1/9.2 guest on a kvm/qemu host with the following command: kvm -m 256 -cdrom FreeBSD-9.2-RELEASE-amd64-disc1.iso -drive file=FreeBSD-9.2-RELEASE-amd64.qcow2,if=virtio -net nic,model=virtio -net user -nographic -vnc :10 -enable-kvm -balloon virtio -cpu core2duo,+xsave The FreeBSD Guest will kernel crash on boot with the following error: panic: CPU0 does not support X87 or SSE: 0 When launching the guest without the cpu flags, it works just fine. This bug has been resolved in source: https://lkml.org/lkml/2014/2/22/58 Can this fix be included in Precise ASAP! To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1285708/+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 1273386] Re: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel
Could this be related? https://bugs.launchpad.net/ubuntu/precise/+source/openvswitch/+bug/1262692 -- 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/1273386 Title: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel Status in OpenStack Neutron (virtual network service): Triaged Status in OpenStack Compute (Nova): New Status in “linux” package in Ubuntu: Incomplete Bug description: In the past 9 days we have been seeing very frequent occurences of this kernel crash: http://paste.openstack.org/show/61869/ Even if the particular crash pasted here is triggered by dnsmasq, in almost all cases the crash is actually triggered by the neutron metada proxy. This also affects nova badly since this issue, which appears namespace related, results in a hang while mounting the ndb device for key injection. logstash query: http://logstash.openstack.org/#eyJzZWFyY2giOiJcImtlcm5lbCBCVUcgYXQgL2J1aWxkL2J1aWxkZC9saW51eC0zLjIuMC9mcy9idWZmZXIuYzoyOTE3XCIgYW5kIGZpbGVuYW1lOnN5c2xvZy50eHQiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6ImN1c3RvbSIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJmcm9tIjoiMjAxNC0wMS0xNlQxODo1MDo0OCswMDowMCIsInRvIjoiMjAxNC0wMS0yN1QxOToxNjoxMSswMDowMCIsInVzZXJfaW50ZXJ2YWwiOiIwIn0sInN0YW1wIjoxMzkwODUwMzI2ODY0fQ== We have seen about 398 hits since the bug started to manifest. Decreased hit rate in the past few days is due to less neutron patches being pushed. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1273386/+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
