From owner-freebsd-amd64@freebsd.org Sat Feb 27 04:36:20 2016 Return-Path: Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0EE8AB6423 for ; Sat, 27 Feb 2016 04:36:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B218115D5 for ; Sat, 27 Feb 2016 04:36:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u1R4aKFB039633 for ; Sat, 27 Feb 2016 04:36:20 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 207537] wireless does not associate properly - AR9565 Date: Sat, 27 Feb 2016 04:36:17 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 10.3-BETA2 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ntremble@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Sat, 27 Feb 2016 12:07:13 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Feb 2016 04:36:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207537 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@FreeBSD.org Reporter: ntremble@gmail.com CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Created attachment 167466 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D167466&action= =3Dedit 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@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 is= sue 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-upd= ate process. neilt@frog:~ % ifconfig ... ath0: flags=3D8843 metric 0 mtu 2290 ether b8:ee:65:39:de:46 nd6 options=3D21 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: associated ... wlan0: flags=3D8843 metric 0 mtu 15= 00 ether b8:ee:65:39:de:46 nd6 options=3D29 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@frog:~ %=20 loader.conf: kern.vty=3Dvt if_ath_load=3D"YES" fuse_load=3D"YES" vboxdrv_load=3D"YES" rc.conf: hostname=3D"frog" ifconfig_re0=3D"DHCP" wlans_ath0=3D"wlan0" ifconfig_wlan0=3D"WPA SYNCDHCP" sshd_enable=3D"YES" powerd_enable=3D"YES" dumpdev=3D"AUTO" fusefs_enable=3D"YES" devfs_system_ruleset=3D"localrules" dbus_enable=3D"YES" hald_enable=3D"YES" #kdm4_enable=3D"YES" lpd_enable=3D"YES" vboxnet_enable=3D"YES" devfs_system_ruleset=3D"system" wpa_supplicant.conf: network=3D{ ssid=3D"my ssid" psk=3D"my psk" } --=20 You are receiving this mail because: You are on the CC list for the bug.=