Date: Fri, 3 Oct 2014 15:33:06 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Erik Trulsson <Erik.Trulsson.1013@student.uu.se> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: CURRENT: ath0: stuck beacon; resetting (bmiss count 4) Message-ID: <20141003153306.0e0db45c.ohartman@zedat.fu-berlin.de> In-Reply-To: <20141003151554.19434wd2pn8bwlu2@webmail.uu.se> References: <20141003145403.704e85be.ohartman@zedat.fu-berlin.de> <20141003151554.19434wd2pn8bwlu2@webmail.uu.se>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/zR1ms=sFjvL6I5B9fVQ+nh+ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Fri, 03 Oct 2014 15:15:54 +0200 Erik Trulsson <Erik.Trulsson.1013@student.uu.se> schrieb: > Quoting "O. Hartmann" <ohartman@zedat.fu-berlin.de>: >=20 > > Since a couple of days I get this weird console-and-log-spamming messag= e: > > > > 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 =20 > > this WiFi hardware: > > > > [...] > > ath0: <Atheros 9287> 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? >=20 > It means that you have run into a well-known and long lasting hardware =20 > bug in Atheros Wifi chipsets, where they sometimes get stuck and stops =20 > sending out beacons. > You get that message when the device driver detects that this has =20 > happened and resets the chip to get things going again. >=20 > There is, AFAIK, no way of making sure the problem cannot happen, but =20 > you might be able to reduce the frequency of it happening by reducing =20 > 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 Lin= k facility. Hopefully, FreeBSD will have support for Intel's Dual Band 7260-chipset thi= s decade, so the problem will be gone anyway (except Intel put also nice hardware bugs i= nto their silica ...). oh --Sig_/zR1ms=sFjvL6I5B9fVQ+nh+ Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJULqWSAAoJEOgBcD7A/5N8gm8IALFT3XCAvVnIX4/npOFuvZY4 LY1aHOxyAtQtGQEckmqheOUyD8X1U2nirFq3HSOEx0oqw8nXjkocogP8sWIqVB8j DxVe/B6GRO67TjLOPeZbVAbO583oMzaThBbJleAMRudHqF9zCDf+HZ9YRxIeDhEd chfCoNM1KRDDnGiOp1+xJxcawPp75I+ymGMqTNUk+qmv4bzFwiD3gRjZ9/n2gHMG g9hmpl4Z7PLPrWDIjIKYb/M0lXON+ON2Vblk8/NTTr60LvE+dNhSl3mB8ckYpPgE fAqvyUxg9wE9ddTSRrYLcjar0m5eFwP3lxm1zHHOgBeg0i+XpDZnM1I/jkn7xPI= =CaF1 -----END PGP SIGNATURE----- --Sig_/zR1ms=sFjvL6I5B9fVQ+nh+--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141003153306.0e0db45c.ohartman>