All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob <jacob.winther@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Issues with ar5418
Date: Sat, 18 Oct 2008 03:39:27 +0000 (UTC)	[thread overview]
Message-ID: <loom.20081018T032153-976@post.gmane.org> (raw)

I have been running the latest wireless-testing for about 24 hours and generally
the card has been very stable. I've tested it with and without WPA/1.

There are a few issues though,  I also had the same issues with 2.6.27.1...

1) Whenever i run iperf, I get this many of these in the logs:
ath_tx_prepare: TX queue: 1 is full, depth: 492
ath_tx_prepare: TX queue: 1 is full, depth: 492

2) There is a big difference in speed upstream and downstream throughout, the
figures below are fairly constant:

Client connecting to XX, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  5] local 192.168.0.97 port 40407 connected with 192.168.0.3 port 5001
[  4] local 192.168.0.97 port 5001 connected with 192.168.0.3 port 41205
[ ID] Interval       Transfer     Bandwidth
[  5]  0.0-10.0 sec  27.0 MBytes  22.6 Mbits/sec
[  4]  0.0-12.3 sec  64.0 KBytes  42.8 Kbits/sec

3) If I run tcpdump the speeds drop considerably, below is a before and after
running tcpdump -i wla0

------------------------------------------------------------
[  3] local 192.168.0.97 port 57664 connected with 192.168.0.3 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec  28.6 MBytes  23.9 Mbits/sec

== after==

------------------------------------------------------------
Client connecting to isola, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 192.168.0.97 port 57665 connected with 192.168.0.3 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-12.1 sec  72.0 KBytes  48.9 Kbits/sec


I also had this in my logs:
tcpdump uses obsolete (PF_INET,SOCK_PACKET)


I hope to try out 802.11n later this week.

Cheers,
Jacob

--

02:00.0 Network controller: Atheros Communications Inc. AR5418 802.11abgn
Wireless PCI Express Adapter (rev 01)
	Subsystem: Apple Computer Inc. Device 0087
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 256 bytes
	Interrupt: pin A routed to IRQ 17
	Region 0: Memory@90100000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: ath9k
	Kernel modules: ath9k

wlan0     IEEE 802.11abgn  ESSID:"XX"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:1C:B3:AE:F8:30   
          Bit Rate=0 kb/s   Tx-Power=20 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B   
          Power Management:off
          Link Quality=59/100  Signal level:-56 dBm  Noise level=-94 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

             reply	other threads:[~2008-10-18  3:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-18  3:39 Jacob [this message]
2008-10-18  8:01 ` [ath9k-devel] Issues with ar5418 Benoit PAPILLAULT
2008-10-20 12:37   ` Luis R. Rodriguez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20081018T032153-976@post.gmane.org \
    --to=jacob.winther@gmail.com \
    --cc=ath9k-devel@lists.ath9k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.