From owner-freebsd-wireless@FreeBSD.ORG Sat Nov 9 10:11:24 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CB302248 for ; Sat, 9 Nov 2013 10:11:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x22c.google.com (mail-qa0-x22c.google.com [IPv6:2607:f8b0:400d:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8B45D253C for ; Sat, 9 Nov 2013 10:11:24 +0000 (UTC) Received: by mail-qa0-f44.google.com with SMTP id f11so401528qae.17 for ; Sat, 09 Nov 2013 02:11:23 -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=VRUjoyd2gSBAgXgMWju47Ulrt1qQ/TMGm9wUeO0KD60=; b=hk3HGjRs0eEHq0MqE08z93clav73cAhxklkajUwOs8kw2Lo5SwaV0zEH9kb3SLGTAZ l2F+0SHR134GTcJXku71oloU4HGMUpJ5lBHAzO+anqB1xJE0jMU2hIdcpRUo+8H4c75W D7gJvkEfzOYmEFpasgHRiW3cgJZm48CAKX2rNqGrat8+LC7idkOoZ4fccfnQZOReqehp 9V6oXeOyZdsT2bFs+c8yzNAKugbHsitp9G0534OYeklVKELow/kuKWaw9Jv1Zww2VbjY 7YQTpnqOsQnF+p9OS9rW4sMAdWN2MMEaLp3cWFf3qxpj9fXd7OodZMnF5BOPMZNN06lo Qrtg== MIME-Version: 1.0 X-Received: by 10.224.36.201 with SMTP id u9mr30977162qad.76.1383991883817; Sat, 09 Nov 2013 02:11:23 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Sat, 9 Nov 2013 02:11:23 -0800 (PST) In-Reply-To: References: Date: Sat, 9 Nov 2013 02:11:23 -0800 X-Google-Sender-Auth: e0j7ZR68R2X-hK7OGgnsnhIVi3Y Message-ID: Subject: Re: AR9160 on HEAD - unstable? From: Adrian Chadd To: Sven Hazejager Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Nov 2013 10:11:24 -0000 Hi! Well, I'd start by checking to see what is being transmitted and received. * is it transmitting beacons? * is it transmitting anything data-like? eg, is it transmitting broadcast/multicast frames? * can it receive frames? You can use athstats to see what's going on. wlandebug -i ath(0,1,2..) +rate is a cheap way to see if its transmitting data frames reliably. -adrian On 9 November 2013 02:01, Sven Hazejager wrote: > OK will ignore the stuck beacon stuff :-). Warm reboot is indeed typing > "reboot". That did not resolve this morning's matter. Actually, after I > unplugged the ALIX for a couple of seconds, it came back up... same problem! > Second time, I unplugged it for 30 seconds... problem solved...! Hardware > issue with my AR9160? I've never had it this bad before. > > I did compile in your debug stuff + ath tools: what should I do next time > this happens to get more information? > > On 9 November 2013 08:49, Adrian Chadd wrote: >> >> the stuck beacon stuff is likely just the MAC getting angry at the >> power save aggressiveness that the iphone/ipad does. But it itself >> shouldn't lock things up. >> >> When you say you did a warm reboot, is that a 'reboot' where you typed >> reboot? is there a physical reset button on the ALIX you can short? > > >