Woon Wai Keen @ doubleukay.com
2005-Dec-10 20:01 UTC
[Xen-users] Solved: network problems when starting xend, Xen-3.0 + tg3
I finally found out why the network became unreachable (to the point
that tcpdump -i peth0 revealed no packets) when xend is started. This is
triggered when the tg3 interface is added to a bridge before the link
comes up.
The message displayed on the console is:
bridge: can''t decode speed from peth0: 0.
In scripts/network-bridge, the order of the operations are:
add_to_bridge ${bridge} ${vif0}
add_to_bridge ${bridge} ${pdev}
ip link set ${bridge} up
ip link set ${vif0} up
ip link set ${pdev} up
What worked for me is:
ip link set ${bridge} up
ip link set ${vif0} up
ip link set ${pdev} up
sleep 5 # to allow for autonegotiation period
add_to_bridge ${bridge} ${vif0}
add_to_bridge ${bridge} ${pdev}
The problem persists when forcing the link speed and disabling auto-neg
with ethtool.
Is this a bug with the tg3 driver or the bridging code?
--
Regards,
wK (www.doubleukay.com)
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Ian Pratt
2005-Dec-11 02:27 UTC
RE: [Xen-users] Solved: network problems when starting xend, Xen-3.0 + tg3
> I finally found out why the network became unreachable (to > the point that tcpdump -i peth0 revealed no packets) when > xend is started. This is triggered when the tg3 interface is > added to a bridge before the link comes up.This is rather interesting. We use tg3 cards on many of our boxes and haven''t had problems. It should only be peth0 that needs to do autonegotation. Please can you try a more minimal version of your patch that just perturbs peth0. Also, rather than "sleep 5", could you try polling for the link status going "up". Thanks, Ian> The message displayed on the console is: > bridge: can''t decode speed from peth0: 0. > > In scripts/network-bridge, the order of the operations are: > add_to_bridge ${bridge} ${vif0} > add_to_bridge ${bridge} ${pdev} > ip link set ${bridge} up > ip link set ${vif0} up > ip link set ${pdev} up > > What worked for me is: > ip link set ${bridge} up > ip link set ${vif0} up > ip link set ${pdev} up > sleep 5 # to allow for autonegotiation period > add_to_bridge ${bridge} ${vif0} > add_to_bridge ${bridge} ${pdev} > > The problem persists when forcing the link speed and > disabling auto-neg with ethtool. > > Is this a bug with the tg3 driver or the bridging code? > > -- > Regards, > wK (www.doubleukay.com) >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Woon Wai Keen @ doubleukay.com
2005-Dec-11 12:44 UTC
Re: [Xen-users] Solved: network problems when starting xend,Xen-3.0 + tg3
Ian Pratt wrote:> This is rather interesting. We use tg3 cards on many of our boxes and > haven''t had problems.To be specific, it''s the builtin NIC for the Dell Poweredge 850. Tigon3 [partno(BCM95721) rev 4101 PHY(5750)] (PCIX:100MHz:32-bit)> It should only be peth0 that needs to do autonegotation. Please can you > try a more minimal version of your patch that just perturbs peth0. > > Also, rather than "sleep 5", could you try polling for the link status > going "up".How about this: http://pastebin.ca/33278 -- Regards, wK (www.doubleukay.com) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ken Simpson
2006-Jan-09 02:11 UTC
Re: [Xen-users] Solved: network problems when starting xend, Xen-3.0 + tg3
Responding to a rather old post:> > Ian Pratt wrote: > > This is rather interesting. We use tg3 cards on many of our boxes and > > haven''t had problems.> To be specific, it''s the builtin NIC for the Dell Poweredge 850. > Tigon3 [partno(BCM95721) rev 4101 PHY(5750)] (PCIX:100MHz:32-bit)> > It should only be peth0 that needs to do autonegotation. Please > > can you try a more minimal version of your patch that just > > perturbs peth0.> > Also, rather than "sleep 5", could you try polling for the link status > > going "up".> How about this: http://pastebin.ca/33278I have the same problem on a SunFire X2100 with the tg3 driver. The patch at the above URL fixes the problem. Apparently it just takes a while for the device to auto-negotiate and therefore merging the device into the bridge fails. Waiting for the device to come up fixes the problem. Thanks for the patch, Woon. It took about four hours to find the solution to this problem -- not a fun time in the data center! Regards, Ken -- MailChannels: Assured Messaging (TM) | http://mailchannels.com -- Suite 203, 910 Richards St. Vancouver, BC, V6B 3C1, Canada Direct: +1-604-729-1741 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello,
Is there a Solaris kernel port for Xen available ?
If so ,could anybody point me to it ?
-Dakshina
__________________________________________
Yahoo! DSL Something to write home about.
Just $16.99/mo. or less.
dsl.yahoo.com
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
dasari dakshina wrote:> Hello, > Is there a Solaris kernel port for Xen available ? > If so ,could anybody point me to it ? > -Dakshina > > > > > __________________________________________ > Yahoo! DSL – Something to write home about. > Just $16.99/mo. or less. > dsl.yahoo.com > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-usershttp://www.google.com/search?hl=en&q=solaris+x86+xen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
dasari dakshina schrieb:>Hello, > Is there a Solaris kernel port for Xen available ? > If so ,could anybody point me to it ? > >There is a mailing list for the xen port on opensolaris.org where you can get indepth answers - if you are patient. Dirk _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ian Pratt
2006-Jan-09 08:56 UTC
RE: [Xen-users] Solved: network problems when starting xend, Xen-3.0 + tg3
> Responding to a rather old post: > > > > Ian Pratt wrote: > > > This is rather interesting. We use tg3 cards on many of our boxes > > > and haven''t had problems. > > > To be specific, it''s the builtin NIC for the Dell Poweredge 850. > > Tigon3 [partno(BCM95721) rev 4101 PHY(5750)] (PCIX:100MHz:32-bit) > > > > > It should only be peth0 that needs to do autonegotation. > Please can > > > you try a more minimal version of your patch that just perturbs > > > peth0. > > > > Also, rather than "sleep 5", could you try polling for the link > > > status going "up". > > > How about this: http://pastebin.ca/33278 > > I have the same problem on a SunFire X2100 with the tg3 > driver. The patch at the above URL fixes the problem. > Apparently it just takes a while for the device to > auto-negotiate and therefore merging the device into the > bridge fails. Waiting for the device to come up fixes the problem.I suspect this is provoked by the ethernet switch you have it connected to. I''ve noticed that some of our Dell switches are rather slower to do autonegotiation than any of our other brands. Quite why the link needs to be up before adding the device to the bridge is unclear. That smacks of a tg3 driver bug, perhaps a race updating dev->flags. Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users