Project

General

Profile

Actions
Copy link

Bug #4030

closed

AR9227 cards cause kernic panic when switched to n-mode

Added by Alex Restifo over 10 years ago. Updated almost 10 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
Wireless
Target version:
-
Start date:
11/20/2014
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

I have a PCI AR9227 card that refuses to change to n-mode. After it boots back up, it appears to be in n-mode and works for about an hour, which is when I start seeing multiple "ath0: stuck beacon! (bmiss count 8)" messages. Afterwards, the AR9227 resets (usually doesn't affect other hardware, but it sometimes will affect the whole machine). This shuts down the wifi permanently on the machine, even though it is "resetting".

Actions
Copy link
 #1

Updated by Chris Buechler over 10 years ago

did you submit a crash report? If so, what are the first two octets of your IP? (that's enough for me to find it, not enough for anyone else to know what your IP is)

Actions
Copy link
 #2

Updated by Alex Restifo over 10 years ago

108.28 (Sorry for the [super] late reply)

Actions
Copy link
 #3

Updated by Chris Buechler over 10 years ago

not seeing a crash report from anything on those first two octets. One in the same big Verizon block but well off from that, was about 36 hours after this was submitted, and looks much diff from what I'd expect here (contains nothing about wireless).

How is your wireless card configured?

Actions
Copy link
 #4

Updated by Zsolt SZASZ about 10 years ago

I have the same wireless chipset in my system, too. My pfsense was upgraded to the latest version 2.2.2 and the stability issues are still present. One of the suggestions from Adrian Chadd would be to add the variable: sysctl dev.ath.0.hal.force_full_reset=1. It must be added in System-> Advanced-> System Tunables to last this setting even after a system reboot. I can say after that the stability of the wireless network become much better (you will still receive a few "stuck beacons" but not that much like before).

So I suggest to upgrade pfsense to the latest 2.2.2 starting now, and add the variable to the system!
Please someone remind to Adrian to consider this fix in freebsd-head.

Actions
Copy link
 #5

Updated by Chris Buechler almost 10 years ago

  • Status changed from New to Resolved
  • Affected Version deleted (2.2)

The updated wireless and Atheros driver in 2.2.2 and newer addresses the crash here. The force_full_reset Zsolt noted can fix other issues for some.

Actions
Copy link

Also available in: Atom PDF