From owner-freebsd-amd64@freebsd.org Tue Dec 6 04:59:36 2016 Return-Path: Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C0FCC69F56 for ; Tue, 6 Dec 2016 04:59:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8BC6361D for ; Tue, 6 Dec 2016 04:59:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uB64xaxX024998 for ; Tue, 6 Dec 2016 04:59:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 215079] [ath] [panic] (Qualcomm AR9227) stuck beacon after running a while Date: Tue, 06 Dec 2016 04:59:36 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: c.kworr@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2016 04:59:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215079 --- Comment #2 from c.kworr@gmail.com --- Added to /etc/sysctl.conf and rebooted (just in case). Not that much differ= ence yet. Dec 6 06:54:45 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:54:50 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:55:02 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:55:07 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:55:09 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:55:17 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:55:18 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:55:45 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:55:47 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:55:48 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:56:09 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:56:13 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:56:17 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:56:25 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) --=20 You are receiving this mail because: You are on the CC list for the bug.=