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] Network dies and kernel errors

To: John McMonagle <johnm@xxxxxxxxxxx>
Subject: Re: [Xen-devel] Network dies and kernel errors
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Tue, 2 Aug 2011 12:17:36 -0400
Cc: tinnycloud@xxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 02 Aug 2011 09:18:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <201107311821.48278.johnm@xxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <201107251418.21569.johnm@xxxxxxxxxxx> <201107291038.21289.johnm@xxxxxxxxxxx> <20110729173129.GA7637@xxxxxxxxxxxx> <201107311821.48278.johnm@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
On Sun, Jul 31, 2011 at 06:21:47PM -0500, John McMonagle wrote:
> Konrad
> 
> I ran as you requested and after 2 days it's still up.

Good!
> 
> Attached are xen.dmesg and dom0.dmesg  all the command line parameters are in 
> them. 

> At this point I'd be happy if was on line with a reasonably efficient stable 
> configuration.

So it looks like from your runs (before you had irqbalance):

(XEN)  MSI    31 vec=ad  fixed  edge   assert phys    cpu dest=00000023 
mask=1/0/0
(XEN)  MSI    31 vec=ad  fixed  edge   assert phys    cpu dest=00000023 
mask=1/0/0
(XEN)  MSI    31 vec=ad  fixed  edge   assert phys    cpu dest=00000023 
mask=1/0/0
(XEN)  MSI    31 vec=ad  fixed  edge   assert phys    cpu dest=00000023 
mask=1/0/0
(XEN)    IRQ:  31 affinity:00000000,00000000,00000000,00004000 vec:b5 
type=PCI-MSI         status=00000010 in-flight=0 domain-list=0:273(----),
(XEN)  MSI    31 vec=39  fixed  edge   assert phys    cpu dest=00000020 
mask=1/0/0
(XEN)    IRQ:  31 affinity:00000000,00000000,00000000,00000100 vec:39 
type=PCI-MSI         status=00000050 in-flight=0 domain-list=0:273(----),

The affinity (and the corresponding vector) moves from one CPU to another
and then dom0 somehow does not get it. Do you have another of these
boxes available remotly to debug this further?


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

<Prev in Thread] Current Thread [Next in Thread>