| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] Network dies and kernel errors
in my test environment, the irqbalance is already stopped.
So my bnx bug may not related to this.
Many thanks.
> Date: Tue, 2 Aug 2011 12:17:36 -0400
> From: konrad.wilk@xxxxxxxxxx
> To: johnm@xxxxxxxxxxx
> CC: tinnycloud@xxxxxxxxxxx; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Network dies and kernel errors
>
> 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
|
|
|
| |
|
Home