> Ah, finally people experiencing same bug as me!
>
> It is much much worse for me, as soon as I ping from domU
> network goes down, started with the subarch change.
For this bug it might actually be helpful to start collecting
information about the hardware it's observed on.
For us, the bug is hard to repro, despite us having tried on several
different machines (2 and 4 way SMP, Opteron and Xeon, tg3 and e1000
NICs).
If the bug is easier to trigger for you, please post a summary of the
hardware and anything unusual about your config (i.e. not default
bridged).
Thanks,
Ian
> Adam Wendt
> IPCoast, Inc.
>
> On Wed, 8 Feb 2006 12:11 , Chris Wright <chrisw@xxxxxxxxxxxx> sent:
>
> >* Ian Pratt (m+Ian.Pratt@xxxxxxxxxxxx) wrote:
> >> Yep, this is the bug I warned y'all about at the summit, but you
> >> asked for the code to be checked in anyway...
> >
> >Hehe, get what you ask for...
> >
> >> A bug shared is a bug fixed quicker? :-)
> >
> >Let's hope ;-)
> >
> >> For us, this only manifests on x86_64, and arrived with
> the subarch
> >> xen version of 2.6.12. Extensive inspection of the arch->subarch
> >> conversion suggests that nothing should have changed, so this is
> >> likely a latent bug being triggered by slight timing changes.
> >>
> >> It sounds like it's rather easier for you to trigger than
> it was for
> >> us
> >> -- we had to run xm-test several times to get it to happen. Happy
> >> hunting, and good luck :-)
> >
> >It's trivial for me to trigger. I'll keep poking at it.
> >
> >thanks,
> >-chris
> >
> >_______________________________________________
> >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
|
Home