From owner-freebsd-stable@FreeBSD.ORG Sat Nov 22 18:11:51 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9DDC43C8 for ; Sat, 22 Nov 2014 18:11:51 +0000 (UTC) Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3644986 for ; Sat, 22 Nov 2014 18:11:51 +0000 (UTC) Received: by mail-wi0-f176.google.com with SMTP id ex7so2127815wid.9 for ; Sat, 22 Nov 2014 10:11:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=tgd/8cBLzziaLcGps1i0yQxx+zLePLGd4xJ9q7o6dl0=; b=nAEDJt6y1wDfLNsAJJQVh0Qjyiozo8P7j0mJvYe/38Fw8SFd1svRQh7ihIukOcXtlg MoSa4ewO4sd/XiP6UfsuV6Dr0HeTjkonhXXSgmXjsRMvFTDtKsskcFNyc3K1NDx7Xu+O Fz1ZVV6oDWbgha6/okl/qpV0HdJiEOjdz9aK/dD34PdtBWZLiZBKz+K7VKrtSTrzAAyf vyOUk5num742xFwv6RjbaBwrXU5AoUir9ePg93ckPWXWdYpONV5LAFoJt5WrQui59MLo NSXmq34EbykZ9aEfAYnxCw1rSe1QHBQnRSI8lKtl2k9vyYmdnoTnuITZPrqiNxLmwT/w q8RA== MIME-Version: 1.0 X-Received: by 10.180.99.105 with SMTP id ep9mr7540667wib.26.1416679909574; Sat, 22 Nov 2014 10:11:49 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.106.136 with HTTP; Sat, 22 Nov 2014 10:11:49 -0800 (PST) In-Reply-To: <5470C695.3040204@yahoo.com.br> References: <20141122171734.GA4600@marvin2011.fritz.box> <5470C695.3040204@yahoo.com.br> Date: Sat, 22 Nov 2014 10:11:49 -0800 X-Google-Sender-Auth: yfpgEnO13X7KmvOwoAz14LwVECk Message-ID: Subject: Re: ath(4) device timeout -> reboot necessary From: Adrian Chadd To: Danilo Egea Gondolfo Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Stable Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Nov 2014 18:11:51 -0000 sniffle! Try setting sysctl dev.ath.0.hal.force_full_reset=1 But the reason the AR9287 is going deaf is still unknown. In station mode we detect it by seeing missed beacons and doing a hardware reset. In AP mode we don't have that; we just see it failing to do noise floor calibration and we never hear any frames. We just need to schedule a full hardware reset if the noise floor calibration fails. There are also issues with wpa_supplicant being run more than once at a time due to issues with the rc script side of things and it's confusing the wifi drivers. I haven't really looked into it in that much detail - I was hoping the RC scripts would be fixed, but I'm going to have to fix the driver to at least not confuse the hardware. (Yes, we have to fix the "running multiple copies of wpa_supplicant - as it's going to mess things up no matter what we do.) -adrian On 22 November 2014 at 09:23, Danilo Egea Gondolfo wrote: > > On 11/22/14 15:17, Thomas Zander wrote: >> >> Hi, >> >> regularly[1] I get those on my workstation: >> >> Nov 22 10:52:15 marvin2011 kernel: ath0: device timeout >> Nov 22 13:31:43 marvin2011 kernel: ath0: device timeout >> Nov 22 13:52:54 marvin2011 kernel: ath0: device timeout >> Nov 22 16:50:05 marvin2011 kernel: ath0: device timeout >> >> Weren't there logs, most of the time I would not even notice, but >> sometimes the machine loses connection to the AP, and when that >> happens, I first try to disable wpa_supplicant and restart the >> interface. Rarely[2] this works, but most of the time, this happens: >> >> Nov 22 16:53:37 marvin2011 kernel: wlan0: link state changed to DOWN >> Nov 22 16:53:37 marvin2011 dhclient[339]: connection closed >> Nov 22 16:53:37 marvin2011 dhclient[339]: exiting. >> Nov 22 16:53:37 marvin2011 wpa_supplicant[327]: ioctl[SIOCS80211, op=20, >> val=0, arg_len=7]: Device not configured >> Nov 22 16:53:37 marvin2011 last message repeated 3 times >> Nov 22 16:53:37 marvin2011 wpa_supplicant[327]: ioctl[SIOCS80211, op=25, >> val=0, arg_len=0]: Device not configured >> Nov 22 16:53:37 marvin2011 wpa_supplicant[327]: ioctl[SIOCS80211, op=95, >> val=208, arg_len=0]: Device not configured >> Nov 22 16:53:37 marvin2011 wpa_supplicant[327]: ioctl[SIOCS80211, op=17, >> val=0, arg_len=0]: Device not configured >> Nov 22 16:53:37 marvin2011 wpa_supplicant[327]: ioctl[SIOCS80211, op=26, >> val=0, arg_len=0]: Device not configured >> Nov 22 16:53:37 marvin2011 wpa_supplicant[327]: ioctl[SIOCS80211, op=95, >> val=208, arg_len=0]: Device not configured >> Nov 22 16:53:37 marvin2011 wpa_supplicant[327]: ioctl[SIOCS80211, op=17, >> val=0, arg_len=0]: Device not configured >> Nov 22 16:53:37 marvin2011 wpa_supplicant[327]: ioctl[SIOCS80211, op=26, >> val=0, arg_len=0]: Device not configured >> Nov 22 16:53:37 marvin2011 wpa_supplicant[327]: ioctl[SIOCS80211, op=16, >> val=1, arg_len=0]: Device not configured >> Nov 22 16:53:37 marvin2011 wpa_supplicant[327]: wlan0: >> CTRL-EVENT-TERMINATING >> Nov 22 16:53:37 marvin2011 riggs: /etc/rc.d/netif: WARNING: wlan0 does not >> exist. Skipped. >> Nov 22 16:54:27 marvin2011 kernel: wlan0: Ethernet address: >> Nov 22 16:54:27 marvin2011 devd: Executing '/etc/pccard_ether wlan0 start' >> Nov 22 16:54:27 marvin2011 wpa_supplicant[92697]: Successfully initialized >> wpa_supplicant >> Nov 22 16:54:27 marvin2011 wpa_supplicant[92712]: Successfully initialized >> wpa_supplicant >> Nov 22 16:54:27 marvin2011 dhclient[92732]: dhclient already running, pid: >> 92731. >> Nov 22 16:54:27 marvin2011 dhclient[92732]: exiting. >> Nov 22 16:54:27 marvin2011 riggs: /etc/rc.d/dhclient: WARNING: failed to >> start dhclient >> Nov 22 16:54:27 marvin2011 wpa_supplicant[92714]: ioctl[SIOCS80211, >> op=103, val=0, arg_len=128]: Operation now in progress >> Nov 22 16:54:27 marvin2011 kernel: ath0: ath_reset_grablock: didn't finish >> after 10 iterations >> Nov 22 16:54:27 marvin2011 kernel: ath0: ath_reset_grablock: warning, >> recursive reset path! >> Nov 22 16:54:27 marvin2011 kernel: ath0: oath_reset: concurrent reset! >> Danger! >> Nov 22 16:54:27 marvin2011 wpa_supplicant[92714]: wlan0: Failed to >> initiate AP scan >> Nov 22 16:54:28 marvin2011 wpa_supplicant[92713]: ioctl[SIOCS80211, >> op=103, val=0, arg_len=128]: Operation now in progress >> Nov 22 16:54:28 marvin2011 wpa_supplicant[92713]: wlan0: Failed to >> initiate AP scan >> Nov 22 16:54:29 marvin2011 wpa_supplicant[92714]: ioctl[SIOCS80211, >> op=103, val=0, arg_len=128]: Operation now in progress >> Nov 22 16:54:29 marvin2011 wpa_supplicant[92714]: wlan0: Failed to >> initiate AP scan >> >> >> After this, the console gets flooded with the same error messages from >> ath(4) (grablog, recursive reset, danger) and wpa_supplicant over and >> over. >> >> Machine is 10.1-STABLE amd64, this is the dmesg output from the wlan >> adapter: >> ath0: mem 0xf7c00000-0xf7c0ffff irq 16 at device 0.0 on >> pci4 >> ath0: [HT] enabling HT modes >> ath0: [HT] enabling short-GI in 20MHz mode >> ath0: [HT] 1 stream STBC receive enabled >> ath0: [HT] 1 stream STBC transmit enabled >> ath0: [HT] 2 RX streams; 2 TX streams >> ath0: AR9287 mac 384.2 RF5133 phy 15.15 >> ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 >> >> So far, I have been unable to find a solution other than >> rebooting the machine, and I am looking for better options. >> >> The favourite option, obviously, is a patch that resolves it, but >> recommending an adapter that just works[tm] out of the box on 10.1 is >> acceptable as well, as long as >> - it is PCIe, and >> - currently, as of today, available at one of the usual dealers in >> Germany, e.g. amazon.de, mindfactory, etc. >> >> Of course I am happy to do whatever I can to debug the problem, but in >> lack of expert knowledge on wlan drivers, I'd need some help here. >> >> Best regards >> Riggs >> >> [1] statistically about once every three hours >> [2] roughly in 10% of the cases >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> > +1 > > My card is a AR9285 and I'm running HEAD (274171). > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"