Gary-
Have you/can you run the apport-collect command (Note #2 in the bug)
yet, and submit the results?
On 03/21/2014 03:56 PM, Gary Gaydos wrote:
See the above three log files, 2 with iperf and 1 with netperf.
iperf is equivalent between 3.11.0-15-generic and 3.13.6 upstream kernel
when
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
DistroRelease: Ubuntu 12.04
InstallationMedia: Ubuntu-Server 12.04.4 LTS Precise Pangolin - Release amd64
(20140204)
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
I've performed some further experiments. I reran the netperf and iperf
tests while using the iptraf tool to validate the netperf and iperf
results.
Iptraf is within a few percent of netperf and iperf in all cases except
iperf tcp stream. Iperf tcp stream shows 9.4 Gb/s, iptraf shows 2.7
Gb/s
** Attachment added: iperf running 3.13.6 upstream kernel on 12.04.4
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291660/+attachment/4036407/+files/iperf_3.13.6_upstream.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Attachment added: iperf running 3.11.o-15-generic kernel on 12.04.4
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291660/+attachment/4036409/+files/iperf_3.11.0-15-generic.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Attachment added: netperf with 3.13.6 upstream kernel on 12.04.4
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291660/+attachment/4036406/+files/netperf_3.13.6_upstream.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
See the above three log files, 2 with iperf and 1 with netperf.
iperf is equivalent between 3.11.0-15-generic and 3.13.6 upstream kernel
when running point to point (no switch). TCP stream is as expected.
UDP stream is poor in both cases.
netstat results are significantly different than iperf
On 03/21/2014 03:56 PM, Gary Gaydos wrote:
See the above three log files, 2 with iperf and 1 with netperf.
iperf is equivalent between 3.11.0-15-generic and 3.13.6 upstream kernel
when running point to point (no switch). TCP stream is as expected.
UDP stream is poor in both cases.
** Attachment added: eth0 (ixgbe) connected to the switch and another ixgbe on
another system
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291660/+attachment/4032864/+files/eth0_switch.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Attachment added: eth0 (ixgbe) connected point to point to another ixgbe on
another system
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291660/+attachment/4032866/+files/eth0_ptp.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Attachment added: eth1 (ixgbe) connected to the switch and another ixgbe on
another system
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291660/+attachment/4032868/+files/eth1_switch.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Attachment added: eth1 (ixgbe) connected point to point to another ixgbe on
another system
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291660/+attachment/4032867/+files/eth1_ptp.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Attachment added: eth0 (ixgbe) connected to the switch and another ixgbe on
another system
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291660/+attachment/4032865/+files/eth0_switch.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
See the attached eth*.log files attached above.
I ran ethtool, pings, and netperf on eth0 and eth1 in two different
configurations. One configuration is with eth0 and eth1 directly
connected to 10 Gb ixgbe adapters on another system. These are labeled
ptp for point to point. I ran the same
Tim, I'm no longer on-site and do not have access to this. I've
subscribed Mark Brown who is the IBM TPM. Mark, can you see if you can
work with Gary and help find out if 10Gb works at all on those systems
at all?
--
You received this bug notification because you are a member of Kernel
Have contacted IBM for further information.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1291660
Title:
Intel ixgbe driver doesn't work at 10Gb speeds
Status in “linux” package in
Tried the mainline which provides ixgbe version3.19.1-k
Same result. Card connects at 1Gb and forcing it to 10Gb via teh tool
results in the Unknown! Message for speed and duplex and the link is
shit down.
--
You received this bug notification because you are a member of Kernel
Packages, which
Jeff - do you know that 10Gbit works ? Could it be cabling or switch
related ? Can you test an older release ? ixgbe has supported 10Gbit for
awhile now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Note that you've _also_ got an igb device which is 1 Gbit only.
[5.207985] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.0.5-k
[5.207986] igb: Copyright (c) 2007-2013 Intel Corporation.
[5.208101] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version
3.13.10-k
[
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.13 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
this tarball has the results of sosreport and a few other things that
demonstrate the bug above.
** Attachment added: ixgbe-bug.tar.gz
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291660/+attachment/4021147/+files/ixgbe-bug.tar.gz
--
You received this bug notification because you
21 matches
Mail list logo
