[Bug 207537] wireless does not associate properly - AR9565

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207537

            Bug ID: 207537
           Summary: wireless does not associate properly - AR9565
           Product: Base System
           Version: 10.3-BETA2
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: wireless
          Assignee: freebsd-wireless at FreeBSD.org
          Reporter: ntremble at gmail.com
                CC: freebsd-amd64 at FreeBSD.org
                CC: freebsd-amd64 at FreeBSD.org

Created attachment 167466
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=167466&action=edit
dmesg with AR9565 active and non-functional

Generic kernel, 10.3-BETA3 (same issue with 10.3-BETA2 and 10.2-RELEASE).
HP 15-d070TU laptop.

As of this morning I am running 10.3-BETA3, upgraded from 10.2-BETA2 using
freebsd-update -r 10.3-BETA3 upgrade, but all comments below apply to
10.3-BETA3, 10.3-BETA2 and 10.2-RELEASE at least.

uname -a:
FreeBSD frog 10.3-BETA3 FreeBSD 10.3-BETA3 #0 r296074: Fri Feb 26 01:13:37 UTC
2016     root at releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64

When I enable the AR9565 Wi-Fi in my laptop the system makes all the right
noises but cannot start dhclient. The ath0 interface shows as associated but
wlan0 shows no carrier. The extract below shows this. Full logs and
configuration files are attached.

The visible symptoms are that the system regularly emits messages such as:
"ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping" and the wireless
interface is unable to route packets.

The wired ethernet goes to the same router and functions perfectly. This issue
with the wireless was *not* present in 11.0-CURRENT when I last tried it a
couple of months back, and the wireless in this same laptop worked perfectly
with the same router and an unchanged configuration.

The closest match I can find is this one, which has similar symptoms but the
requester did not respond to the last question: #188415. My response to that
question is that I am running the generic kernel fresh from the freebsd-update
process.


neilt at frog:~ % ifconfig
...
ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 2290
        ether b8:ee:65:39:de:46
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng
        status: associated
...
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether b8:ee:65:39:de:46
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
        status: no carrier
        ssid "" channel 11 (2462 MHz 11g ht/20)
        regdomain 106 indoor ecm authmode WPA2/802.11i privacy ON
        deftxkey UNDEF txpower 20 bmiss 7 scanvalid 60 protmode CTS
        ampdulimit 8k ampdudensity 8 shortgi wme burst roaming MANUAL
neilt at frog:~ % 

loader.conf:
 kern.vty=vt
 if_ath_load="YES"
 fuse_load="YES"
 vboxdrv_load="YES"

rc.conf:
 hostname="frog"
 ifconfig_re0="DHCP"
 wlans_ath0="wlan0"
 ifconfig_wlan0="WPA SYNCDHCP"
 sshd_enable="YES"
 powerd_enable="YES"
 dumpdev="AUTO"
 fusefs_enable="YES"
 devfs_system_ruleset="localrules"
 dbus_enable="YES"
 hald_enable="YES"
 #kdm4_enable="YES"
 lpd_enable="YES"
 vboxnet_enable="YES"
 devfs_system_ruleset="system"

wpa_supplicant.conf:
 network={
        ssid="my ssid"
        psk="my psk"
 }

-- 
You are receiving this mail because:
You are on the CC list for the bug.