WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] Hard lock of server - saved history from serial consolew

To: "Matt Ayres" <matta@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Hard lock of server - saved history from serial consolewithin
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Wed, 19 Apr 2006 23:19:42 +0100
Delivery-date: Wed, 19 Apr 2006 15:20:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZj/cGqvuQ0Qa73RzaCxMKeosEyvAAAXZlQ
Thread-topic: [Xen-devel] Hard lock of server - saved history from serial consolewithin
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