[ovs-discuss] [e1000:bugs] #357 Intel 82546GB chip does not work with OpenVSwitch
jesse at nicira.com
Tue Sep 11 16:32:31 UTC 2012
OVS doesn't clear NETIF_F_HW_VLAN_RX but it's possible that something else
does. In any case, the driver must support stripping and insertion
independently and if the hardware doesn't support it then it must set the
feature flags so that things get emulated appropriately.
On Tue, Sep 11, 2012 at 1:02 AM, Timm Essigke
<Timm.Essigke at uni-bayreuth.de>wrote:
> Dear OVS developers,
> some days ago (09/04/12) I reported my problems with Intel PCI-X NICs on
> this mailing list. Jesse Gross considered it as a driver problem and
> pointed me to the e1000 mailing list.
> Jesse Brandeburg (Intel) kindly analyzed the problem and plays the ball
> back to your side (see below).
> Can you please join the discussion?
> Thank you!
> -------- Original Message -------- Subject: [e1000:bugs] #357 Intel
> 82546GB chip does not work with OpenVSwitch Date: Tue, 11 Sep 2012
> 01:11:46 +0000 From: Jesse Brandeburg <go_jesse at users.sf.net><go_jesse at users.sf.net> Reply-To:
> [e1000:bugs] <357 at bugs.e1000.p.re.sf.net> <357 at bugs.e1000.p.re.sf.net> To:
> [e1000:bugs] <357 at bugs.e1000.p.re.sf.net> <357 at bugs.e1000.p.re.sf.net>
> I found why you don't see any transmits. CTRL.VME is not set
> (0x40000000) and needs to be for the hardware to insert the vlan tag on
> transmit. So your hardware is currently transmitting untagged frames when
> openvswitch enabled the vlan. This appears to be (unverified) because
> openvswitch is actively clearing the netdev->features flag
> NETIF_F_HW_VLAN_RX, and then doesn't read the features mask back afterward
> to find out that our e1000 hardware no longer supports tag insertion.
> * bugs:357 Intel 82546GB chip does not work with OpenVSwitch*
> *Status:* open *Labels:* e1000 *Created:* Mon Sep 10, 2012 09:45 AM UTC
> by T. Essigke *Last Updated:* Tue Sep 11, 2012 12:29 AM UTC *Owner:*Jesse Brandeburg
> The 82546GB chip does not work with OpenVSwitch, while similar chips do.
> It works with the old vlan/bridge code. In the attachement is a script to
> reproduce the problem and the output of ethregs.
> Here is a summary of the results:
> vlan/bridge openvswitch
> ping ethregs ping ethregs
> 80003ES2 + - + -
> 80003ES2_iomem + + + +
> 80003ES2_iomem_run2 + + + +
> 82546GB + + - +
> 82546GB_iomem + + - +
> 82546GB_iomem_run2 - + - +
> Maybe it is an initialization issue of the card.
> For more details see my mails on the e1000-devel mailing list.
> Sent from sourceforge.net because you indicated interest in
> To unsubscribe from further messages, please visit
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the discuss