From owner-freebsd-current@FreeBSD.ORG Fri Oct 3 17:55:23 2014 Return-Path: Delivered-To: freebsd-current@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 76BE9559 for ; Fri, 3 Oct 2014 17:55:23 +0000 (UTC) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (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 10220ED0 for ; Fri, 3 Oct 2014 17:55:22 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id hi2so2121909wib.3 for ; Fri, 03 Oct 2014 10:55:21 -0700 (PDT) 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=T2YzhSYq4bLqkUf4gtFxtT7VO9x7Ite5TIUEr1oz10g=; b=l5Bv388rVR+Ik+lwJ0umR9Zw7dGhb9amaI5TjZjhT38NtM3/JHJo0ZfdEbC3EKI+Zd na5igmo3glmu/5s/HiSjbj+GEPScvqX0T5GZxs8j5EPAIBcfdvoKB2gTPjfbpTWHixZt +NdicAxpU3tspbhaqV0dCozkd8xqPQzETO/RjekLVErTe+vMIcK0tDfp1mpM/T9AOWrM MoH0nEb0u4o+srw0369WP/GyBVI2xPXeCW81EvxVJD92RRVIxlKX1TnB4v7jzz9tUZYQ LL8PMol1R/Oz2qfgxP9OeLrgN1aPLnUC+QiI6TbRT7c/VvIhhDVPlNTBtvvYxMqCtr1c 5oNQ== MIME-Version: 1.0 X-Received: by 10.180.74.203 with SMTP id w11mr179600wiv.26.1412358921306; Fri, 03 Oct 2014 10:55:21 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.106.136 with HTTP; Fri, 3 Oct 2014 10:55:21 -0700 (PDT) In-Reply-To: <20141003153306.0e0db45c.ohartman@zedat.fu-berlin.de> References: <20141003145403.704e85be.ohartman@zedat.fu-berlin.de> <20141003151554.19434wd2pn8bwlu2@webmail.uu.se> <20141003153306.0e0db45c.ohartman@zedat.fu-berlin.de> Date: Fri, 3 Oct 2014 10:55:21 -0700 X-Google-Sender-Auth: M5MAVzEmS0Szm9JYsVd_ZzYK7R8 Message-ID: Subject: Re: CURRENT: ath0: stuck beacon; resetting (bmiss count 4) From: Adrian Chadd To: "O. Hartmann" Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD CURRENT , Erik Trulsson X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Oct 2014 17:55:23 -0000 I think you're going to be .. unhappy with what Intel's firmware is like as an AP. I still have to chase down why the AR9287 stalls and do a full chip reset when it goes RX deaf. I'm just chasing down other things at the moment. -a On 3 October 2014 06:33, O. Hartmann wrote: > Am Fri, 03 Oct 2014 15:15:54 +0200 > Erik Trulsson schrieb: > >> Quoting "O. Hartmann" : >> >> > Since a couple of days I get this weird console-and-log-spamming message: >> > >> > ath0: stuck beacon; resetting (bmiss count 4) >> > >> > The machine in question is running the most recent CURRENT right now: >> > >> > FreeBSD 11.0-CURRENT #2 r272471: Fri Oct 3 13:03:58 CEST 2014 amd64 >> > >> > and the box acts as a gateway with WiFi access point via hostapd and >> > this WiFi hardware: >> > >> > [...] >> > ath0: mem 0xf7e00000-0xf7e0ffff irq 16 at device 0.0 on pci1 >> > 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: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 >> > >> > What is this and how can I get rid of it? >> >> It means that you have run into a well-known and long lasting hardware >> bug in Atheros Wifi chipsets, where they sometimes get stuck and stops >> sending out beacons. >> You get that message when the device driver detects that this has >> happened and resets the chip to get things going again. >> >> There is, AFAIK, no way of making sure the problem cannot happen, but >> you might be able to reduce the frequency of it happening by reducing >> the amount of interference you receive from other wireless devices. > > Ah, I understand, so nothing to worry about. The WiFi NIC is a cheap TP Link facility. > Hopefully, FreeBSD will have support for Intel's Dual Band 7260-chipset this decade, so > the problem will be gone anyway (except Intel put also nice hardware bugs into their > silica ...). > > > oh