Hi Jesse,
thank you for picking up my problem!
I made a script and ran it on my system. Attached is the script and the
output. So it should be very easy for you to reproduce my problem.
At the top of the script you need to make some adjustments for your
network; the only command line argument is the interface name.
I thought it makes sense to have the output of the working 80003ES2 NIC
and the problematic 82546GB NIC for comparison. However, ethregs
required booting with iomem=relaxed (_iomem) to work for the former. I
realized that for the 82546GB chip it makes a difference if the
openvswitch modules were loaded before or not. So I started all my runs
with a cold-booted system with the openvswitch modules blacklisted. I
demonstrate the effect of previously loaded openvswitch modules with the
_run2 files which were generated by a second run of the script right
after the first run.
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.
I hope you can understand the cause of the problem from the ethregs
output included in the files.
Thank you very much!
Timm
On 09/05/2012 10:29 PM, Jesse Brandeburg wrote:
On Wed, 5 Sep 2012 17:13:52 +0200
Timm Essigke <timm.essi...@uni-bayreuth.de> wrote:
First, I asked on the openvswitch mailing list and they consider it as a
driver problem.
My system is:
Ubuntu 12.04
Supermicro: Kernel 3.2.0-29-generic, 64-bit
Fujitsu: Kernel 3.2.0-29-generic-pae, 32-bit
Openvswitch 1.4.0-1ubuntu1.2
thanks for the report, myself or one of my team members will take a
quick pass at reproducing this issue, sounds like it won't be too
difficult to repro.
My initial thought is that the vlan code may not be fully working in
e1000, or that openvswitch needs set_rx_mode support.
The thing that would help me most would be a register dump when it
works (configured with vlan) and when it doesn't (with openvswitch)
the tool is called ethregs and is available from e1000.sf.net, the tool
is self documenting, but would be best run like so:
ethtool -i ethX
ethregs -c -o -s <bus:dev.fn from above> > regdump.txt
Thanks,
Jesse
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit
http://communities.intel.com/community/wired
--
========================================
Dr. Timm Essigke
Structural Biology/Bioinformatics
University of Bayreuth
Universitätsstr. 30, BGI
95447 Bayreuth
Germany
Telephone: +49-921-55-3547
Fax: +49-921-55-3071
e-mail: timm.essi...@uni-bayreuth.de
http://www.bisb.uni-bayreuth.de/
========================================
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit
http://communities.intel.com/community/wired
