Artem Naluzhnyy wrote: > Hi, > > After 7.2-RLEASE -> 8.0-BETA2 update my notebook wireless works > without problems but there are lots of annoying "ath0: bad series0 > hwrate 0x1b"-like messages on console now. > > ==================================================== > pciconf: > > ath0_at_pci0:1:0:0: class=0x020000 card=0x3065168c chip=0x001c168c > rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = > 'HDAUDIOFUNC_01&VEN_1095&DEV_1392&SUBSYS_10280242&REV_1000 > (USBVID_147E&PID_20165&B71A446&0&1)' > class = network > subclass = ethernet > > ==================================================== > sysctls: > > hw.ath.bstuck: 4 > hw.ath.txbuf: 200 > hw.ath.rxbuf: 40 > hw.ath.resetcal: 1200 > hw.ath.shortcal: 100 > hw.ath.longcal: 30 > hw.ath.hal.swba_backoff: 0 > hw.ath.hal.sw_brt: 10 > hw.ath.hal.dma_brt: 2 > dev.ath.0.%desc: Atheros 5424/2424 > dev.ath.0.%driver: ath > dev.ath.0.%location: slot=0 function=0 > dev.ath.0.%pnpinfo: vendor=0x168c device=0x001c subvendor=0x168c > subdevice=0x3065 class=0x020000 > dev.ath.0.%parent: pci1 > dev.ath.0.smoothing_rate: 95 > dev.ath.0.sample_rate: 10 > dev.ath.0.sample_stats: 0 > dev.ath.0.countrycode: 0 > dev.ath.0.regdomain: 96 > dev.ath.0.slottime: 9 > dev.ath.0.acktimeout: 48 > dev.ath.0.ctstimeout: 48 > dev.ath.0.softled: 0 > dev.ath.0.ledpin: 0 > dev.ath.0.ledon: 0 > dev.ath.0.ledidle: 2700 > dev.ath.0.txantenna: 0 > dev.ath.0.rxantenna: 1 > dev.ath.0.diversity: 1 > dev.ath.0.txintrperiod: 5 > dev.ath.0.diag: 0 > dev.ath.0.tpscale: 0 > dev.ath.0.tpc: 0 > dev.ath.0.tpack: 63 > dev.ath.0.tpcts: 63 > dev.ath.0.rfsilent: 1 > dev.ath.0.rfkill: 1 > dev.ath.0.intmit: 1 > dev.ath.0.monpass: 24 > > ==================================================== > dmesg: > > ath0: <Atheros 5424/2424> mem 0xbf7f0000-0xbf7fffff irq 17 at device 0.0 on pci1 > ath0: [ITHREAD] > ath0: AR5413 mac 10.0 RF5424 phy 6.1 > ath0: bad series0 hwrate 0x1b, tries 1 ts_status 0x0 > ath0: bad series0 hwrate 0x1b, tries 1 ts_status 0x0 > ath0: bad series3 hwrate 0x1b, tries 2 ts_status 0x0 > ath0: bad series0 hwrate 0x1b, tries 1 ts_status 0x0 > ath0: bad series2 hwrate 0x1c, tries 4 ts_status 0x0 > ath0: bad series3 hwrate 0x1b, tries 2 ts_status 0x0 > ath0: bad series3 hwrate 0x1b, tries 2 ts_status 0x0 > ath0: bad series3 hwrate 0x1b, tries 2 ts_status 0x0 > ath0: bad series3 hwrate 0x1b, tries 2 ts_status 0x0 > > ==================================================== > ifconfig: > > ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 2290 > ether 00:15:af:xx:xx:xx > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: associated > wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > ether 00:15:af:xx:xx:xx > inet xx.xx.xx.xx netmask 0xfffffff8 broadcast xx.xx.xx.xx > media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g > status: associated > ssid xx channel 3 (2422 Mhz 11g) bssid 00:1f:1f:xx:xx:xx > regdomain 96 indoor ecm authmode WPA2/802.11i privacy ON > deftxkey UNDEF TKIP 2:128-bit txpower 20 bmiss 7 scanvalid 450 bgscan > bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS > wme roaming MANUAL > ==================================================== > How often is "lots"? hw tx rate 0x1b is 1Mb/s CCK and 0x1c is 1M w/ short preamble. Both of these rates should be ok to use in 11g so I don't see why there are complaints unless the ap you are associated to is doing something like forcing 11g-only operation (i.e. OFDM only, no CCK). However even with that you should be fine unless perhaps fixed tx rate parameters are set wrong. Not sure there's a way to dump the negotiated rate set. You can try turning on something like: wlandebug assoc to see if that provides useful info. Otherwise you might need to collect a packet trace with something like: tcpdump -i wlan0 -p -y IEEE802_11_RADIO -w t.pcap while associating--then inspect the results (and/or send me the pcap file). SamReceived on Sat Jul 18 2009 - 16:37:18 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:52 UTC