rt73 disconnects and crashes usb

[Borahshadow]

Background
I have an averatec 2370 laptop which has the Ralink rt73 wireless chipset connected through some kind of internal usb bus.
with edgy and feisty I used ndiswrapper because the linux ralink drivers didn't work well for me.

I installed gutsy with tribe 5 and was very impressed. The wireless worked out of the box and the detected my screen correctly and after selecting the nvidia restricted driver suspend works on this laptop (I can't think of anything that doesn't as of gutsy).

I noticed some times my network will just quit working and won't reconnect even if i plug it into a cable nothing works and I have to reboot.

Here is the weirdest thing though if I just select reboot most of the time when it reboots it won't even see that a wireless card exists even if I reboot directly into feisty still nothing I usually have to turn off wait a few seconds and turn back on

sometimes if I run lsusb after it quits working lsusb just hangs and shows nothing

I have tried to reproduce this but I can't consistently reproduce it. Sometimes it happens quick, sometimes after 30 min, sometimes after 1hour, and sometimes I turn off my computer before it happens. I'm sure if I left in on long enough it would eventually happen.

I've waited this long to report it to see if I could reproduce it but I can't so I had to get it reported before the release

this really is a show stopper for me on what is other wise a great release for this laptop

[Borahshadow (codyregister)]

Oh I forgot to mention I didn't know whether this was a kerne bug or a network manager bug or what so I put don't know

[Borahshadow (codyregister)]

Sorry to post so many comments on my own bug but I just found the kernel bug policies and thought I'd attach those files and say I think this is the same bug as #133486

[Borahshadow (codyregister)]

ok here is dmesg and lspci after the network has failed
the closest thing I have to being able to reproduce it is
I open up firefox and go to the kubuntu website
I mount my file server that is using samba
I download a torrent of gutsy (I've done it with beta and RC) to the fileserver
open the torrent with ktorrent
select to save the torrent on my fileserver
and it starts
wait possibly browse the web

BTW I'm using kubuntu

[dragon76 (tfishwall)]

Everex ST5340T notebook
Kubuntu Gutsy Beta amd64 Generic kernel

I had this happen to me today and a few days ago. I have an Everex ST5340T laptop... it is identical to the Averatec 2370. The first time it happened I noticed that my usb trackball quit working... yes wireless was on at the time. Today when it happened it occured exactly at 4.00hrs uptime... maybe has something to do with it? I don't know if this is an issue with the wireless drivers or the usb. The only way I can get the wireless/usb to come back up is to turn the system off and cold boot. It seems as though this may be a usb issue.

[dragon76 (tfishwall)]

I have reproduced the problem.

[dragon76 (tfishwall)]

I have reproduced this again. This time uptime was 1hr 52min so that is unrelated. I confirmed that usb devices continued working after this occurs. wlan0 is not listed when doing an ifconfig. wlan0 is listed when doing an iwconfig but didn't show an essid, ip, etc. I also found a thread in the ubuntu forums reporting the same problem with an external usb wireless adapter using the same chipset.

Hope this helps

[Timothy Alexander (dragonfyre13)]

We have quite a loyal following of averatec 2370 users here: http://ubuntuforums.org/showthread.php?t=308152
Who would all be interested in this getting some attention. Just as an FYI. It's pretty much the only outstanding issue to this laptop working out of the box so far, and I'm looking for a workaround, or compile flag/change that will fix it.

[Borahshadow (codyregister)]

I just tried to reproduce it without any local network traffic (besides directly from my router to the internet) and it went for 4:50 and then I had to shutdown but I think it would keep going but no crash without local traffic (ie. to a server)

[dragon76 (tfishwall)]

Just a dmesg log from when it locked earlier today.

[Borahshadow (codyregister)]

Happened again at 26 min rebooted happened in 3min rebooted again and no wireless device these were without known local network traffic
sorry no new dmesg logs I forgot was in a hurry to get something done

[Uwe Hauck (bicyclist)]

my rt73usb usb wlan stick shows the same behaviour. It works sometime from 6 min to an hour.
but when i have a higher load on it it crashes and can't be restarted without reboot.

[Henrik Nilsen Omma (henrik)]

This will be retargeted towards the Hardy kernel once it is released. I've tagged this as "hardy-kernel-candidate" so that we make sure to retarget this report once the new release is out. However against the linux-source-2.6.22 package this is being marked as "Won't Fix" as it does not meet the criteria for a stable release update. To learn more about the stable release update process please refer to https://wiki.ubuntu.com/StableReleaseUpdates . Thanks!

[Leann Ogasawara (leannogasawara)]

Hardy Heron Alpha2 was recently released. It contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/hardy/alpha2 . Thanks!

[dragon76 (tfishwall)]

I have been running Hardy since alpha1 and am now using 2.6.24 kernel. I haven't had a chance in the last couple of weeks to try the wireless due to the holiday season, but will do so in the next couple of days and report back.

[Borahshadow (codyregister)]

I was going to start running hardy at alpha 1 but didn't get around to it until alpha 2. I installed it but have used it very minimally therefore due to the random nature of the bug I did not get it. I might be able to use hardy more full time at a later alpha but It just is a little too buggy at alpha 2 (however it is very good for alpha)

[Bakou (logan-fraser)]

I'm having pretty much the same prob with a WUA2340 d-link usb wifi thing (the gold rangebooster G one)
using hardy heron beta.. it seems that if you get a bad disconnect it's likely it'll hang lsusb and stop working (but seem to still be connected)
it also prevents rmmod ndiswrapper from doing anything, so you can't just do modprobe ndiswrapper to get it working as normal. Any workarounds for this?

root@blackbox:~# ndiswrapper -v
utils version: '1.9', utils version needed by module: '1.9'
module details:
filename: /lib/modules/2.6.24-12-generic/ubuntu/misc/ndiswrapper/ndiswrapper.ko
version: 1.52
vermagic: 2.6.24-12-generic SMP mod_unload 586

[Bakou (logan-fraser)]

here is some relevant log info taken from after i disconnect from a wireless network.. at the end i try to do a rmmod ndiswrapper and it completely freezes up till the mark at the end of the log

9:37:39 blackbox NetworkManager: <info> Activation (wlan0) failed for access point (linksys)
Mar 26 19:37:39 blackbox NetworkManager: <info> Activation (wlan0) failed.
Mar 26 19:37:39 blackbox NetworkManager: <info> Deactivating device wlan0.
Mar 26 19:37:39 blackbox NetworkManager: <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument
Mar 26 19:37:50 blackbox kernel: [ 3475.289382] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Mar 26 19:38:44 blackbox NetworkManager: <debug> [1206574724.023005] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'dlink'
Mar 26 19:38:44 blackbox NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / dlink
Mar 26 19:38:44 blackbox NetworkManager: <info> Deactivating device wlan0.
Mar 26 19:38:44 blackbox NetworkManager: <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument
Mar 26 19:38:44 blackbox NetworkManager: <info> Device wlan0 activation scheduled...
Mar 26 19:38:44 blackbox NetworkManager: <info> Activation (wlan0) started...
Mar 26 19:38:44 blackbox NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 26 19:38:44 blackbox NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Mar 26 19:38:44 blackbox NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Mar 26 19:38:44 blackbox NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Mar 26 19:38:44 blackbox NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Mar 26 19:38:44 blackbox NetworkManager: <info> Activation (wlan0/wireless): access point 'dlink' is unencrypted, no key needed.
Mar 26 19:38:45 blackbox NetworkManager: <info> retry to connect to global supplicant socket (try=1)
Mar 26 19:38:45 blackbox NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant0^I'
Mar 26 19:38:45 blackbox NetworkManager: <info> SUP: response was 'OK'
Mar 26 19:38:45 blackbox NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Mar 26 19:38:45 blackbox NetworkManager: <info> SUP: response was 'OK'
Mar 26 19:38:45 blackbox NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Mar 26 19:38:45 blackbox NetworkManager: <info> SUP: response was '0'
Mar 26 19:38:45 blackbox NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 646c696e6b'
Mar 26 19:38:45 blackbox NetworkManager: <info> SUP: response was 'OK'
Mar 26 19:38:45 blackbox NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Mar 26 19:38:45 blackbox NetworkManager: <info> SUP: response was 'OK'
Mar 26 19:38:45 blackbox NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Mar 26 19:38:45 blackbox NetworkManager: <info> SUP: response was 'OK'
Mar 26 19:38:45 blackbox NetworkManager: <in...