Kernel: ath0: stuck beacon; resetting (bmiss count 4)
-
is there any solution for the below error which has been a pain now from the past few weeks nanobsd snaps
kernel: ath0: stuck beacon; resetting (bmiss count 4)
older snaps, almost a month old or so used to work perfectly fine on the alix using a atheros wifi card but the recent bug fixes and updates give me a lot of these entries in my system log and my wireless connection has become very unstable.
-
is it just me with this?
-
If you go back to an older snap, does the problem go away? If not, it could just be coincidence. The ath issues are one reason I gave up over a year ago using pfsense for wireless access…
-
around a month and a half backs snap doesnt give the error.
any recommendation on a different brand of wifi card which works flawless?
-
Not really.
-
is it just me with this?
Nope, same problem here with a snapshot-iso (regular install) from a few days a go. Which is gonna be nanobsd eventually, right now I'm just trying to get the card to work.
Using a DWA-552.
edit: I'm not sure how, but I just got rid of the error ??? :)
-
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.
