Re: [Madwifi-devel] [PATCH] Stuck Beacon Problem
Status: Beta
Brought to you by:
otaku
From: Emery G. <em...@vi...> - 2005-02-25 16:38:05
|
Hello Sam, I digged up this older email, after a thread discussing the=20 Stuck Beacon Problem made references to Jonas' patch. I read through the=20 threads, and here I see you mentioning that his patch is only a way of=20 covering up the problem and that no one has reported the information to=20 help you in diagnosing this problem. I was curious to know what information would you need? I've seen several=20 reports where people experience the problem including myself, but=20 obviously no real solution has come up. I'm no programmer, I'm just a=20 sys admin, but I'd definitely like to help. I myself have tried to debug the problem my own way. So far here's what=20 I found out and tried to do. The last time, I had my Host AP running madwifi was back in January. At=20 that time I had Redhat 9.0 with a 2.4 kernel running as a host AP with a=20 Dlink-G520 PCI card using the madwifi code from aug 5th, 2004. I had=20 successfully been using madwifi in Master mode since Jan 2004. My SBP (stuck beacon problem) started when I upgraded to fedora core 3,=20 which changed the kernel, to a 2.6 kernel with udev. At that point, I=20 tried compiling the latest cvs snapshot from jan 2005. The madwifi=20 modules loaded fine, but I could never get a steady connection with my=20 AP. My AP would slow down to look like it's frozen, until I would do a=20 "ifdown ath0". Looking at the logs and top, the load average, CPU=20 utlisation, memory, disk io, all seemed fine, but obviously, my system=20 had almost became unresponsive. I tried all sorts of kernel 2.6/madwifi version combinations and so far=20 none of them works. And since I'm using udev, I haven't gotten kernel=20 2.4 to work again, and therefore, I haven't gotten an older snapshot=20 (pre aug 6th) to work with kernel 2.6. One thing I did notice, before I upgraded to Fedora Core 3, around x-mas=20 time, I had tried updating the my madwifi driver, and I had noticed that=20 I couldn't use drivers from after aug 5th, 2004. And looking at through=20 the mailling list, I noticed that august 6th was when the WPA branch=20 merged into HEAD. Is it possible that the WPA branch quietly broke something? Or that the=20 solution to the problem lies in older cvs code? Sam Leffler wrote: > Jonas T=C3=A4rnstr=C3=B6m wrote: > >> This patch solves the "Stuck Beacon Problem" (as experienced by me)=20 >> by temporarily disabling the beacon interrupt (SWBA) and then turning=20 >> it back on followed by a reset of the card. It seems to work for me. > > > I appreciate your attacking this problem but your patch is not a=20 > solution; it simply covers up the real problem. I know of no hardware=20 > bug that requires you to add a watchdog timeout of this sort for=20 > madwifi. Instead I believe there is a software problem that is=20 > triggering the condition you see. Unfortunately no one has reported=20 > the information I've requested to help in diagnosis and I've never=20 > seen the problem. > > Sam > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now.=20 > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Madwifi-devel mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-devel |