[ath9k-devel] 2.6.28-rc7-wl

[Luis R. Rodriguez <lrodriguez@atheros.com>]

On Thu, Dec 04, 2008 at 03:38:09PM -0800, Brian wrote:
> 
> 
> Luis,
> 
> >> So I think the driver could be fine, it could be application specific.
> >> Will also do a search of the NX site and see if they have any problems.
> >>
> >> Will let you know how I go.
> >
> > I see.. What is NX?
> http://www.nomachine.com/
> NX is really great and is easily the best remote control software.
> While I can get by with krdc I want to use NX if I can.
> 
> We run tests against ath9k over hours too and
> > I don't think we've seen this memory hog issue. But if your userspace
> > application is hogging up application your kernel shoulod not panic,
> > unless of course some -ENOMEM as part of your drivers is not being
> > handled correctly. But the patches merged recently actually handle this
> > for ath9k :) I at least have tested it with mem=200 and even using the
> > swiotlb.
> >
> Yes I saw that you had included the -ENOMEM fix, so I was very hopeful
> that the problem would go away.
> I must say the difference between rc6 and rc7 is really significant.
> Things are quicker and more stable for all the normal operations.
> I just do not see what is different about NX, I might try running
> wireshark on it. If you could fire up NX and it fails then at least we
> could say that it is not specific to my machine.
> I should also point out that when researching this problem on the web I
> found that hundreds of people were having the same freezing problem.
> 
> My krdc has been running for 30mins with no problems, but the memory is
> going up.
> 
> Back in a bit

So do some other test -- run bitorrent, or iperf. That should rule out
ath9k.

To test if its NX try testing it over a wired ethernet connection.

  Luis