Re: [Xen-devel] Hard lock of server - saved history from serial consolewithin

[Matt Ayres <matta@xxxxxxxxxxxx>]

Ian Pratt wrote:
> > Routed / Proxy ARP.
> >
> > vif-route assigns an IP to the appropriate vif interface.  
> > The IP's of the VM are routed through the vif interface.
> Have you iptables rules thrown in their too?
>  
Yes, an iptable rule for each IP for bandwidth accounting. Also 4 rules 
in the raw table and 4 rules in the nat table for port redirection.  I 
don't see how the actual iptables rules could effect the kernel though.
> > It's really nothing special... routing is actually less 
> > complex than bridging IMHO.
> > Is this perhaps a 2.6.16 kernel bug?  Are there any 
> > dis-advantages to upgrading to 2.6.16.9 or .10-rc?
> Please try .9 or .10-rc and let us know how you get on.
Easier said than done. I have 31 nodes and 2 have rebooted with this 
error so far.  It's especially hurtful as I just upgraded all nodes to 
the changeset listed in the original message yesterday.  I'll give it a 
shot, but I have absolutely no idea which node will reboot next.
> Ian
>
> > Thanks,
> > Matt
> >
> > Ian Pratt wrote:
> > > Please can you describe your networking setup. Judging by the stack 
> > > trace its non standard.
> > > Ian
> > >
> > > > -----Original Message-----
> > > > From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> > > > [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Matt 
> > > > Ayres
> > > > Sent: 19 April 2006 23:07
> > > > To: xen-devel@xxxxxxxxxxxxxxxxxxx
> > > > Subject: [Xen-devel] Hard lock of server - saved history 
> > from serial 
> > > > consolewithin
> > > >
> > > > This was a hard lock...
> > > >
> > > > xen_changeset          : Sun Apr 16 15:45:57 2006 +0100 
> > > > 9629:07408313ce33
> > > >  
> > > >  
> > > >  
> > > >  
> > > >                                                               
> > > >       --- TOP OF BUFFER ---
> > > > Unable to handle kernel paging request at virtual address d144a053
> > > >
> > > >   printing eip: 
> > > >
> > > > c03e5b55
> > > >
> > > > 09baa000 -> *pde = 00000000:ec867001
> > > >
> > > > 0e467000 -> *pme = 00000000:eb346067
> > > >
> > > > 0fb46000 -> *pte = 00000000:00000000
> > > >
> > > > Oops: 0000 [#1]
> > > >
> > > > SMP
> > > >
> > > > Modules linked in: 
> > > >
> > > > CPU:    0 
> > > >
> > > > EIP:    0061:[<c03e5b55>]    Not tainted VLI 
> > > >
> > > > EFLAGS: 00010282   (2.6.16-xen #4) 
> > > >
> > > > EIP is at ipt_do_table+0xad/0x2d0
> > > >
> > > > eax: 00000002   ebx: c804ca1e   ecx: c804ca1e   edx: 00000000 
> > > >
> > > > esi: d144a000   edi: 00004000   ebp: d144d9d0   esp: c0567dd0 
> > > >
> > > > ds: 007b   es: 007b   ss: 0069 
> > > >
> > > > Process swapper (pid: 0, threadinfo=c0566000 task=c04e5c80)
> > > >
> > > > Stack: <0>c051956c 00000000 c804ca1e 00000000 ce2f1800 cfdcb000 
> > > > d144a000 0000000 0
> > > >         00000001 00000000 c0567e70 80000000 c03aeb78 cfdcb000 
> > > > c03e6bd0
> > > > c0567eb4
> > > >         00000002 ce2f1800 cfdcb000 c0519540 00000000 c03a42f8 
> > > > 00000002
> > > > c0567eb4
> > > > Call Trace: 
> > > >
> > > > PORT HISTORY> NEXT
> > > >
> > > >   [<c03aeb78>] ip_forward_finish+0x0/0x36
> > > >
> > > >   [<c03e6bd0>] ipt_hook+0x1c/0x20
> > > >
> > > >   [<c03a42f8>] nf_iterate+0x2c/0x5e
> > > >
> > > >   [<c03aeb78>] ip_forward_finish+0x0/0x36
> > > >
> > > >   [<c03aeb78>] ip_forward_finish+0x0/0x36
> > > >
> > > >   [<c03a43f3>] nf_hook_slow+0x3c/0xc3
> > > >
> > > >   [<c03aeb78>] ip_forward_finish+0x0/0x36
> > > >
> > > >   [<c03aed4c>] ip_forward+0x19e/0x22e
> > > >
> > > >   [<c03aeb78>] ip_forward_finish+0x0/0x36
> > > >
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > >  
> > > >
> > > > _______________________________________________
> > > > Xen-devel mailing list
> > > > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > > > http://lists.xensource.com/xen-devel
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel