[Xen-bugs] [Bug 1028] New: frequent dom0 panics with xen 3.1

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1028

           Summary: frequent dom0 panics with xen 3.1
           Product: Xen
           Version: unspecified
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: major
          Priority: P2
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: kala@xxxxxxxx


The system has ran for few weeks without errors but in the past 24h I have
received 3 similar panics somewhere at csum_partial. I have not yet discovered
when exactly this happens - maybe because of increased network traffic which
has been much higher in the past 24h.

--

Unable to handle kernel paging request at ffff8800007abbb0 RIP:
 [<ffffffff804620f7>] csum_partial+0x227/0x4ca
PGD db8067 PUD db9067 PMD dbd067 PTE 0
Oops: 0000 [1] SMP
CPU 0
Modules linked in: xt_physdev sd_mod iscsi_tcp libiscsi scsi_transport_iscsi
scsi_mod ipt_LOG xt_tcpudp xt_state iptable_nat ip_nat iptable_filter ip_tables
x_tables ip_conntrack_tftp ip_conntrack_ftp ip_conntrack nfnetlink usbhid
ehci_hcd ohci_hcd usbcore
Pid: 0, comm: swapper Not tainted 2.6.18-xen0 #2
RIP: e030:[<ffffffff804620f7>]  [<ffffffff804620f7>] csum_partial+0x227/0x4ca
RSP: e02b:ffffffff805acb20  EFLAGS: 00010202
RAX: 0000000000000001 RBX: 0000000000000000 RCX: ffff8800007abbf0
RDX: 0000000000000000 RSI: 0000000000000450 RDI: ffff8800007abbb0
RBP: ffffffff805acb30 R08: 0000000000000000 R09: 0000000000000010
R10: 0000000000000011 R11: 000000000000008a R12: 0000000000000000
R13: 0000000000000034 R14: 0000000000000034 R15: ffff880040163c28
FS:  00002b81b73376d0(0000) GS:ffffffff8055b000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process swapper (pid: 0, threadinfo ffffffff8056e000, task ffffffff804da7e0)
Stack:  0000000000000450 00000000000005a8 ffffffff805acb90 ffffffff803ecdcc
 ffffffff80446339 0000000000000010 00000020be5836e6 ffff880000000484
 0000000000000000 ffff880040163c28 ffff8800eb72c68c ffff8800eb72c6a0
Call Trace:
 <IRQ> [<ffffffff803ecdcc>] skb_checksum+0x124/0x267
 [<ffffffff80446339>] br_forward_finish+0x0/0x54
 [<ffffffff803f1be8>] skb_checksum_help+0x7f/0xe1
 [<ffffffff88060340>] :iptable_nat:ip_nat_fn+0x3c/0x1c1
 [<ffffffff88060717>] :iptable_nat:ip_nat_local_fn+0x37/0xc4
 [<ffffffff8040780b>] nf_iterate+0x43/0x80
 [<ffffffff8040f720>] dst_output+0x0/0x10
 [<ffffffff80407995>] nf_hook_slow+0x59/0xc2
 [<ffffffff8040f720>] dst_output+0x0/0x10
 [<ffffffff80411de2>] ip_queue_xmit+0x3f4/0x466
 [<ffffffff80420f2b>] tcp_transmit_skb+0x651/0x68d
 [<ffffffff80421eb6>] tcp_retransmit_skb+0x54e/0x64c
 [<ffffffff8020e3f1>] profile_pc+0x22/0x75
 [<ffffffff804248da>] tcp_write_timer+0x4cb/0x70d
 [<ffffffff8042440f>] tcp_write_timer+0x0/0x70d
 [<ffffffff80233b70>] run_timer_softirq+0x168/0x213
 [<ffffffff80230485>] __do_softirq+0x85/0x11b
 [<ffffffff8020ac70>] call_softirq+0x1c/0x28
 [<ffffffff8020ca5f>] do_softirq+0x6b/0xe8
 [<ffffffff8023036d>] irq_exit+0x48/0x4a
 [<ffffffff8020c9ea>] do_IRQ+0x6b/0x75
 [<ffffffff803a774f>] evtchn_do_upcall+0xb3/0x137
 [<ffffffff8020a7a6>] do_hypervisor_callback+0x1e/0x2c
 <EOI> [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
 [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
 [<ffffffff8020dfb9>] raw_safe_halt+0xb7/0xde
 [<ffffffff80208d13>] xen_idle+0x6e/0x80
 [<ffffffff80208a1a>] cpu_idle+0x51/0x70
 [<ffffffff80207394>] rest_init+0x26/0x2a
 [<ffffffff80578802>] start_kernel+0x24d/0x24f
 [<ffffffff80578219>] _sinittext+0x219/0x220


Code: 4c 03 07 4c 13 47 08 4c 13 47 10 4c 13 47 18 4c 13 47 20 4c
RIP  [<ffffffff804620f7>] csum_partial+0x227/0x4ca
 RSP <ffffffff805acb20>
CR2: ffff8800007abbb0
 <0>Kernel panic - not syncing: Aiee, killing interrupt handler!
 (XEN) Domain 0 crashed: rebooting machine in 5 seconds.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs