[ath9k-devel] 2.6.28-rc7-wl

[Brian <bnc@astronomicalresearchaustralia.org>]

Luis,
> So do some other test -- run bitorrent, or iperf. That should rule out
> ath9k.
> 
Yes I was trying that, in the process of setting up ftp.

> To test if its NX try testing it over a wired ethernet connection.
> 
Yes, I should have thought of that, however I have problems with my eth0
port.

Anyway while looking around the nomachine site I found that my version
of NX was pretty old. So I downloaded the latest.

Some observations

1) I have been up for over an hour on NX
2) The number of errors being generated  are a LOT less, I am collecting
stats.
3) I have changed the bandwidth back to 20mhz so I am only getting 54Mbs
at the moment.

So the main reason I upgraded was because I felt that NX was causing the
large number of TX/RX errors. I think has proved correct, but I will not
know for sure until I put the bandwidth back up to 40mhz.

If this proves to be correct then I think the driver has a problem as
there is no way that errors should cause such a hard lockup.
So my question is how does the driver handle the fact that packets go
missing? Or is this problem handled further up in the tcp stack.

Brian