>> Do you want the test program I am using? It is a pretty basic
>> send()/recv() program, ~650 lines of C.
>>
>> Tony
>>
>>
>
> Not really, iperf drives the problem fine.
>
>
Thanks for the tip; I hadn't tried iperf before today. I can reproduce
the problem with "iperf -s" on the system
On Tue, 13 Nov 2007 17:57:12 -0500
Tony Battersby <[EMAIL PROTECTED]> wrote:
> Stephen Hemminger wrote:
> > I can reproduce the problem under load with only a single port on 2.6.23.
> > I haven't been able to reproduce it on 2.6.24-rc2 (latest) but that maybe
> > because of either insufficient str
Stephen Hemminger wrote:
> I can reproduce the problem under load with only a single port on 2.6.23.
> I haven't been able to reproduce it on 2.6.24-rc2 (latest) but that maybe
> because of either insufficient stress or another bug fix correcting the
> problem. There is an issue with Yukon XL upda
On Tue, 13 Nov 2007 12:51:33 -0500
Tony Battersby <[EMAIL PROTECTED]> wrote:
> I am getting "hw csum failure" messages with sky2. I have seen this
> problem reported elsewhere with a fibre NIC, but I am using a copper
> NIC. It seems to be triggered by SMP. It is easy to reproduce in
> 2.6.23.
I am getting "hw csum failure" messages with sky2. I have seen this
problem reported elsewhere with a fibre NIC, but I am using a copper
NIC. It seems to be triggered by SMP. It is easy to reproduce in
2.6.23. 2.6.24-rc2-git3 still has the problem, but it happens less
frequently.
To reproduce
