Kernel: ath0: stuck beacon; resetting (bmiss count 4)
-
around a month and a half backs snap doesnt give the error.
Then it's voodoo since nothing in the ath driver has changed since we went to FreeBSD 8.1 somewhere around a year ago. :) Nothing in the config really has changed either as there's only one way to set things up, and that's not a config-related condition.
There's a lot of info on this issue in general on FreeBSD lists if you search on it.
My ath cards all work fine, only APs I use, so not sure what to suggest.
-
is it just me with this?
Same thing here with current i386 snapshots…. (this didn't happen the last time i tested v2 about a month ago...)
"kernel: ath0: stuck beacon; resetting (bmiss count 4)"
-
It may be possible this is related to one of our mbuf patches that was reverted and deferred to a future version, I really doubt it as it would likely be universal and cause panics but it's possible, try today's snapshot or newer.
-
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
-
i was surprised to see replies to this thread coz i just stopped getting mails regarding new posts from the forum for some reason.
-
i was surprised to see replies to this thread coz i just stopped getting mails regarding new posts from the forum for some reason.
Looks like the mail queue is backlogged. I'm getting the notifications, they're just extremely slow.
-
For me changing wifi channel worked a few times already (as I get this error from time to time).
-
i was surprised to see replies to this thread coz i just stopped getting mails regarding new posts from the forum for some reason.
Hmm, weird :P
Here it seemed like I just had to choose the right settings, although I haven't got a clue which setting it might have been that solved it…
(About the issue you created this topic for, not the email problem ;) ) -
i was planning to post a bounty to start with $100 and mayb more ppl can contribute to it to make wireless hotspot more robust and alos get rid of these stuck beacon if any1 was willing to complete it.
-
Which wifi card are you using btw?
-
Compex WLM54G atheros 5414 chipset but it reports as this:
dev.ath.0.%desc: Atheros 5413 -
Hmm…
Well, maybe this bug is fixed in a newer version of the ath(4) driver.
I've been told someone is working on it and also adding N support.Only I don't know where to get the most recent version of this driver and how to update the one that currently comes with pfSense.
-
same problem here:
kernel: ath0: stuck beacon; resetting (bmiss count 4)
hardware is:
kernel: ath0: <atheros 5212="">mem 0xfd8f0000-0xfd8fffff irq 17 at device 1.0 on pci5
kernel: ath0: [ITHREAD]
kernel: ath0: AR2413 mac 7.9 RF2413 phy 4.5Version 2.0-BETA5 (i386)
built on Thu Feb 24 17:17:04 EST 2011</atheros> -
probably only the devs would know i guess on how and where to get the updated drivers, i would be very much interested in it.
-
I asked on the FreeBSD forum, got this:
svn co http://svn.freebsd.org/base/head/sys/dev/athBut does pfSense have svn? Haven't looked at that yet…
- might not work if there where changes in the kernel that are needed by the updated driver.
-
Installed svn using```
pkg_add -r subversionThen I used scp to copy over these from my FreeBSD virtual pc because svn needed them. /usr/lib/libgssapi.so.10 /usr/lib/libheimntlm.so.10 /usr/lib/libkrb5.so.10 /usr/lib/libhx509.so.10 /usr/lib/libasn1.so.10 /usr/lib/libroken.so.10 The svn command downloaded all files from that link. Now have to figure out what to do next. -
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…)
-
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. -
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: associatedI 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. -
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.
