[BAWUG] Error -110 Reading and Writing

[Rob Thorne]

I have a DLink 520 hooked up to a Linux box I'm using as a wireless gateway. It works reasonably well, but occasionally gets into a bad state:

Oct 17 16:47:07 netz NoCat[23692]: Capturing 10.0.1.200 for
http://my.yahoo.com/
Oct 17 16:47:12 netz kernel: eth1: error -110 reading Rx descriptor.
Frame dropped.
Oct 17 16:47:12 netz kernel: eth1: Error -110 writing packet header
to BAP
Oct 17 16:47:12 netz kernel: eth1: Error -110 writing Tx descriptor
to BAP
Oct 17 16:47:43 netz last message repeated 29293 times
Oct 17 16:48:44 netz last message repeated 57838 times
Oct 17 16:49:45 netz last message repeated 57824 times

Once it gets into this state, I have to take the wireless interface down completely, and do a "rmmod orinoco_pci" before restarting the interface.

This makes this sort of gateway fine for using at home, but useless anywhere that I couldn't manually kick the gateway over every so often.

Does anyone know:

1. Why the f&*^% this happens?
2. Is this specific to the DLink cards, or is this something other
people have seen?
3. Can it be prevented?
4. If it can't be prevented, can this bad state at least be detected,
so I can at least write a cron job that will reinitialize the
interface when it goes south?

This seems to happen most when a connection is heavily loaded, although I couldn't say if this is the cause.

Any ideas anyone has would be much appreciated.

Much thanks,
Rob
Santa Cruz

--
Rob Thorne
Chief Technical Officer
Torenware Networks


--
general wireless list, a bawug thing <http://www.bawug.org/>
[un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless