Date: Sun, 26 May 2002 23:12:53 -0300 (BRT) From: Paulo Fragoso <paulo@nlink.com.br> To: "Jin Guojun [DSD]" <j_guojun@lbl.gov> Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Wireless Problems (wi) Message-ID: <20020526225503.W84607-100000@mirage.nlink.com.br> In-Reply-To: <3CEED543.75C213B4@lbl.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Fri, 24 May 2002, Jin Guojun [DSD] wrote: > I do not think this is related to 4.5 or later. I had similar problem on > 4.3-RELEASE. > I believe that this is trigged by losing the contact to the wireless server. > Somehow, > the dirver dies and left some recovering status in configuration register on the > card > (just guessing). > When wi driver sees this status after reboot or power cycle, it will not reset > the card regardless power on or reboot. This may leave the card in some unknown > status. > But there is a very important fact: when we remove the card from its adapter and after a little time we reintroduce again (there is one power cylce here) it can't work, only will work after a reboot, without a power cycle. We think could be some situation which the wi driver can't answer correctly. In our routers there ins't other OS and it is very difficult to test because this happen after some hours working fine. At weekend this problem rarely happen when our traffic is low. > MS Windows does not try to look such status, and just re-initializes the card. > So, > if BSD cannot recover the wi0, boot to window, then boot back to BSD, and wi0 > will work again. If this is the case, then above guessing will be true. > > -Jin > > Paulo Fragoso wrote: > > > Hi, > > > > Have you ever found a problem with Orinoco and Avaya wireless card like > > this: > > > > /kernel: wi0: xmit failed > > /kernel: wi0: watchdog timeout > > /kernel: wi0: init failed > > /kernel: wi0: failed to allocate 1594 bytes on NIC > > /kernel: wi0: tx buffer allocation failed > > /kernel: wi0: failed to allocate 1594 bytes on NIC > > /kernel: wi0: mgmt. buffer allocation failed > > /kernel: wi0: timeout in wi_seek to 0/0; last status 4000 > > /kernel: wi0: timeout in wi_seek to 0/44; last status 4044 > > > > It's happening after 1 or 2 hours working normally and only after reboot > > (without turn off, like M$ Windows) this card return to work. > > > > This is very strange, we have a lot of remote router with FreeBSD release > > older than 4.5 and it's happening only with 4.5-RELEASE, 4.5-RELESE-pX an > > 4.6RC. Is it a coincidence or there is a problem with wi code? > > > > How those cards are locking and all CPU speed down when it is happing? > > > > Whe really need some help. Can anyone help us? > > > > Many thanks, > > Paulo Fragoso. > > > > -- > > __O > > _-\<,_ Why drive when you can bike? > > (_)/ (_) > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hardware" in the body of the message > > -- > ------------ Jin Guojun ----------- v --- j_guojun@lbl.gov --- > Distributed Systems Department http://www.itg.lbl.gov/~jin > M/S 50B-2239 Ph#:(510) 486-7531 Fax: 486-6363 > Lawrence Berkeley National Laboratory, Berkeley, CA 94720 > > > -- __O _-\<,_ Why drive when you can bike? (_)/ (_) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020526225503.W84607-100000>