Hm, what's in your kenrel config file? Is ENABLE_11N or whatever the ath driver option there? sysctl dev.ath.0.txagg=1 ; then check dmesg and output me the results. Thanks! -a On 24 November 2015 at 14:50, José Pérez <fbl_at_aoek.com> wrote: > Dear Svatopluk, > tried again with current, and I get (almost) the same: > Nov 23 18:14:47 current kernel: ath0: ath_edma_rxbuf_alloc: nothing on > rxbuf?! > Nov 23 18:14:47 current kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc > failed: i=0, nbufs=128? > Nov 23 18:14:47 current kernel: ath0: ath_edma_rxbuf_alloc: nothing on > rxbuf?! > Nov 23 18:14:47 current kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc > failed: i=1, nbufs=128? > > Ideas? Can I help? > > Thank you. > > Regards, > > > --- > José Pérez > > > El 2015-11-23 13:45, Svatopluk Kraus escribió: >> >> On Mon, Nov 23, 2015 at 1:12 PM, José Pérez <fbl_at_aoek.com> wrote: >>> >>> Hi, >>> I am the (happy?) owner of an Atheros AR9565 which used to work just >>> fine. >>> >>> I recently updated an old -current, and a flood of these messages bumped >>> up: >>> Nov 13 17:47:16 test kernel: ath0: ath_edma_rxbuf_alloc: nothing on >>> rxbuf?! >>> Nov 13 17:47:16 test kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc >>> failed: >>> i=24, nb >>> ufs=128? >>> >>> # pciconf -lv | relevant_part >>> ath0_at_pci0:1:0:0: class=0x028000 card=0x064211ad chip=0x0036168c >>> rev=0x01 hdr=0x00 >>> vendor = 'Qualcomm Atheros' >>> device = 'QCA9565 / AR9565 Wireless Network Adapter' >>> class = network >>> >>> # dmesg | relevant_part >>> ath0: <Qualcomm Atheros AR9565> mem 0xf0800000-0xf087ffff irq 32 at >>> device >>> 0.0 on pci1 >>> ath0: WB335 2-ANT card detected >>> ar9300_attach: calling ar9300_hw_attach >>> ar9300_hw_attach: calling ar9300_eeprom_attach >>> ar9300_flash_map: unimplemented for now >>> Restoring Cal data from DRAM >>> Restoring Cal data from EEPROM >>> Restoring Cal data from Flash >>> Restoring Cal data from Flash >>> Restoring Cal data from OTP >>> ar9300_hw_attach: ar9300_eeprom_attach returned 0 >>> ath0: [HT] enabling HT modes >>> ath0: [HT] enabling short-GI in 20MHz mode >>> ath0: [HT] 1 stream STBC receive enabled >>> ath0: [HT] 1 RX streams; 1 TX streams >>> ath0: AR9565 mac 704.1 RF5110 phy 2261.3 >>> ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0000 >>> >>> # ifconfig | relevant_part >>> wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu >>> 1500 >>> ether a4:db:30:ab:ad:ca >>> inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 >>> nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> >>> media: IEEE 802.11 Wireless Ethernet MCS mode 11ng >>> status: associated >>> ssid myssid channel 6 (2437 MHz 11g ht/20) bssid >>> de:ad:be:ee:ee:ef >>> regdomain ETSI2 country ES indoor ecm authmode WPA2/802.11i >>> privacy ON deftxkey UNDEF AES-CCM 2:128-bit AES-CCM 3:128-bit >>> txpower 30 bmiss 7 scanvalid 60 protmode CTS ampdulimit 64k >>> ampdudensity 4 shortgi wme burst roaming MANUAL >>> groups: wlan >>> >>> >>> >>> Is there anything I can help with to improve this? Thank you. >>> >> >> What revision do you use? If you use <r291142, r291192>, please, try >> to update to r291193 or higher. >> >> Svatopluk Kraus >> >> >> >>> Regards, >>> >>> -- >>> José Pérez >>> _______________________________________________ >>> freebsd-current_at_freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to >>> "freebsd-current-unsubscribe_at_freebsd.org" >> >> _______________________________________________ >> freebsd-current_at_freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" > > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"Received on Tue Nov 24 2015 - 23:18:57 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:01 UTC