Re: D-Link DWL-120 / Belkin F5D5060 tx timeout problem

Hi Sander,

On Tue, 20 Jul 2004, Sander Zegers wrote:

> I added the patch and a ping -f no resulted in a hang up of the console
> - still access trough ssh. The drivers were removed and I was unable to
> remodprobe them.  The AP is a D-link DWL 6000AP. There is an other
> client connected to it, so I think the AP shouldn't be a problem, the
> NIC's are working correctly with the Windows drivers. The new logfiles
> you requested are attached, if they are not ok or not detailed enough,
> I'll make new ones.


> Jul 20 11:46:23 laptop modprobe: FATAL: Error inserting usbvnetr
> (/lib/modules/2.6.7/kernel/drivers/usb/usbvnetr.ko): Unknown
> symbol in module, or unknown parameter (see dmesg)

You've got both Sourceforge and Berlios driver installed - please remove
the SF one (althrough it shouldn't cause your error).


> /root/at76c503a/at76c503.c: wlan0: connected to BSSID 00:05:5d:6d:37:d9
> NETDEV WATCHDOG: wlan0: transmit timed out
> /root/at76c503a/at76c503.c: wlan0: tx timeout.
> NETDEV WATCHDOG: wlan0: transmit timed out
> /root/at76c503a/at76c503.c: wlan0: tx timeout.
> NETDEV WATCHDOG: wlan0: transmit timed out
> /root/at76c503a/at76c503.c: wlan0: tx timeout.
> NETDEV WATCHDOG: wlan0: transmit timed out
> /root/at76c503a/at76c503.c: wlan0: tx timeout.
> /root/at76c503a/at76c503.c: wlan0: timeout, state 7
> /root/at76c503a/at76c503.c: wlan0: lost beacon bssid 00:05:5d:6d:37:d9

So, the old error
> /root/at76c503a/at76c503.c: wlan0: error in tx submit urb: -22
didn't show up anymore?

What's the time between
> /root/at76c503a/at76c503.c: wlan0: connected to BSSID 00:05:5d:6d:37:d9
and
> NETDEV WATCHDOG: wlan0: transmit timed out

(change your /etc/syslogd.conf to get _all_ messages into
/var/log/messages).

Does the "ping -f" gets some packets through or does the console lock
immediately?

The above looks more and more like an USB problem, especially with this
line at the end:
> usb 1-1: control timeout on ep0out

Please describe your USB setup: which hostcontroller (lspci), any hubs,
how long is the cable to the WLAN device, any other device on the same
root hub...

Any try without the Sourceforge driver.

/Jörg