RE: [Xen-users] Solved: network problems when starting xend, Xen-3.0 + tg3

["Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>]

> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users