From owner-freebsd-wireless@FreeBSD.ORG Sat Nov 9 10:01:35 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 79AAF1D7 for ; Sat, 9 Nov 2013 10:01:35 +0000 (UTC) (envelope-from sven@hazejager.nl) Received: from mail-oa0-f44.google.com (mail-oa0-f44.google.com [209.85.219.44]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 40F5724E9 for ; Sat, 9 Nov 2013 10:01:35 +0000 (UTC) Received: by mail-oa0-f44.google.com with SMTP id i7so3553241oag.3 for ; Sat, 09 Nov 2013 02:01:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Nov/V88RrVDsSD1iJryrDjM59dPNAM8T0usFeeRUz0A=; b=YfyiMVVzOmXTlIPm8Fi0nwXjKHbHdtGAZA+1b9zIKI8CLFYPpNO4ifMOp2alCp62IO I4xUK+2SrxXBMbgeMTCmTgGzE71mz3DK0CIMA/5gg2E2kff1xD747N+P5HjfQy0fTmji C6xiyg8LXeD4FggvUoPzjaMew04aABNPe3bxLcE7ZXCMM9YR3ISghpQHvB4dXVYhKSqX UD/DsvCgYdn3Y23YQ0oGxoBWIvCuez9Kh8F0qJWQhmS1Qo1mlMZwZiH/xUPoS4sxKofs TfLz5AXaMdXbvMJJE64VhFPXcHb8tquyrUIxzLPkdttB+D5WOP6ZvWxEDzPj+OTkMeL0 YkKw== X-Gm-Message-State: ALoCoQkqJVTcoX8LDhmOKwfEpmHai+myWH4BSTTVEnBEN+DaNgTAxhtu2TqTfnJnnE9R8hNY9XsC MIME-Version: 1.0 X-Received: by 10.60.117.225 with SMTP id kh1mr15291379oeb.15.1383991294273; Sat, 09 Nov 2013 02:01:34 -0800 (PST) Received: by 10.182.18.9 with HTTP; Sat, 9 Nov 2013 02:01:34 -0800 (PST) X-Originating-IP: [212.123.177.47] In-Reply-To: References: Date: Sat, 9 Nov 2013 11:01:34 +0100 Message-ID: Subject: Re: AR9160 on HEAD - unstable? From: Sven Hazejager To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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:01:35 -0000 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? >