[Xen-users] File server in domU dies on heavy traffic

["In-Tuition Xen" <listxenusers@xxxxxxxxxxxxxx>]

Itai Tavor scribbled on 14 July 2006 07:20:
> Hi,
> 
> Got a very painful problem with my Xen 3 setup... I can run 6-7
> guests fairly stably, but as soon as traffic to the file server guest
> picks up, it dies (guest console message below). I've seen this
> happen with NFS and SCP traffic and it's very consistent. After that,
> networking to/from all guests is gone, until the host is rebooted.
> 
> The setup is:
> 
> AMD Athlon64, Nforce 4 chipset, Marvel Yukon gigabit ethernet, xen-
> unstable from 7/4/06, Debian sarge amd64 on host and guests, shoe
> size 8.5.

Hi all,

I've got exactly the same problem happening on some recent xen0's
(xen-3.0.2-3.FC5).  They're running on exactly the same hardware as some
rock solid xen0's (6 blades) running an older version (xen-3.0.1-4).
I've rolled back the problem xen0's to this version in the hope that
will fix it.

Regards,

Matt.

BUG: unable to handle kernel NULL pointer dereference at virtual address
000000b0
 printing eip:
c90c21ac
*pde = ma 2209b067 pa 03053067
*pte = ma 00000000 pa fffff000
Oops: 0002 [#1]
SMP 
Modules linked in: ipv6 autofs4 sunrpc xennet ip_conntrack_ftp
ip_conntrack_netbios_ns ipt_REJECT xt_state ip_conntrack nfnetlink
xt_tcpudp iptable_filter ip_tables x_tables dm_snapshot dm_zero
dm_mirror dm_mod
CPU:    0
EIP:    0061:[<c90c21ac>]    Not tainted VLI
EFLAGS: 00210046   (2.6.17-1.2157_FC5xenU #1) 
EIP is at network_tx_buf_gc+0xc3/0x1b7 [xennet]
eax: 0000001c   ebx: 0000002e   ecx: c5820cfc   edx: 00000000
esi: 00000001   edi: c5820400   ebp: 00000020   esp: c0651edc
ds: 007b   es: 007b   ss: 0069
Process swapper (pid: 0, threadinfo=c0650000 task=c05f1800)
Stack: <0>c5820cfc 00000000 00000000 00000004 c5820000 000136fe 00013703
000136dd 
       00000000 c5820488 c5820400 c5820000 c90c3150 c5d8b300 00000000
00000000 
       00000109 c043a57d 00000109 c5820000 c0651f88 c0651f88 00000109
c0643880 
Call Trace:
 <c90c3150> netif_int+0x24/0x66 [xennet]  <c043a57d>
handle_IRQ_event+0x42/0x85
 <c043a64d> __do_IRQ+0x8d/0xdc  <c040665a> do_IRQ+0x1a/0x25
 <c0519efd> evtchn_do_upcall+0x66/0x9f  <c0404d79>
hypervisor_callback+0x3d/0x48
 <c042007b> ptrace_request+0x6d/0x207  <c0407a6a> safe_halt+0x84/0xa7
 <c0402bde> xen_idle+0x46/0x4e  <c0402cfd> cpu_idle+0x94/0xad
 <c0655772> start_kernel+0x346/0x34c 
Code: ff b4 9f 00 09 00 00 50 e8 9d 85 45 f7 c7 84 9f 00 09 00 00 00 00
00 00 8b 87 f4 00 00 00 89 84 9f f4 00 00 00 89 9f f4 00 00 00 <f0> ff
8d 90 00 00 00 0f 94 c0 83 c4 10 84 c0 74 62 bb 00 e0 ff 
EIP: [<c90c21ac>] network_tx_buf_gc+0xc3/0x1b7 [xennet] SS:ESP
0069:c0651edc
 <0>Kernel panic - not syncing: Fatal exception in interrupt
 BUG: warning at arch/i386/kernel/smp-xen.c:519/smp_call_function() (Not
tainted)
 <c040c5a0> smp_call_function+0x69/0x110  <c040eee6>
bust_spinlocks+0x3d/0x46
 <c040c6a0> smp_send_stop+0x10/0x46  <c040c655> stop_this_cpu+0x0/0x3b
 <c0418a2a> panic+0x46/0x184  <c04057d0> die+0x246/0x27b
 <c040f139> do_page_fault+0x0/0x8c1  <c040f863>
do_page_fault+0x72a/0x8c1
 <c040f139> do_page_fault+0x0/0x8c1  <c0404d37> error_code+0x2b/0x30
 <c90c21ac> network_tx_buf_gc+0xc3/0x1b7 [xennet]  <c90c3150>
netif_int+0x24/0x66 [xennet]
 <c043a57d> handle_IRQ_event+0x42/0x85  <c043a64d> __do_IRQ+0x8d/0xdc
 <c040665a> do_IRQ+0x1a/0x25  <c0519efd> evtchn_do_upcall+0x66/0x9f
 <c0404d79> hypervisor_callback+0x3d/0x48  <c042007b>
ptrace_request+0x6d/0x207
 <c0407a6a> safe_halt+0x84/0xa7  <c0402bde> xen_idle+0x46/0x4e
 <c0402cfd> cpu_idle+0x94/0xad  <c0655772> start_kernel+0x346/0x34c

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