Tony Battersby wrote:
> "iperf -c 192.168.1.1" never finishes, but "iperf -c 192.168.2.1" does
> finish. Press Ctrl-C to abort the hung iperf. Ping 192.168.1.1 does
> not respond. Ping 192.168.2.1 does respond, but each ping has almost
> exactly 1 second latency (the latency should be < 1 ms).
>
Brandeburg, Jesse wrote:
> make sure to disable the default Linux arp behavior for this kind of
> test on PC3 by*
> [EMAIL PROTECTED] echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter
> [EMAIL PROTECTED] echo 1 > /proc/sys/net/ipv4/conf/eth0/arp_filter
> [EMAIL PROTECTED] echo 1 > /proc/sys/net/ipv4/
Tony Battersby wrote:
> I am experiencing network tx hangs on a dual-port SK-9E22 with sky2 in
> 2.6.24. The problem is triggered by both ports transmitting at high
> speed simultaneously. This problem is 100% quickly reproducible.
> Here is the setup:
>
> PC #1 with Intel PRO/1000 NIC:
> e1000
> What bus and chipset is in use on the systems with sky2?
> I have seen problems when using PCI-X on AMD systems (documented in AMD
> errata)
> due to multiple outstanding transactions.
Motherboard: SuperMicro PDSME
Chipset: Intel E7230
Processor: Intel Pentium D 3.4 GHz
(note: tried both SMP a
On Mon, 28 Jan 2008 13:43:19 -0500
Tony Battersby <[EMAIL PROTECTED]> wrote:
> I am experiencing network tx hangs on a dual-port SK-9E22 with sky2 in
> 2.6.24. The problem is triggered by both ports transmitting at high
> speed simultaneously. This problem is 100% quickly reproducible. Here
> i
I am experiencing network tx hangs on a dual-port SK-9E22 with sky2 in
2.6.24. The problem is triggered by both ports transmitting at high
speed simultaneously. This problem is 100% quickly reproducible. Here
is the setup:
PC #1 with Intel PRO/1000 NIC:
e1000 IP address 192.168.1.1
running iper
