Jan. 26th, 2011

yuri_kurenkov: (Default)
После апгрейда операционки на домашнем рутере стало маячить в dmesg:

ath0: stuck beacon; resetting (bmiss count 4
)

Вот, что Sam Leffler об этом думает:

"stuck beacon" means the ap tried to xmit a beacon frame but for various
reasons (where "various" is VERY large) it wasn't able to.  After N
consecutive attempts, 4 in this case) it gives up and resets the device
(which should bring it back to life in case it's stuck because of a
hardware bug).  Often this occurs because you are using a slow platform
and the time provided to prepare the beacon frame is insufficient to
push it to the hardware fast enough to meet the realtime requirements.  
This can be exacerbated by operating on a busy channel.  Unfortunately
you've provided very little info so I can't advise you.  I suggest you
search for this subject and look at the discussions that have occurred
for the last 5-6 years...


6.X нормально работала в этой конфигурации на 486-й мамке с PentiumOverdrive-83 процессором. А 8.Х 233MMX мало. Буду искать suggestions 5-6 лет выдержки...

Profile

yuri_kurenkov: (Default)
yuri_kurenkov

August 2011

S M T W T F S
 1 23 456
78910111213
14151617181920
21222324252627
28293031   

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Sep. 23rd, 2017 12:23 am
Powered by Dreamwidth Studios