johnny Strom
2013-Apr-17 07:50 UTC
[Pkg-xen-devel] Bug#701744: We see the same with Debian wheezy.
Hello we see the same with debian Wheezy. Apr 16 16:02:25 hypervisor3 kernel: [2441115.664216] vif vif-17-0: vif17.0: Frag is bigger than frame. Apr 16 16:02:25 hypervisor3 kernel: [2441115.664267] vif vif-17-0: vif17.0: fatal error; disabling device Apr 16 16:02:25 hypervisor3 kernel: [2441115.675667] BUG: unable to handle kernel NULL pointer dereference at 00000000000008b8 Apr 16 16:02:25 hypervisor3 kernel: [2441115.675748] IP: [<ffffffff8134d981>] _raw_spin_lock_irqsave+0xe/0x25 Apr 16 16:02:25 hypervisor3 kernel: [2441115.675804] PGD 0 Apr 16 16:02:25 hypervisor3 kernel: [2441115.675843] Oops: 0002 [#1] SMP Apr 16 16:02:25 hypervisor3 kernel: [2441115.675893] CPU 17 Apr 16 16:02:25 hypervisor3 kernel: [2441115.675903] Modules linked in: cpuid xt_physdev xen_netback xen_blkback xen_gntdev xen_evtchn xenfs nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc xt_tcpudp xt_state ipt_LOG iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_filter ip_tables x_tables bridge stp dm_round_robin loop dm_multipath scsi_dh snd_pcm snd_page_alloc snd_timer snd soundcore coretemp crc32c_intel dm_mod iTCO_wdt sb_edac edac_core joydev evdev ghash_clmulni_intel aesni_intel aes_x86_64 aes_generic cryptd dcdbas pcspkr iTCO_vendor_support wmi shpchp acpi_power_meter processor button thermal_sys ext4 crc16 jbd2 mbcache microcode usbhid hid sg sr_mod sd_mod cdrom crc_t10dif lpfc scsi_transport_fc scsi_tgt ahci libahci libata ehci_hcd megaraid_sas usbcore scsi_mod usb_common tg3 libphy [last unloaded: scsi_wait_scan] Apr 16 16:02:25 hypervisor3 kernel: [2441115.676849] Apr 16 16:02:25 hypervisor3 kernel: [2441115.676883] Pid: 6383, comm: netback/17 Not tainted 3.2.0-4-amd64 #1 Debian 3.2.39-2 Dell Inc. PowerEdge R720/0X6H47 Apr 16 16:02:25 hypervisor3 kernel: [2441115.676978] RIP: e030:[<ffffffff8134d981>] [<ffffffff8134d981>] _raw_spin_lock_irqsave+0xe/0x25 Apr 16 16:02:25 hypervisor3 kernel: [2441115.677056] RSP: e02b:ffff880f79a57c30 EFLAGS: 00010002 Apr 16 16:02:25 hypervisor3 kernel: [2441115.677099] RAX: ffff8809dc3b0218 RBX: 00000000000008b8 RCX: 00000000153b5180 Apr 16 16:02:25 hypervisor3 kernel: [2441115.677168] RDX: 0000000000010000 RSI: ffffc9001b930000 RDI: 00000000000008b8 Apr 16 16:02:25 hypervisor3 kernel: [2441115.677237] RBP: 00000000000008b8 R08: 000000000002002a R09: 000000000000002f Apr 16 16:02:25 hypervisor3 kernel: [2441115.677306] R10: ffff880f7c37a4c0 R11: ffff880f7c37a4c0 R12: ffff8809dc3b7740 Apr 16 16:02:25 hypervisor3 kernel: [2441115.677375] R13: 0000000000000000 R14: ffff8809dc3b7818 R15: ffff880f78fe0002 Apr 16 16:02:25 hypervisor3 kernel: [2441115.677448] FS: 00007fa2bb71e700(0000) GS:ffff880fbfa20000(0000) knlGS:0000000000000000 Apr 16 16:02:25 hypervisor3 kernel: [2441115.677519] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b Apr 16 16:02:25 hypervisor3 kernel: [2441115.677563] CR2: 00000000000008b8 CR3: 0000000001605000 CR4: 0000000000002660 Apr 16 16:02:25 hypervisor3 kernel: [2441115.677632] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Apr 16 16:02:25 hypervisor3 kernel: [2441115.677701] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Apr 16 16:02:25 hypervisor3 kernel: [2441115.677771] Process netback/17 (pid: 6383, threadinfo ffff880f79a56000, task ffff880f76f698d0) Apr 16 16:02:25 hypervisor3 kernel: [2441115.677843] Stack: Apr 16 16:02:25 hypervisor3 kernel: [2441115.677877] 0000000000000000 ffffffffa048cddd ffff880f7c37a4c0 ffff8809dc3b7740 Apr 16 16:02:25 hypervisor3 kernel: [2441115.677969] 00000000153b5180 00000000153b5180 0000000000000000 00000000153b5180 Apr 16 16:02:25 hypervisor3 kernel: [2441115.678060] ffff880f78fe0002 ffffffffa048cf71 ffff8809dc3b7740 ffffc90017356ec0 Apr 16 16:02:25 hypervisor3 kernel: [2441115.678152] Call Trace: Apr 16 16:02:25 hypervisor3 kernel: [2441115.678191] [<ffffffffa048cddd>] ? xen_netbk_schedule_xenvif+0x35/0xd6 [xen_netback] Apr 16 16:02:25 hypervisor3 kernel: [2441115.678264] [<ffffffffa048cf71>] ? netbk_tx_err+0x3f/0x4b [xen_netback] Apr 16 16:02:25 hypervisor3 kernel: [2441115.678311] [<ffffffffa048d517>] ? xen_netbk_tx_build_gops+0x59a/0x9e2 [xen_netback] Apr 16 16:02:25 hypervisor3 kernel: [2441115.678384] [<ffffffff81004be5>] ? phys_to_machine+0x13/0x1c Apr 16 16:02:25 hypervisor3 kernel: [2441115.678429] [<ffffffff810040b9>] ? xen_mc_flush+0x124/0x153 Apr 16 16:02:25 hypervisor3 kernel: [2441115.678474] [<ffffffff81003124>] ? xen_end_context_switch+0xe/0x1c Apr 16 16:02:25 hypervisor3 kernel: [2441115.678520] [<ffffffff81003b77>] ? xen_mc_issue.constprop.24+0x31/0x49 Apr 16 16:02:25 hypervisor3 kernel: [2441115.678567] [<ffffffff8100d02f>] ? load_TLS+0x7/0xa Apr 16 16:02:25 hypervisor3 kernel: [2441115.678610] [<ffffffff8100d6a6>] ? __switch_to+0x13b/0x258 Apr 16 16:02:25 hypervisor3 kernel: [2441115.678656] [<ffffffff810359b7>] ? arch_local_irq_enable+0x7/0x8 Apr 16 16:02:25 hypervisor3 kernel: [2441115.678702] [<ffffffff81039834>] ? finish_task_switch+0x88/0xb9 Apr 16 16:02:25 hypervisor3 kernel: [2441115.678747] [<ffffffff8134c60c>] ? __schedule+0x5ac/0x5c3 Apr 16 16:02:25 hypervisor3 kernel: [2441115.678791] [<ffffffffa048da8d>] ? xen_netbk_kthread+0x12e/0x6f5 [xen_netback] Apr 16 16:02:25 hypervisor3 kernel: [2441115.678864] [<ffffffff8105f943>] ? add_wait_queue+0x3c/0x3c Apr 16 16:02:25 hypervisor3 kernel: [2441115.678908] [<ffffffffa048d95f>] ? xen_netbk_tx_build_gops+0x9e2/0x9e2 [xen_netback] Apr 16 16:02:25 hypervisor3 kernel: [2441115.678981] [<ffffffff8105f2f1>] ? kthread+0x76/0x7e Apr 16 16:02:25 hypervisor3 kernel: [2441115.679025] [<ffffffff81354ab4>] ? kernel_thread_helper+0x4/0x10 Apr 16 16:02:25 hypervisor3 kernel: [2441115.679070] [<ffffffff81352b73>] ? int_ret_from_sys_call+0x7/0x1b Apr 16 16:02:25 hypervisor3 kernel: [2441115.679115] [<ffffffff8134dcbc>] ? retint_restore_args+0x5/0x6 Apr 16 16:02:25 hypervisor3 kernel: [2441115.679160] [<ffffffff81354ab0>] ? gs_change+0x13/0x13 Apr 16 16:02:25 hypervisor3 kernel: [2441115.679201] Code: be 01 00 00 00 e9 cf fe ff ff e8 bb 32 d2 ff 85 c0 0f 95 c0 0f b6 c0 c3 e9 92 32 d2 ff 53 48 89 fb e8 58 32 d2 ff ba 00 00 01 00 <f0> 0f c1 13 89 d1 c1 e9 10 66 39 ca 74 07 f3 90 66 8b 13 eb f4 Apr 16 16:02:25 hypervisor3 kernel: [2441115.679715] RIP [<ffffffff8134d981>] _raw_spin_lock_irqsave+0xe/0x25 Apr 16 16:02:25 hypervisor3 kernel: [2441115.679766] RSP <ffff880f79a57c30> Apr 16 16:02:25 hypervisor3 kernel: [2441115.679803] CR2: 00000000000008b8 Apr 16 16:02:25 hypervisor3 kernel: [2441115.680261] ---[ end trace af1c02984d34edeb ]--- Apr 16 16:02:25 hypervisor3 kernel: [2441115.681500] wan0: port 16(vif17.0) entering forwarding state
Jean-Francois Chevrette
2013-Apr-20 08:31 UTC
[Pkg-xen-devel] Bug#701744: We see the same with Debian wheezy.
Same issue here. Haven't found a solution yet. Has anybody been succesful in downgrading the Wheezy kernel to workaround this issue? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20130420/7c8850ef/attachment.html>
Apparently Analagous Threads
- Bug#701744: [xen] Update to hypervisor 4.0.1-5.6 or linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures
- Bug#701744: xen-hypervisor-4.0-amd64: also seeing this problem on 4.0.1-5.8
- Bug#701744: Possible workaround.
- Bug#701744: [xen] Update to hypervisor 4.0.1-5.6 or linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures
- Bug#701744: [xen] Update to hypervisor 4.0.1-5.6 or linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures