Hi, Denis
> Takayuki, have you tested it on 5ghz band?
  blow shows my test result with channel 48, which is 5.24GHz.
  I also got the pretty good throughput for 5GHz with 2.6.39-rc5-wl.

  BTW, did you use fixed frequency in your test ?  In my case, the 
channel is fixed to 48 as show below.

root@RMR1:/# ifconfig wlan0
wlan0     Link encap:Ethernet  HWaddr 00:0E:8E:13:A9:F6
           inet addr:10.0.1.72  Bcast:10.0.1.255  Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:18513 errors:0 dropped:0 overruns:0 frame:0
           TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:27980008 (26.6 MiB)  TX bytes:3672 (3.5 KiB)

root@RMR1:/# iwconfig wlan0
wlan0     IEEE 802.11abg  ESSID:"test48"
           Mode:Ad-Hoc  Frequency:5.24 GHz  Cell: 56:3E:BD:4D:5D:91
           Tx-Power=20 dBm
           RTS thr:off   Fragment thr:off
           Encryption key:off
           Power Management:off

root@RMR1:/# iperf -s -u -i 3.0      (==> command at the peer node : 
iperf -c 10.0.1.72 -u -b 20M -t 100 )
------------------------------------------------------------
Server listening on UDP port 5001
Receiving 1470 byte datagrams
UDP buffer size:   108 KByte (default)
------------------------------------------------------------
[  3] local 10.0.1.72 port 5001 connected with 192.168.1.242 port 54899
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3]  0.0- 3.0 sec  7.16 MBytes  20.0 Mbits/sec  0.170 ms    0/ 5105 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3]  3.0- 6.0 sec  7.15 MBytes  20.0 Mbits/sec  0.250 ms    0/ 5103 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3]  6.0- 9.0 sec  7.14 MBytes  20.0 Mbits/sec  0.499 ms    0/ 5093 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3]  9.0-12.0 sec  7.17 MBytes  20.0 Mbits/sec  0.244 ms    0/ 5112 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3] 12.0-15.0 sec  7.15 MBytes  20.0 Mbits/sec  0.107 ms    0/ 5103 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3] 15.0-18.0 sec  7.15 MBytes  20.0 Mbits/sec  0.253 ms    0/ 5101 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3] 18.0-21.0 sec  7.15 MBytes  20.0 Mbits/sec  0.239 ms    0/ 5103 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3] 21.0-24.0 sec  7.15 MBytes  20.0 Mbits/sec  0.218 ms    0/ 5103 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3] 24.0-27.0 sec  7.15 MBytes  20.0 Mbits/sec  0.172 ms    0/ 5102 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3] 27.0-30.0 sec  7.14 MBytes  20.0 Mbits/sec  0.483 ms    0/ 5095 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3] 30.0-33.0 sec  7.16 MBytes  20.0 Mbits/sec  0.307 ms    0/ 5110 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3] 33.0-36.0 sec  7.15 MBytes  20.0 Mbits/sec  0.175 ms    0/ 5103 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3] 36.0-39.0 sec  7.15 MBytes  20.0 Mbits/sec  0.285 ms    0/ 5102 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3] 39.0-42.0 sec  7.15 MBytes  20.0 Mbits/sec  0.210 ms    0/ 5103 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3] 42.0-45.0 sec  7.15 MBytes  20.0 Mbits/sec  0.250 ms    0/ 5102 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3] 45.0-48.0 sec  7.15 MBytes  20.0 Mbits/sec  0.218 ms    0/ 5102 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3] 48.0-51.0 sec  7.15 MBytes  20.0 Mbits/sec  0.368 ms    0/ 5097 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3] 51.0-54.0 sec  7.03 MBytes  19.7 Mbits/sec  0.182 ms   91/ 5107 (1.8%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3] 54.0-57.0 sec  7.16 MBytes  20.0 Mbits/sec  0.250 ms    0/ 5104 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3] 57.0-60.0 sec  7.15 MBytes  20.0 Mbits/sec  0.308 ms    0/ 5099 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3] 60.0-63.0 sec  7.16 MBytes  20.0 Mbits/sec  0.250 ms    0/ 5105 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3] 63.0-66.0 sec  7.15 MBytes  20.0 Mbits/sec  0.277 ms    0/ 5102 (0%)
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total 
Datagrams
[  3] 66.0-69.0 sec  7.15 MBytes  20.0 Mbits/sec  0.247 ms    0/ 5103 (0%)


But, it went into the crash again as reported yesterday.  This seems to 
be a issue of wireless-testing rather than ath5k.

BUG: unable to handle kernel NULL pointer dereference at 00000002
IP: [<c895fc3b>] ieee80211_rx_handlers+0x6ab/0x1a90 [mac80211]
*pde = 00000000
Oops: 0000 [#1] PREEMPT
last sysfs file: /sys/devices/pci0000:00/0000:00:0f.0/ieee80211/phy1/index
Modules linked in: scx200_wdt xt_NOTRACK iptable_raw xt_state 
nf_defrag_ipv4 nf_conntrack pppoe pppox ipt_REJECT xt_TCPMSS ipt_LOG 
xt_multiport xt_mac xt_limit iptable_mangle iptable_filte]

Pid: 0, comm: swapper Not tainted 2.6.39-rc5-wl #1
EIP: 0060:[<c895fc3b>] EFLAGS: 00010282 CPU: 0
EIP is at ieee80211_rx_handlers+0x6ab/0x1a90 [mac80211]
EAX: 00000000 EBX: c7bc1800 ECX: 00000001 EDX: c7a42634
ESI: c7809ee4 EDI: c7bb6022 EBP: c7809e54 ESP: c7809dd4
  DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
Process swapper (pid: 0, ti=c7808000 task=c139e300 task.ti=c1398000)
Stack:
  0000003b c7809dec c1003f02 00000030 c7809e34 c7809e40 00000000 c7bc1800
  c128f863 c7ae8364 c7809e14 c7809ee4 c7a42360 c7809e20 c7809e20 c1003f02
  00000030 c7809e20 c102cdc3 c7809e00 00000000 ffffffff c7a42360 c7b91c18
Call Trace:
  [<c1003f02>] ? handle_irq+0x12/0x80
  [<c128f863>] ? do_IRQ+0x43/0x8d
  [<c1003f02>] ? handle_irq+0x12/0x80
  [<c102cdc3>] ? irq_exit+0x43/0x60
  [<c1206914>] ? skb_queue_tail+0x54/0x60
  [<c8961266>] ieee80211_prepare_and_rx_handle+0x246/0x8a0 [mac80211]
  [<c1208802>] ? __alloc_skb+0x32/0x120
  [<c8961c24>] ieee80211_rx+0x2e4/0x970 [mac80211]
  [<c1208831>] ? __alloc_skb+0x61/0x120
  [<c89e5ce8>] ath5k_tasklet_rx+0x308/0x850 [ath5k]
  [<c1003f02>] ? handle_irq+0x12/0x80
  [<c102cdc3>] ? irq_exit+0x43/0x60
  [<c128f863>] ? do_IRQ+0x43/0x8d
  [<c102c846>] tasklet_action+0xb6/0xd0
  [<c102cfc7>] __do_softirq+0x77/0x1b0
  [<c102cf50>] ? irq_enter+0x50/0x50


_______________________________________________
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel

Reply via email to