RE: [Xen-devel] Network dies and kernel errors

MaoXiaoyun
Thu, 04 Aug 2011 03:55:02 -0000

> Date: Wed, 3 Aug 2011 09:37:57 -0400
> From: konrad.wilk@oracle.com
> To: tinnycloud@hotmail.com
> CC: johnm@advocap.org; xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] Network dies and kernel errors
>
> On Wed, Aug 03, 2011 at 05:01:38PM +0800, MaoXiaoyun wrote:
> >
> > in my test environment, the irqbalance is already stopped.
> >
> > So my bnx bug may not related to this.
>
>
> Did you use ''noirqbalance'' on the Xen hypervisor line?

No. I just stop irqbalance service, any difference with
"noirqbalance"?
If so, I would like to have a try.

Thanks.

> >
> > Many thanks.
> >
> >
> > > Date: Tue, 2 Aug 2011 12:17:36 -0400
> > > From: konrad.wilk@oracle.com
> > > To: johnm@advocap.org
> > > CC: tinnycloud@hotmail.com; xen-devel@lists.xensource.com
> > > 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@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>

--_68a51b7e-93c7-4e06-a2d6-7b71f4e68446_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: 8bit



<!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:微软雅黑
}
-->

<div
dir=''ltr''>


> Date: Wed, 3 Aug 2011 09:37:57 -0400 > From:
konrad.wilk@oracle.com > To:
tinnycloud@hotmail.com > CC: johnm@advocap.org;
xen-devel@lists.xensource.com > Subject: Re: [Xen-devel] Network
dies and kernel errors > > On Wed, Aug 03, 2011
at 05:01:38PM +0800, MaoXiaoyun wrote: > >
> > in my test environment, the irqbalance is already
stopped. > > > > So my bnx bug
may not related to this. > > >
Did you use ''noirqbalance'' on the Xen hypervisor
line?

No. I just stop irqbalance service, any difference with
"noirqbalance"?
If so, I would like to have a try.

Thanks.
> > > > Many
thanks. > > > >
> > > Date: Tue, 2 Aug 2011 12:17:36
-0400 > > > From:
konrad.wilk@oracle.com > > > To:
johnm@advocap.org > > > CC:
tinnycloud@hotmail.com; xen-devel@lists.xensource.com > >
&gt; 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 >
&gt; &gt; (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(----), > >
&gt; (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@lists.xensource.com > >
http://lists.xensource.com/xen-devel >


--_68a51b7e-93c7-4e06-a2d6-7b71f4e68446_--


--===============1880987715=Content-Type: text/plain;
charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1880987715==--