[no subject]

To me, it seems a driver bug. Since I did not use wireless so often,
I cannot file a bug report because I do not have time to play with wi0.
If you have a dedicated use use with wi0, then you should file a bug report
once you can repoduce such problem by introducing some heavy traffic (not
hard at all for creating 11 Mbps network traffic from any host).

> > 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@xxxxxxxxxxx
> > > with "unsubscribe freebsd-hardware" in the body of the message

To Unsubscribe: send mail to majordomo@xxxxxxxxxxx
with "unsubscribe freebsd-hardware" in the body of the message