Thread: [Madwifi-devel] Is this the Stuck Beacon problem?
Status: Beta
Brought to you by:
otaku
From: Aditya B. <ay...@an...> - 2010-08-12 16:06:35
|
Hi, While setting up MadWifi trunk as an AP, I notice the following lines appear repeatedly in the kernel logs. I used athdebug to print out these extra messages. Aug 12 15:45:12 nodew1 last message repeated 4 times Aug 12 15:45:12 nodew1 kernel: ath_intr: status 0x10000 Aug 12 15:45:12 nodew1 kernel: ath_intr: status 0x4009 Aug 12 15:45:13 nodew1 last message repeated 3 times Aug 12 15:45:13 nodew1 kernel: ath_intr: status 0x10000 Aug 12 15:45:13 nodew1 kernel: ath_intr: status 0x10000 Aug 12 15:45:13 nodew1 kernel: ath_intr: status 0x4009 Aug 12 15:45:13 nodew1 kernel: ath_intr: status 0x4009 When this happens, the STA for some reason cannot associate with the AP at all although Im sure Im setting all the necessary parameters like ESSID, channel number etc. Can someone please throw some light on this? Also independently of the above messages, I also get "Stuck Beacon message" as well. Has this problem been fixed or is it still unsolved? Thanks regards, Aditya Bhave |