Kernel: ath0: stuck beacon; resetting (bmiss count 4)

jimp

You can't compile on the firewall - having that code on the firewall doesn't do you any good. You would need to download that to a local FreeBSD installation or VM and compile there, and move the resulting files over. (But even then it may not do what you expect…)

bartgrefte

Ow okay.

Downloaded sourcefiles in virtual pc with FreeBSD 8.2, now trying to compile it, but no luck so far.
Whole bunch of errors when running make on each of the *.c files.

bartgrefte

I did an upgrade to RC1 this morning, broke my wifi. So did a clean install, started from scratch, running into the error the reason this topic was made for. Then after changing the channel couple of times + reboot I managed to get rid of it.

But now a whole different problem, that I thought a clean install would solve, guess not:

Mar 1 15:06:35 hostapd: ath0_wlan0: STA 00:27:10:ce:03:6c IEEE 802.11: deassociated 
Mar 1 15:06:35 hostapd: ath0_wlan0: STA 00:27:10:ce:03:6c IEEE 802.11: deauthenticated due to local deauth request 
Mar 1 15:06:32 hostapd: ath0_wlan0: STA 00:27:10:ce:03:6c IEEE 802.11: associated 
Mar 1 15:06:32 hostapd: ath0_wlan0: STA 00:27:10:ce:03:6c IEEE 802.11: deassociated 
Mar 1 15:06:32 hostapd: ath0_wlan0: STA 00:27:10:ce:03:6c IEEE 802.11: deauthenticated due to local deauth request 
Mar 1 15:06:31 hostapd: ath0_wlan0: STA 00:27:10:ce:03:6c WPA: received EAPOL-Key 2/4 Pairwise with unexpected replay counter 
Mar 1 15:06:31 hostapd: ath0_wlan0: STA 00:27:10:ce:03:6c IEEE 802.11: associated

I think something changed between beta 5 feb.4 snapshot and RC1, since this problem showed up after the upgrade, but what?
Also the upgrade did not fix the "stuck beacon"-bug, so that is still in there as well. Although it is no longer a pain in the a** at the moment.

cmb

@bartgrefte:

I think something changed between beta 5 feb.4 snapshot and RC1, since this problem showed up after the upgrade, but what?

nothing wireless related has changed in months. These driver issues come and go for some people for unknown reasons. We don't write, maintain or have any control of wireless drivers which is where these issues are, these things need to be reported upstream.

bartgrefte

Hmm…

Well, I managed to compile a newer version of the driver using the source, but now I need to figure out how to get pfSense to (try to) use that one instead of the one already in the kernel. Google explained how to disable and load drivers, but not how to "override" one already in the kernel without having to rebuild that.

bartgrefte

According to someone on the FreeBSD forum the only way to use the new driver is to completely rebuild/recompile the kernel.

Already found this: http://devwiki.pfsense.org/DevelopersBootStrapAndDevIso , but what if I only want the kernel? Any howto's on that?
Someone already asked that but did not get response: http://forum.pfsense.org/index.php/topic,26188.msg163743.html#msg163743

bartgrefte

I modified the make.conf to exclude the driver and created a custom pfSense….. The driver is still in there. >:(

jimp

http://lists.freebsd.org/pipermail/freebsd-stable/2011-March/061772.html

Mostly the stuck beacon appears to be interference. Try a different channel. Driver isn't going to help that.

bartgrefte

Already tried that, all 13 channels are busy…
That's why I would like to try an updated driver, hopefully it is a bit more stable than the one FreeBSD 8.1/pfSense 2 has got.

Or at least the option to try it and help testing it for Adrian (who is working on it), don't have that option now because there does not seem to be a way to remove the driver already in the kernel.

jimp

Not much in that message implies that the stuck beacon message will really improve with a different driver. He talks about some features that haven't been ported yet, and that some chips may not improve at all (or may get worse) with a new driver.

That said, if you load a driver's .ko file from /boot/loader.conf.local it can override the in-kernel version of the driver.

But if you want to try the debug kernel options mentioned in that message, you'll have to run off a whole custom kernel (may as well make a custom iso/update) and the builder works fine for me. I just setup another builder today and had no trouble getting through the ports and such.

wallabybob

Other people have reported in these forums that they have successfully used a driver in a loadable module to override the driver in the kernel. I haven't tried it myself so can't verify this from personal experience.

If you care to follow this path you will need to load the module form of the driver at boot time by adding a line like if_ath_load="YES" to /boot/loader.conf.local

I would also suggest you add a printf() call to the attach function in your driver (for example, printf("bartgrefte's ath attach function\n");) so you can be sure the system is using your driver and not the driver in the kernel.

bartgrefte

Hmm, okay.
Read about that, did not new that method could override a driver integrated in the kernel

Well, if the MODULES_OVERRIDE option jimp mentioned in a different topic does not work, I'll try that :)

bartgrefte

@wallabybob:

Other people have reported in these forums that they have successfully used a driver in a loadable module to override the driver in the kernel. I haven't tried it myself so can't verify this from personal experience.
**If you care to follow this path you will need to load the module form of the driver at boot time by adding a line like if_ath_load="YES" to /boot/loader.conf.local

I would also suggest you add a printf() call to the attach function in your driver (for example, printf("bartgrefte's ath attach function\n");) so you can be sure the system is using your driver and not the driver in the kernel.**

Tried that, can't tell if it worked. Not seeing that sentence pop up anywhere in dmesg.
Note: loader.conf.local did not exist, so I created one with Vi.

offtopic: Why does pfSense not have Nano instead of Vi? Nano is easier to use.

jimp

vi is better. ;D

ee is there if you need an easy editor.

bartgrefte

Matter of personal opinion I guess :P
I kinda prefer Nano, because with that you don't have to look up the commands, they are on the screen ;D

jimp

ee is the same way, it wastes a lot of screen area on listing commands and menus and such. Me, I'd rather be editing than looking at that. :-)

johbra

I just want to share my experience with this problem. I was running PfSense 1.2.3 with a ath card and no problems. When i upgraded to "2.0-RC1 (i386) built on Sat Feb 26 15:30:26 EST 2011" wireless stopped working (with the same error).

The only setting i changed to get this working was channel (wireless channel).

bartgrefte

Changing the channel has worked for some people, but all channels are busy here and I have tried all of them without luck.

Right know I'm considering switching to a Linux based alternative for pfSense, hoping that the Linux equivalent of the Atheros driver does not contain this bug and because that one does (as far as I know) offer support for the N standard.

fthomasr

I have the same issue: kernel: ath0: stuck beacon; resetting (bmiss count 4)

Alix 6E1 board, .99H BIOS, Mikrotik r52h Atheros 5414 chipset card.

On startup mine also reports it as this:
ath0: <atheros 5413="">mem 0xe0080000-0xe008ffff irq 9 at device 12.0 on pci0
ath0: [ITHREAD]
ath0: AR5413 mac 10.5 RF5413 phy 6.1

Which I thought might be significant.

I'm trying the tunables suggested below as we speak to see if it gets better:

@UrbanSk:

Hi!
I have had this for a while also.

Try setting hw.ath.bstuck to 8 in system/advanced/system tunables (add new row).

I also added hw.ath.longcal and value 30.

For me WiFi now works better.

/UrbanSk</atheros>

bartgrefte

Tunables? That setting is not present here, or is only present in pfSense 2?

And to quote myself:
@bartgrefte:

Changing the channel has worked for some people, but all channels are busy here and I have tried all of them without luck.

Right know I'm considering switching to a Linux based alternative for pfSense, hoping that the Linux equivalent of the Atheros driver does not contain this bug and because that one does (as far as I know) offer support for the N standard.

I haven't been able to find a decent alternative for pfSense….