Ubuntu
rt73 package

rt73usb intrepid 8.10 beta -- wireless connection periodically lost; must restart driver

Bug #283759 reported by joshyg6
This bug report is a duplicate of:  Bug #258985: Ralink rt73 hangs and requires reboot. Edit Remove
38
This bug affects 4 people
Affects Status Importance Assigned to Milestone
rt2x00 Project
Invalid
Undecided
Unassigned
Fedora
Invalid
Unknown
Mandriva
Invalid
Unknown
rt73 (Ubuntu)
Invalid
Undecided
Unassigned
Nominated for Intrepid by Nicolas Boucher
Nominated for Jaunty by Peter Hoeg

Bug Description

I may have something.. So I blacklisted the recompiled/newly installed legacy rt73 drivers, and i went back to using the rt73usb included initially with intrepid. i was using the Internet as normal, and then it crapped out, and these are the tail logs..

Quote:
Oct 15 07:53:19 jupiter2 NetworkManager: <debug> [1224071599.522971] periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:3D:39:10:96 (LODGER)
Oct 15 07:55:13 jupiter2 NetworkManager: <debug> [1224071713.601943] periodic_update(): Roamed from BSSID 00:0F:3D:39:10:96 (LODGER) to (none) ((none))
Oct 15 07:55:19 jupiter2 NetworkManager: <debug> [1224071719.605557] periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:3D:39:10:96 (LODGER)

****** Connection seemed to crap out around this point!!!********

Oct 15 08:00:01 jupiter2 /USR/SBIN/CRON[9353]: (root) CMD ([ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
Oct 15 08:03:26 jupiter2 kernel: [ 4474.961767] usb 8-5.2: reset high speed USB device using ehci_hcd and address 4
Oct 15 08:10:01 jupiter2 /USR/SBIN/CRON[9577]: (root) CMD ([ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
Oct 15 08:17:01 jupiter2 /USR/SBIN/CRON[9828]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Oct 15 08:20:01 jupiter2 /USR/SBIN/CRON[10010]: (root) CMD ([ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
Oct 15 08:22:12 jupiter2 kernel: [ 5601.528260] phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2.
Oct 15 08:22:12 jupiter2 kernel: [ 5601.528262] Please file bug report to http://rt2x00.serialmonkey.com.
Oct 15 08:22:12 jupiter2 kernel: [ 5601.528340] phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2.
Oct 15 08:22:12 jupiter2 kernel: [ 5601.528341] Please file bug report to http://rt2x00.serialmonkey.com.

****** At this point here, I sudo ifconfig wlan0 down. Then I sudo modprobe -r rt73usb. Then I sudo modprobe rt73usb. Then I sudo ifconfig wlan0 up. Then I reselect the proper network from the NetworkManager drop down, and then it connects and I have internet again! ****************

Oct 15 08:28:48 jupiter2 avahi-daemon[5359]: Interface wlan0.IPv4 no longer relevant for mDNS.
Oct 15 08:28:48 jupiter2 avahi-daemon[5359]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.100.
Oct 15 08:28:48 jupiter2 dhclient: receive_packet failed on wlan0: Network is down
Oct 15 08:28:48 jupiter2 avahi-daemon[5359]: Withdrawing address record for 192.168.0.100 on wlan0.
Oct 15 08:28:51 jupiter2 NetworkManager: <debug> [1224073731.029387] periodic_update(): Roamed from BSSID 00:0F:3D:39:10:96 (LODGER) to (none) ((none))
Oct 15 08:28:55 jupiter2 kernel: [ 6003.929519] usbcore: deregistering interface driver rt73usb
Oct 15 08:28:55 jupiter2 nm-system-settings: SCPlugin-Ifupdown: devices removed (udi: /org/freedesktop/Hal/devices/net_00_16_44_7c_a0_e2_0)
Oct 15 08:28:55 jupiter2 NetworkManager: <info> (wlan0): now unmanaged
Oct 15 08:28:55 jupiter2 NetworkManager: <info> (wlan0): device state change: 8 -> 1
Oct 15 08:28:55 jupiter2 NetworkManager: <info> (wlan0): deactivating device.
Oct 15 08:28:55 jupiter2 NetworkManager: <info> wlan0: canceled DHCP transaction, dhcp client pid 8501
Oct 15 08:28:55 jupiter2 modprobe: WARNING: Not loading blacklisted module rt73
Oct 15 08:28:55 jupiter2 modprobe: WARNING: Not loading blacklisted module rt73
Oct 15 08:28:55 jupiter2 NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed
Oct 15 08:28:55 jupiter2 NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed
Oct 15 08:28:55 jupiter2 modprobe: WARNING: Not loading blacklisted module rt73
Oct 15 08:28:55 jupiter2 last message repeated 2 times
Oct 15 08:28:55 jupiter2 NetworkManager: <info> (wlan0): cleaning up...
Oct 15 08:28:55 jupiter2 modprobe: WARNING: Not loading blacklisted module rt73
Oct 15 08:28:55 jupiter2 nm-dispatcher.action: Error in get_property: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist
Oct 15 08:28:55 jupiter2 modprobe: WARNING: Not loading blacklisted module rt73
Oct 15 08:28:55 jupiter2 last message repeated 13 times
Oct 15 08:29:10 jupiter2 kernel: [ 6019.060139] phy0: Selected rate control algorithm 'pid'
Oct 15 08:29:10 jupiter2 kernel: [ 6019.060438] Registered led device: rt73usb-phy0:radio
Oct 15 08:29:10 jupiter2 kernel: [ 6019.060452] Registered led device: rt73usb-phy0:assoc
Oct 15 08:29:10 jupiter2 kernel: [ 6019.060464] Registered led device: rt73usb-phy0:quality
Oct 15 08:29:10 jupiter2 kernel: [ 6019.061014] usbcore: registered new interface driver rt73usb
Oct 15 08:29:10 jupiter2 nm-system-settings: SCPlugin-Ifupdown: devices added (udi: /org/freedesktop/Hal/devices/net_00_16_44_7c_a0_e2_0, iface: wlan0)
Oct 15 08:29:10 jupiter2 NetworkManager: <info> wlan0: driver is 'rt73usb'.
Oct 15 08:29:10 jupiter2 NetworkManager: <info> wlan0: driver supports SSID scans (scan_capa 0x01).
Oct 15 08:29:10 jupiter2 NetworkManager: <info> Found new 802.11 WiFi device 'wlan0'.
Oct 15 08:29:10 jupiter2 NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_16_44_7c_a0_e2_0
Oct 15 08:29:13 jupiter2 kernel: [ 6022.272165] firmware: requesting rt73.bin
Oct 15 08:29:14 jupiter2 NetworkManager: <info> (wlan0): device state change: 1 -> 2
Oct 15 08:29:14 jupiter2 NetworkManager: <info> (wlan0): preparing device.
Oct 15 08:29:14 jupiter2 NetworkManager: <info> (wlan0): deactivating device.
Oct 15 08:29:14 jupiter2 NetworkManager: <info> (wlan0): device state change: 2 -> 3
Oct 15 08:29:14 jupiter2 NetworkManager: <info> (wlan0): supplicant interface state change: 1 -> 2.
Oct 15 08:29:14 jupiter2 NetworkManager: <info> Activation (wlan0) starting connection 'Auto LODGER'
Oct 15 08:29:14 jupiter2 NetworkManager: <info> (wlan0): device state change: 3 -> 4
Oct 15 08:29:14 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 15 08:29:14 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct 15 08:29:14 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct 15 08:29:14 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct 15 08:29:14 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct 15 08:29:14 jupiter2 NetworkManager: <info> (wlan0): device state change: 4 -> 5
Oct 15 08:29:14 jupiter2 NetworkManager: <info> Activation (wlan0/wireless): access point 'Auto LODGER' has security, but secrets are required.
Oct 15 08:29:14 jupiter2 NetworkManager: <info> (wlan0): device state change: 5 -> 6
Oct 15 08:29:14 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct 15 08:29:15 jupiter2 kernel: [ 6023.884609] wlan0: authenticate with AP 00:16:b6:2e:13:f8
Oct 15 08:29:15 jupiter2 kernel: [ 6023.886242] wlan0: authenticated
Oct 15 08:29:15 jupiter2 kernel: [ 6023.886247] wlan0: associate with AP 00:16:b6:2e:13:f8
Oct 15 08:29:15 jupiter2 kernel: [ 6023.888496] wlan0: RX AssocResp from 00:16:b6:2e:13:f8 (capab=0x401 status=0 aid=4)
Oct 15 08:29:15 jupiter2 kernel: [ 6023.888501] wlan0: associated
Oct 15 08:29:15 jupiter2 kernel: [ 6023.889065] wlan0: disassociating by local choice (reason=3)
Oct 15 08:29:15 jupiter2 NetworkManager: <info> (wlan0): supplicant connection state change: 1 -> 4
Oct 15 08:29:15 jupiter2 NetworkManager: <info> (wlan0): supplicant connection state change: 4 -> 0
Oct 15 08:29:15 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 15 08:29:15 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct 15 08:29:15 jupiter2 NetworkManager: <info> (wlan0): device state change: 6 -> 4
Oct 15 08:29:15 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct 15 08:29:15 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct 15 08:29:15 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct 15 08:29:15 jupiter2 NetworkManager: <info> (wlan0): device state change: 4 -> 5
Oct 15 08:29:15 jupiter2 NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto LODGER' has security, and secrets exist. No new secrets needed.
Oct 15 08:29:15 jupiter2 NetworkManager: <info> Config: added 'ssid' value 'LODGER'
Oct 15 08:29:15 jupiter2 NetworkManager: <info> Config: added 'scan_ssid' value '1'
Oct 15 08:29:15 jupiter2 NetworkManager: <info> Config: added 'bssid' value '00:0f:3d:39:10:96'
Oct 15 08:29:15 jupiter2 NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
Oct 15 08:29:15 jupiter2 NetworkManager: <info> Config: added 'auth_alg' value 'SHARED'
Oct 15 08:29:15 jupiter2 NetworkManager: <info> Config: added 'wep_key0' value '<omitted>'
Oct 15 08:29:15 jupiter2 NetworkManager: <info> Config: added 'wep_tx_keyidx' value '0'
Oct 15 08:29:15 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct 15 08:29:15 jupiter2 NetworkManager: <info> Config: set interface ap_scan to 1
Oct 15 08:29:19 jupiter2 NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 2
Oct 15 08:29:20 jupiter2 NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 3
Oct 15 08:29:21 jupiter2 kernel: [ 6030.477636] wlan0: authenticate with AP 00:0f:3d:39:10:96
Oct 15 08:29:21 jupiter2 kernel: [ 6030.484519] wlan0: authenticated
Oct 15 08:29:21 jupiter2 kernel: [ 6030.484523] wlan0: associate with AP 00:0f:3d:39:10:96
Oct 15 08:29:21 jupiter2 kernel: [ 6030.486778] wlan0: RX AssocResp from 00:0f:3d:39:10:96 (capab=0x431 status=0 aid=1)
Oct 15 08:29:21 jupiter2 kernel: [ 6030.486782] wlan0: associated
Oct 15 08:29:21 jupiter2 NetworkManager: <info> (wlan0): supplicant connection state change: 3 -> 4
Oct 15 08:29:21 jupiter2 NetworkManager: <info> (wlan0): supplicant connection state change: 4 -> 7
Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'LODGER'.
Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Oct 15 08:29:21 jupiter2 NetworkManager: <info> (wlan0): device state change: 5 -> 7
Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction.
Oct 15 08:29:21 jupiter2 NetworkManager: <info> dhclient started with pid 10598
Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Oct 15 08:29:21 jupiter2 dhclient: Internet Systems Consortium DHCP Client V3.1.1
Oct 15 08:29:21 jupiter2 dhclient: Copyright 2004-2008 Internet Systems Consortium.
Oct 15 08:29:21 jupiter2 dhclient: All rights reserved.
Oct 15 08:29:21 jupiter2 dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Oct 15 08:29:21 jupiter2 dhclient:
Oct 15 08:29:21 jupiter2 dhclient: wmaster0: unknown hardware address type 801
Oct 15 08:29:21 jupiter2 NetworkManager: <info> DHCP: device wlan0 state changed normal exit -> preinit
Oct 15 08:29:21 jupiter2 dhclient: wmaster0: unknown hardware address type 801
Oct 15 08:29:21 jupiter2 dhclient: Listening on LPF/wlan0/00:16:44:7c:a0:e2
Oct 15 08:29:21 jupiter2 dhclient: Sending on LPF/wlan0/00:16:44:7c:a0:e2
Oct 15 08:29:21 jupiter2 dhclient: Sending on Socket/fallback
Oct 15 08:29:21 jupiter2 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Oct 15 08:29:21 jupiter2 dhclient: DHCPOFFER of 192.168.0.100 from 192.168.0.1
Oct 15 08:29:21 jupiter2 dhclient: DHCPREQUEST of 192.168.0.100 on wlan0 to 255.255.255.255 port 67
Oct 15 08:29:21 jupiter2 dhclient: DHCPACK of 192.168.0.100 from 192.168.0.1
Oct 15 08:29:21 jupiter2 NetworkManager: <info> DHCP: device wlan0 state changed preinit -> bound
Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled...
Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) started...
Oct 15 08:29:21 jupiter2 NetworkManager: <info> address 192.168.0.100
Oct 15 08:29:21 jupiter2 NetworkManager: <info> prefix 24 (255.255.255.0)
Oct 15 08:29:21 jupiter2 NetworkManager: <info> gateway 192.168.0.1
Oct 15 08:29:21 jupiter2 NetworkManager: <info> nameserver '192.168.0.1'
Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
Oct 15 08:29:21 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Oct 15 08:29:21 jupiter2 avahi-daemon[5359]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.100.
Oct 15 08:29:21 jupiter2 dhclient: bound to 192.168.0.100 -- renewal in 290345 seconds.
Oct 15 08:29:21 jupiter2 avahi-daemon[5359]: New relevant interface wlan0.IPv4 for mDNS.
Oct 15 08:29:21 jupiter2 avahi-daemon[5359]: Registering new address record for 192.168.0.100 on wlan0.IPv4.
Oct 15 08:29:22 jupiter2 NetworkManager: <info> (wlan0): device state change: 7 -> 8
Oct 15 08:29:22 jupiter2 NetworkManager: <info> Policy set (wlan0) as default device for routing and DNS.
Oct 15 08:29:22 jupiter2 NetworkManager: <info> Activation (wlan0) successful, device activated.
Oct 15 08:29:22 jupiter2 NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Oct 15 08:29:22 jupiter2 ntpd[8629]: ntpd exiting on signal 15
Oct 15 08:29:23 jupiter2 ntpdate[10687]: adjust time server 91.189.94.4 offset -0.006663 sec
Oct 15 08:29:23 jupiter2 ntpd[10721]: ntpd 4.2.4p4@1.1520-o Wed Aug 20 17:03:52 UTC 2008 (1)
Oct 15 08:29:23 jupiter2 ntpd[10722]: precision = 1.000 usec

What do you all think? Does this shed more late anywhere!!???

Revision history for this message
Nicolas Boucher (boucher-nicolas) wrote :

Had the same problem on Mandriva 2009 and thought it may not occurs with Ubuntu 8.10, but it is the same thing.

Revision history for this message
Nicolas Boucher (boucher-nicolas) wrote :

The connection is lost after a time that is proportional as the quantity of data you exchange!
For exemple Internet surfing will last one day.
But FTP with a high rate or a Skype video conference will provoque a RT73USB connection lost after 5 minutes of use.
I can add the hardware description :

Fabricant: ‎Ralink
Description: ‎802.11 bg WLAN
Classe de matériel: ‎
Connexion
Bus: ‎USB
Bus PCI n°: ‎1
Périphérique PCI n°: ‎2
Identifiant du fabricant: ‎0x15a9
Identifiant du périphérique: ‎0x0004
Identifiant secondaire du fabricant: ‎0x0000
Identifiant secondaire du périphérique: ‎0x0000

Revision history for this message
joshyg6 (josheg) wrote : Re: [Bug 283759] Re: rt73usb intrepid 8.10 beta -- wireless connection periodically lost; must restart driver
Download full text (15.3 KiB)

did you figure that from my outputs? really? so what do you
suggest/propose? that's rather fascinating..

j

On Fri, Oct 17, 2008 at 7:58 AM, <email address hidden>
<email address hidden> wrote:
> The connection is lost after a time that is proportional as the quantity of data you exchange!
> For exemple Internet surfing will last one day.
> But FTP with a high rate or a Skype video conference will provoque a RT73USB connection lost after 5 minutes of use.
> I can add the hardware description :
>
> Fabricant: ‎Ralink
> Description: ‎802.11 bg WLAN
> Classe de matériel: ‎
> Connexion
> Bus: ‎USB
> Bus PCI n°: ‎1
> Périphérique PCI n°: ‎2
> Identifiant du fabricant: ‎0x15a9
> Identifiant du périphérique: ‎0x0004
> Identifiant secondaire du fabricant: ‎0x0000
> Identifiant secondaire du périphérique: ‎0x0000
>
> --
> rt73usb intrepid 8.10 beta -- wireless connection periodically lost; must restart driver
> https://bugs.launchpad.net/bugs/283759
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
> Status in Mandriva Linux: In Progress
>
> Bug description:
> I may have something.. So I blacklisted the recompiled/newly installed legacy rt73 drivers, and i went back to using the rt73usb included initially with intrepid. i was using the Internet as normal, and then it crapped out, and these are the tail logs..
>
> Quote:
> Oct 15 07:53:19 jupiter2 NetworkManager: <debug> [1224071599.522971] periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:3D:39:10:96 (LODGER)
> Oct 15 07:55:13 jupiter2 NetworkManager: <debug> [1224071713.601943] periodic_update(): Roamed from BSSID 00:0F:3D:39:10:96 (LODGER) to (none) ((none))
> Oct 15 07:55:19 jupiter2 NetworkManager: <debug> [1224071719.605557] periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:3D:39:10:96 (LODGER)
>
> ****** Connection seemed to crap out around this point!!!********
>
> Oct 15 08:00:01 jupiter2 /USR/SBIN/CRON[9353]: (root) CMD ([ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
> Oct 15 08:03:26 jupiter2 kernel: [ 4474.961767] usb 8-5.2: reset high speed USB device using ehci_hcd and address 4
> Oct 15 08:10:01 jupiter2 /USR/SBIN/CRON[9577]: (root) CMD ([ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
> Oct 15 08:17:01 jupiter2 /USR/SBIN/CRON[9828]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
> Oct 15 08:20:01 jupiter2 /USR/SBIN/CRON[10010]: (root) CMD ([ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528260] phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2.
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528262] Please file bug report to http://rt2x00.serialmonkey.com.
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528340] phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2.
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528341] Please file bug report to http://rt2x00.serialmonkey.com.
>
> ****** At this point here, I sudo ifconfig wlan0 down. Then I sudo modprobe -r rt73usb. Then I sudo modprobe rt73usb. Then I sudo ifconfig wl...

Revision history for this message
Nicolas Boucher (boucher-nicolas) wrote :

Yes because I had the same problem during 1 month with a Mandriva 2009 beta version, and now with the official release. I have change to a Ubuntu distribution because I like both of them and also because I tought I wouldn't have this bug in ubuntu but it is not the case.

Those are the ouputs I could catch from my Mandriva message log the 20/09/08 :

Sep 20 19:21:00 localhost ntpd[5290]: kernel time sync status change 0001
Sep 20 19:55:10 localhost ntpd[5290]: kernel time sync status change 4001
Sep 20 20:01:01 localhost CROND[29874]: (root) CMD (nice -n 19 run-parts--report /etc/cron.hourly)
*Sep 20 20:10:04 localhost kernel: phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2.
Sep 20 20:10:04 localhost kernel: Please file bug report to http://rt2x00.serialmonkey.com.

I have also see an interesting thread of messages between people working on the Linux kernel (i suppose) talking about this kind of error message as a Kernel regression :

http://groups.google.com/group/linux.kernel/browse_thread/thread/189864466d6ed5f4/5189422969b027b8?lnk=raot

Well I would like to see this bug corrected because I guess every RT73USB module users will be impacted by this lost of connection which in my case happens 10 times a day.

I remember this RT73USB module had an abnormal slow rate, and now that this point is fixed, it is unstable as it disconnects...

Revision history for this message
joshyg6 (josheg) wrote :
Download full text (16.4 KiB)

yeah, i agree.. mine drops often too... i fixed the slow rate, though,
by modifying the tx rate (trial and error) to match well the router i
had.. and doing speedtest.net tests, to see which were fastest..
eventually i settled on 54M for now.. do you know what queue2 is? or
what phy0 is? what is it storing there in the "frame"? is there any
way to see what gets written and cleared there?

On Fri, Oct 17, 2008 at 11:29 AM, <email address hidden>
<email address hidden> wrote:
> Yes because I had the same problem during 1 month with a Mandriva 2009
> beta version, and now with the official release. I have change to a
> Ubuntu distribution because I like both of them and also because I
> tought I wouldn't have this bug in ubuntu but it is not the case.
>
> Those are the ouputs I could catch from my Mandriva message log the
> 20/09/08 :
>
> Sep 20 19:21:00 localhost ntpd[5290]: kernel time sync status change 0001
> Sep 20 19:55:10 localhost ntpd[5290]: kernel time sync status change 4001
> Sep 20 20:01:01 localhost CROND[29874]: (root) CMD (nice -n 19 run-parts--report /etc/cron.hourly)
> *Sep 20 20:10:04 localhost kernel: phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2.
> Sep 20 20:10:04 localhost kernel: Please file bug report to http://rt2x00.serialmonkey.com.
>
> I have also see an interesting thread of messages between people working
> on the Linux kernel (i suppose) talking about this kind of error message
> as a Kernel regression :
>
> http://groups.google.com/group/linux.kernel/browse_thread/thread/189864466d6ed5f4/5189422969b027b8?lnk=raot
>
> Well I would like to see this bug corrected because I guess every
> RT73USB module users will be impacted by this lost of connection which
> in my case happens 10 times a day.
>
> I remember this RT73USB module had an abnormal slow rate, and now that
> this point is fixed, it is unstable as it disconnects...
>
> --
> rt73usb intrepid 8.10 beta -- wireless connection periodically lost; must restart driver
> https://bugs.launchpad.net/bugs/283759
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
> Status in Mandriva Linux: In Progress
>
> Bug description:
> I may have something.. So I blacklisted the recompiled/newly installed legacy rt73 drivers, and i went back to using the rt73usb included initially with intrepid. i was using the Internet as normal, and then it crapped out, and these are the tail logs..
>
> Quote:
> Oct 15 07:53:19 jupiter2 NetworkManager: <debug> [1224071599.522971] periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:3D:39:10:96 (LODGER)
> Oct 15 07:55:13 jupiter2 NetworkManager: <debug> [1224071713.601943] periodic_update(): Roamed from BSSID 00:0F:3D:39:10:96 (LODGER) to (none) ((none))
> Oct 15 07:55:19 jupiter2 NetworkManager: <debug> [1224071719.605557] periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:3D:39:10:96 (LODGER)
>
> ****** Connection seemed to crap out around this point!!!********
>
> Oct 15 08:00:01 jupiter2 /USR/SBIN/CRON[9353]: (root) CMD ([ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
> Oct 15 08:03:2...

Revision history for this message
Nicolas Boucher (boucher-nicolas) wrote :
Download full text (6.5 KiB)

I have found the file where it writes the same logs as yours : kernel.log
I have put the Ubuntu kernel time network in this thread because they may be helpful to resolve this RT73USB periodically connection lost.
Hope they can decided about status and importance of this bug.
Thanks!
Nicolas

Oct 16 21:17:27 Ubuntu-Nicolas kernel: [ 27.489702] firmware: requesting rt73.bin
Oct 16 21:17:27 Ubuntu-Nicolas kernel: [ 27.697766] NET: Registered protocol family 17
Oct 16 21:17:39 Ubuntu-Nicolas kernel: [ 39.711470] NET: Registered protocol family 10
Oct 16 21:17:39 Ubuntu-Nicolas kernel: [ 39.712148] lo: Disabled Privacy Extensions
Oct 16 21:17:39 Ubuntu-Nicolas kernel: [ 39.712890] ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct 16 21:17:39 Ubuntu-Nicolas kernel: [ 39.713695] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct 16 21:18:15 Ubuntu-Nicolas kernel: [ 75.530407] wlan0: authenticate with AP f2:3f:8b:e3:17:f0
Oct 16 21:18:15 Ubuntu-Nicolas kernel: [ 75.531913] wlan0: authenticated
Oct 16 21:18:15 Ubuntu-Nicolas kernel: [ 75.531923] wlan0: associate with AP f2:3f:8b:e3:17:f0
Oct 16 21:18:15 Ubuntu-Nicolas kernel: [ 75.535158] wlan0: RX AssocResp from f2:3f:8b:e3:17:f0 (capab=0x411 status=0 aid=1)
Oct 16 21:18:15 Ubuntu-Nicolas kernel: [ 75.535165] wlan0: associated
Oct 16 21:18:15 Ubuntu-Nicolas kernel: [ 75.535752] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Oct 16 21:18:26 Ubuntu-Nicolas kernel: [ 86.388012] wlan0: no IPv6 routers present
Oct 16 21:18:46 Ubuntu-Nicolas kernel: [ 106.306448] type=1503 audit(1224184726.124:5): operation="inode_permission" requested_mask="r::" denied_mask="r::" fsuid=7 name="/proc/7298/net/" pid=7298 profile="/usr/sbin/cupsd"
Oct 16 21:18:47 Ubuntu-Nicolas kernel: [ 107.334861] type=1503 audit(1224184727.150:6): operation="inode_permission" requested_mask="r::" denied_mask="r::" fsuid=7 name="/proc/7306/net/" pid=7306 profile="/usr/sbin/cupsd"
Oct 16 21:18:47 Ubuntu-Nicolas kernel: [ 107.334895] type=1503 audit(1224184727.150:7): operation="socket_create" family="ax25" sock_type="dgram" protocol=0 pid=7306 profile="/usr/sbin/cupsd"
Oct 16 21:18:47 Ubuntu-Nicolas kernel: [ 107.334903] type=1503 audit(1224184727.150:8): operation="socket_create" family="netrom" sock_type="seqpacket" protocol=0 pid=7306 profile="/usr/sbin/cupsd"
Oct 16 21:18:47 Ubuntu-Nicolas kernel: [ 107.334910] type=1503 audit(1224184727.150:9): operation="socket_create" family="rose" sock_type="dgram" protocol=0 pid=7306 profile="/usr/sbin/cupsd"
Oct 16 21:18:47 Ubuntu-Nicolas kernel: [ 107.334926] type=1503 audit(1224184727.150:10): operation="socket_create" family="ipx" sock_type="dgram" protocol=0 pid=7306 profile="/usr/sbin/cupsd"
Oct 16 21:18:47 Ubuntu-Nicolas kernel: [ 107.334933] type=1503 audit(1224184727.150:11): operation="socket_create" family="appletalk" sock_type="dgram" protocol=0 pid=7306 profile="/usr/sbin/cupsd"
Oct 16 21:18:47 Ubuntu-Nicolas kernel: [ 107.334940] type=1503 audit(1224184727.150:12): operation="socket_create" family="econet" sock_type="dgram" protocol=0 pid=7306 profile="/usr/sbin/cupsd"
Oct 16 21:18:47 Ubuntu-Nicolas kernel: [ 107.334947] type=1503 audit(1224184727...

Read more...

Revision history for this message
joshyg6 (josheg) wrote :

People seem to think this is related to the IP STACK.. as in it's a deeper problem than just the drivers driving the wireless connections... What do you all think????

Revision history for this message
joshyg6 (josheg) wrote :

OOOH I THINK I FOUND A PROVISIONAL SOLUTION! It seems that using the "linux-backports-modules-'versionname'" does the trick, and uses a more recent rt73usb/rt2x00 driver set/library which doesn't have the issues anymore!!!!!! so said serialmonkey as well, that it could use a more recent driver set with that module.. what do you think??

Revision history for this message
Owen Tuz (owentuz) wrote :

By 'versionname' do you mean the current version of the drivers? Sorry, but how would I find that? This internet thing is getting annoying :(

Revision history for this message
Owen Tuz (owentuz) wrote :

Ignore previous comment.

It's early days yet, but installing "linux-backports-modules-[kernel version here]-generic" package from my package manager appears to have solved this.

I use Skype daily and prior to this was unable to carry on a conversation without the internet disconnecting partway through - now for two days running I have had no problem with this and was even able to stream live video whilst Skyping last night with no connection loss (although it didn't do the Skype call much good!).#
 Like I said, early days, but thank you joshyg6.

Revision history for this message
Owen Tuz (owentuz) wrote :

Ignore previous comment.

It's early days yet, but installing "linux-backports-modules-[kernel version here]-generic" package from my package manager appears to have solved this.

I use Skype daily and prior to this was unable to carry on a conversation without the internet disconnecting partway through - now for two days running I have had no problem with this and was even able to stream live video whilst Skyping last night with no connection loss (although it didn't do the Skype call much good!).
 Like I said, early days, but thank you joshyg6.

Revision history for this message
Owen Tuz (owentuz) wrote :

Sorry for double post if someone who has the power could remove one that'd be nice.

Revision history for this message
Ivo Jimenez (ivotron) wrote :
Download full text (5.4 KiB)

Hi,

I'm also having this issue. The output of dmesg:

  138.288033] usb 2-10: new high speed USB device using ehci_hcd and address 17
[ 138.581980] usb 2-10: configuration #1 chosen from 1 choice
[ 138.851273] phy10: Selected rate control algorithm 'pid'
[ 138.860059] Registered led device: rt73usb-phy10:radio
[ 138.860187] Registered led device: rt73usb-phy10:assoc
[ 138.860269] Registered led device: rt73usb-phy10:quality
[ 142.908455] firmware: requesting rt73.bin
[ 143.002097] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 149.372753] usb 2-10: USB disconnect, address 17
[ 149.384792] phy10 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3040 with error -19.
[ 149.384819] phy10 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3040 with error -19.
[ 149.384829] phy10 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3028 with error -19.
[ 149.384837] phy10 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3064 with error -19.
[ 149.384845] phy10 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0c failed for offset 0x0000 with error -19.
[ 149.384904] phy10 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
[ 149.388624] phy10 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
[ 149.388710] phy10 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
[ 149.388773] phy10 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
[ 149.800055] usb 2-10: new high speed USB device using ehci_hcd and address 18
[ 150.095898] usb 2-10: configuration #1 chosen from 1 choice
[ 150.367588] phy11: Selected rate control algorithm 'pid'
[ 150.369743] Registered led device: rt73usb-phy11:radio
[ 150.369785] Registered led device: rt73usb-phy11:assoc
[ 150.369827] Registered led device: rt73usb-phy11:quality
[ 154.420685] firmware: requesting rt73.bin
[ 154.509224] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 161.020421] usb 2-10: USB disconnect, address 18
[ 161.025345] phy11 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3040 with error -19.
[ 161.025360] phy11 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3040 with error -19.
[ 161.025369] phy11 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3028 with error -19.
[ 161.025376] phy11 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3064 with error -19.
[ 161.025384] phy11 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0c failed for offset 0x0000 with error -19.
[ 161.025432] phy11 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
[ 161.025632] phy11 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
[ 161.025686] phy11 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
[ 161.025750] phy11 -> rt2x00usb_vendor_reques...

Read more...

Revision history for this message
joshyg6 (josheg) wrote :
Download full text (20.2 KiB)

read previous posts in thread.. backports!

On Thu, Nov 6, 2008 at 2:37 AM, Ivo Jimenez <email address hidden> wrote:
> Hi,
>
> I'm also having this issue. The output of dmesg:
>
> 138.288033] usb 2-10: new high speed USB device using ehci_hcd and address 17
> [ 138.581980] usb 2-10: configuration #1 chosen from 1 choice
> [ 138.851273] phy10: Selected rate control algorithm 'pid'
> [ 138.860059] Registered led device: rt73usb-phy10:radio
> [ 138.860187] Registered led device: rt73usb-phy10:assoc
> [ 138.860269] Registered led device: rt73usb-phy10:quality
> [ 142.908455] firmware: requesting rt73.bin
> [ 143.002097] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [ 149.372753] usb 2-10: USB disconnect, address 17
> [ 149.384792] phy10 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3040 with error -19.
> [ 149.384819] phy10 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3040 with error -19.
> [ 149.384829] phy10 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3028 with error -19.
> [ 149.384837] phy10 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3064 with error -19.
> [ 149.384845] phy10 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0c failed for offset 0x0000 with error -19.
> [ 149.384904] phy10 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
> [ 149.388624] phy10 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
> [ 149.388710] phy10 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
> [ 149.388773] phy10 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
> [ 149.800055] usb 2-10: new high speed USB device using ehci_hcd and address 18
> [ 150.095898] usb 2-10: configuration #1 chosen from 1 choice
> [ 150.367588] phy11: Selected rate control algorithm 'pid'
> [ 150.369743] Registered led device: rt73usb-phy11:radio
> [ 150.369785] Registered led device: rt73usb-phy11:assoc
> [ 150.369827] Registered led device: rt73usb-phy11:quality
> [ 154.420685] firmware: requesting rt73.bin
> [ 154.509224] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [ 161.020421] usb 2-10: USB disconnect, address 18
> [ 161.025345] phy11 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3040 with error -19.
> [ 161.025360] phy11 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3040 with error -19.
> [ 161.025369] phy11 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3028 with error -19.
> [ 161.025376] phy11 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3064 with error -19.
> [ 161.025384] phy11 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0c failed for offset 0x0000 with error -19.
> [ 161.025432] phy11 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
> [ 161.025632] phy11 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offs...

Revision history for this message
Nicolas Boucher (boucher-nicolas) wrote :

I have blacklisted RT73USB and I am using RT73 instead. It's not supported by the network-manager but it's not a problem as it allows me not to fill in the password for each session (Ubuntu key manager).
I have a tutorial to make that changes in Ubuntu.

http://linuxbidouille.com/2008/10/25/wifi-rt73-rt73usb/

Hope that can help it is in French but the command line in the console is the only thing you need.

Revision history for this message
joshyg6 (josheg) wrote :
Download full text (15.0 KiB)

installing linux-backports-modules-'versionname' permanently fixed the
issue for me... i think 'cause it's a more recent rt2x00 and rt73usb
compilation from serialmonkey included... ??? so says some of the
posts by the serialmonkey authors..

On Mon, Nov 10, 2008 at 4:12 AM, Bug Watch Updater
<email address hidden> wrote:
> ** Changed in: fedora
> Status: Unknown => Confirmed
>
> --
> rt73usb intrepid 8.10 beta -- wireless connection periodically lost; must restart driver
> https://bugs.launchpad.net/bugs/283759
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The rt2x00 Project: New
> Status in Ubuntu: New
> Status in Fedora: Confirmed
> Status in Mandriva Linux: In Progress
>
> Bug description:
> I may have something.. So I blacklisted the recompiled/newly installed legacy rt73 drivers, and i went back to using the rt73usb included initially with intrepid. i was using the Internet as normal, and then it crapped out, and these are the tail logs..
>
> Quote:
> Oct 15 07:53:19 jupiter2 NetworkManager: <debug> [1224071599.522971] periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:3D:39:10:96 (LODGER)
> Oct 15 07:55:13 jupiter2 NetworkManager: <debug> [1224071713.601943] periodic_update(): Roamed from BSSID 00:0F:3D:39:10:96 (LODGER) to (none) ((none))
> Oct 15 07:55:19 jupiter2 NetworkManager: <debug> [1224071719.605557] periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:3D:39:10:96 (LODGER)
>
> ****** Connection seemed to crap out around this point!!!********
>
> Oct 15 08:00:01 jupiter2 /USR/SBIN/CRON[9353]: (root) CMD ([ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
> Oct 15 08:03:26 jupiter2 kernel: [ 4474.961767] usb 8-5.2: reset high speed USB device using ehci_hcd and address 4
> Oct 15 08:10:01 jupiter2 /USR/SBIN/CRON[9577]: (root) CMD ([ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
> Oct 15 08:17:01 jupiter2 /USR/SBIN/CRON[9828]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
> Oct 15 08:20:01 jupiter2 /USR/SBIN/CRON[10010]: (root) CMD ([ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528260] phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2.
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528262] Please file bug report to http://rt2x00.serialmonkey.com.
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528340] phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2.
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528341] Please file bug report to http://rt2x00.serialmonkey.com.
>
> ****** At this point here, I sudo ifconfig wlan0 down. Then I sudo modprobe -r rt73usb. Then I sudo modprobe rt73usb. Then I sudo ifconfig wlan0 up. Then I reselect the proper network from the NetworkManager drop down, and then it connects and I have internet again! ****************
>
>
> Oct 15 08:28:48 jupiter2 avahi-daemon[5359]: Interface wlan0.IPv4 no longer relevant for mDNS.
> Oct 15 08:28:48 jupiter2 avahi-daemon[5359]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0...

Revision history for this message
Ivo Jimenez (ivotron) wrote :

I installed the linux-backports-modules-'versionname' package and it didn't solve the issue for me. I'm still plugged to the cord :-(

Revision history for this message
cobas (david-cobas) wrote :

My Belkin USB dongle worked flawlessly all the summer until I noticed this bug about two weeks ago (¿8.10?).
I get the same error:

Nov 15 22:03:40 desktop kernel: [76991.204719] phy11 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2.
Nov 15 22:03:40 desktop kernel: [76991.204720] Please file bug report to http://rt2x00.serialmonkey.com.

However, there's something very disturbing. This happens *only* when I put the dongle on its dock (a photo: http://images.productserve.com/preview/1256/14458469.jpg), which seems to be nothing but a usb extension cord.
I made heavy-duty tests and this pattern repeats consistently. It seems very weird. Does this make sense?

[Only additional difference: the usb connector to which I attach the device is different, for reasons of available space].

Thanks,

              David

Revision history for this message
Stuart Bishop (stub) wrote :

Can anyone confirm if this is a duplicate of Bug #251604 ? This behavior started happening in Hardy with the proposed linux-backports-modules-2.6.24 package. I'm not sure if it is the same bug though.

Revision history for this message
Stuart Bishop (stub) wrote :

Sorry - that should be Bug #258985.

Revision history for this message
joshyg6 (josheg) wrote :
Download full text (15.0 KiB)

using the linux backports module seemed to actually fix this problem for
me...

On Mon, Nov 17, 2008 at 7:00 AM, Stuart Bishop <email address hidden>wrote:

> Sorry - that should be Bug #258985.
>
> --
> rt73usb intrepid 8.10 beta -- wireless connection periodically lost; must
> restart driver
> https://bugs.launchpad.net/bugs/283759
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The rt2x00 Project: New
> Status in Ubuntu: New
> Status in Fedora: Confirmed
> Status in Mandriva Linux: In Progress
>
> Bug description:
> I may have something.. So I blacklisted the recompiled/newly installed
> legacy rt73 drivers, and i went back to using the rt73usb included initially
> with intrepid. i was using the Internet as normal, and then it crapped out,
> and these are the tail logs..
>
> Quote:
> Oct 15 07:53:19 jupiter2 NetworkManager: <debug> [1224071599.522971]
> periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:3D:39:10:96
> (LODGER)
> Oct 15 07:55:13 jupiter2 NetworkManager: <debug> [1224071713.601943]
> periodic_update(): Roamed from BSSID 00:0F:3D:39:10:96 (LODGER) to (none)
> ((none))
> Oct 15 07:55:19 jupiter2 NetworkManager: <debug> [1224071719.605557]
> periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:3D:39:10:96
> (LODGER)
>
> ****** Connection seemed to crap out around this point!!!********
>
> Oct 15 08:00:01 jupiter2 /USR/SBIN/CRON[9353]: (root) CMD ([ -x
> /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
> Oct 15 08:03:26 jupiter2 kernel: [ 4474.961767] usb 8-5.2: reset high speed
> USB device using ehci_hcd and address 4
> Oct 15 08:10:01 jupiter2 /USR/SBIN/CRON[9577]: (root) CMD ([ -x
> /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
> Oct 15 08:17:01 jupiter2 /USR/SBIN/CRON[9828]: (root) CMD ( cd / &&
> run-parts --report /etc/cron.hourly)
> Oct 15 08:20:01 jupiter2 /USR/SBIN/CRON[10010]: (root) CMD ([ -x
> /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528260] phy0 ->
> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the
> non-full queue 2.
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528262] Please file bug report to
> http://rt2x00.serialmonkey.com.
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528340] phy0 ->
> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the
> non-full queue 2.
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528341] Please file bug report to
> http://rt2x00.serialmonkey.com.
>
> ****** At this point here, I sudo ifconfig wlan0 down. Then I sudo modprobe
> -r rt73usb. Then I sudo modprobe rt73usb. Then I sudo ifconfig wlan0 up.
> Then I reselect the proper network from the NetworkManager drop down, and
> then it connects and I have internet again! ****************
>
>
> Oct 15 08:28:48 jupiter2 avahi-daemon[5359]: Interface wlan0.IPv4 no longer
> relevant for mDNS.
> Oct 15 08:28:48 jupiter2 avahi-daemon[5359]: Leaving mDNS multicast group
> on interface wlan0.IPv4 with address 192.168.0.100.
> Oct 15 08:28:48 jupiter2 dhclient: receive_packet failed on wlan0: Network
> is down
> Oct 15 08:28:48 jupiter2 avahi-daemon[5359]: Wit...

Revision history for this message
Nicolas Boucher (boucher-nicolas) wrote :

@Stuart
Hi,
To my point of view this is a duplicate bug ! When you see the thread of Bug #258985, you can see that the only difference is the fact that there are happenning in two different version (Hardy, and Intrepid). But it's only a matter of kernel level. At the time the answer to this point was :

"Steve Beattie wrote on 2008-10-17: (permalink)
Nicolas, thanks for your comment and the pointer to bug 283759; people who are having trouble this hardware under Intrepid should follow that bug. Closing out that portion of this bug."

Revision history for this message
Ivo Jimenez (ivotron) wrote :

I updated from linux-image-2.6.27-8 to linux-image-2.6.27-10 today and the connection issues have improved. My machine keeps disconnecting though, don't know if it's every few MB transfered or every few minutes. I'll keep testing. I used the backports package for 2.6.27-8 but not for this one. I'll try it out to see if improves.

Cheers

Revision history for this message
Ivo Jimenez (ivotron) wrote :

I installed linux-backports-2.6.27-10-generic and the driver isn't being loaded:

[ 11.156574] cfg80211: Using static regulatory domain info
[ 11.156577] cfg80211: Regulatory domain: US
[ 11.156578] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 11.156580] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
[ 11.156582] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 11.156584] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 11.156585] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 11.156587] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 11.156589] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 11.156590] cfg80211: Calling CRDA for country: US
[ 11.261480] rt2x00lib: no symbol version for lbm_cw_lbm_cw_ieee80211_iterate_active_interfaces_atomic
[ 11.261483] rt2x00lib: Unknown symbol lbm_cw_lbm_cw_ieee80211_iterate_active_interfaces_atomic
[ 11.262350] rt2x00usb: Unknown symbol rt2x00lib_suspend
[ 11.262408] rt2x00usb: Unknown symbol rt2x00lib_probe_dev
[ 11.262624] rt2x00usb: Unknown symbol rt2x00lib_rxdone
[ 11.262796] rt2x00usb: Unknown symbol rt2x00lib_remove_dev
[ 11.262853] rt2x00usb: Unknown symbol rt2x00lib_txdone
[ 11.262967] rt2x00usb: Unknown symbol rt2x00queue_get_queue
[ 11.263146] rt2x00usb: Unknown symbol rt2x00lib_resume
[ 11.292896] rt73usb: Unknown symbol rt2x00mac_add_interface
[ 11.293001] rt73usb: Unknown symbol rt2x00mac_get_stats
[ 11.293119] rt73usb: Unknown symbol rt2x00usb_disable_radio
[ 11.293177] rt73usb: Unknown symbol rt2x00usb_vendor_request_buff
[ 11.293257] rt73usb: Unknown symbol rt2x00usb_vendor_request_large_buff
[ 11.293314] rt73usb: Unknown symbol rt2x00usb_kick_tx_queue
[ 11.293371] rt73usb: Unknown symbol rt2x00usb_write_tx_data
[ 11.293428] rt73usb: Unknown symbol rt2x00mac_config_interface
[ 11.293485] rt73usb: Unknown symbol rt2x00mac_remove_interface
[ 11.293541] rt73usb: Unknown symbol rt2x00usb_vendor_request
[ 11.293598] rt73usb: Unknown symbol rt2x00usb_probe
[ 11.293680] rt73usb: Unknown symbol rt2x00mac_config
[ 11.293765] rt73usb: Unknown symbol rt2x00queue_get_queue
[ 11.293829] rt73usb: Unknown symbol rt2x00usb_suspend
[ 11.293886] rt73usb: Unknown symbol rt2x00usb_clear_entry
[ 11.293942] rt73usb: Unknown symbol rt2x00mac_conf_tx
[ 11.294004] rt73usb: Unknown symbol rt2x00mac_start
[ 11.294060] rt73usb: Unknown symbol rt2x00mac_stop
[ 11.294175] rt73usb: Unknown symbol rt2x00mac_configure_filter
[ 11.294232] rt73usb: Unknown symbol rt2x00usb_disconnect
[ 11.294313] rt73usb: Unknown symbol rt2x00mac_tx
[ 11.294389] rt73usb: Unknown symbol rt2x00usb_vendor_req_buff_lock
[ 11.294446] rt73usb: Unknown symbol rt2x00mac_get_tx_stats
[ 11.294522] rt73usb: Unknown symbol rt2x00usb_resume
[ 11.294622] rt73usb: Unknown symbol rt2x00usb_uninitialize
[ 11.294679] rt73usb: Unknown symbol rt2x00usb_initialize
[ 11.294746] rt73usb: Unknown symbol rt2x00mac_bss_info_changed

The led light is turned on tough.

Revision history for this message
Ian Weisser (ian-weisser) wrote :

Marking 'Fix Released' for Ubuntu.
The original reporter's problem was resolved on 2008-11-10 by installing linux-backports-modules.

If that didn't work for you, then you likely have a different bug (different bugs can exhibit the same symptoms) and this report will not help you. Please check if another bug matches your symptoms more closely, or open a new bug once you have collected enough information to be useful.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

Revision history for this message
Georg Neis (gn) wrote :

As suggested I installed linux-backports-modules-2.6.27-9-generic, but like Ivo Jimenez I now get "unknown symbol" errors and have no network at all.

Revision history for this message
joshyg6 (josheg) wrote :
Download full text (15.2 KiB)

need to make sure your backports module is the same as your linux kernel
(uname -r)... could be the problem... ? dl using synaptic?

On Sun, Dec 7, 2008 at 5:08 PM, Georg Neis <email address hidden> wrote:

> As suggested I installed linux-backports-modules-2.6.27-9-generic, but
> like Ivo Jimenez I now get "unknown symbol" errors and have no network
> at all.
>
> --
> rt73usb intrepid 8.10 beta -- wireless connection periodically lost; must
> restart driver
> https://bugs.launchpad.net/bugs/283759
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The rt2x00 Project: New
> Status in Ubuntu: Fix Released
> Status in Fedora: Confirmed
> Status in Mandriva Linux: In Progress
>
> Bug description:
> I may have something.. So I blacklisted the recompiled/newly installed
> legacy rt73 drivers, and i went back to using the rt73usb included initially
> with intrepid. i was using the Internet as normal, and then it crapped out,
> and these are the tail logs..
>
> Quote:
> Oct 15 07:53:19 jupiter2 NetworkManager: <debug> [1224071599.522971]
> periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:3D:39:10:96
> (LODGER)
> Oct 15 07:55:13 jupiter2 NetworkManager: <debug> [1224071713.601943]
> periodic_update(): Roamed from BSSID 00:0F:3D:39:10:96 (LODGER) to (none)
> ((none))
> Oct 15 07:55:19 jupiter2 NetworkManager: <debug> [1224071719.605557]
> periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:3D:39:10:96
> (LODGER)
>
> ****** Connection seemed to crap out around this point!!!********
>
> Oct 15 08:00:01 jupiter2 /USR/SBIN/CRON[9353]: (root) CMD ([ -x
> /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
> Oct 15 08:03:26 jupiter2 kernel: [ 4474.961767] usb 8-5.2: reset high speed
> USB device using ehci_hcd and address 4
> Oct 15 08:10:01 jupiter2 /USR/SBIN/CRON[9577]: (root) CMD ([ -x
> /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
> Oct 15 08:17:01 jupiter2 /USR/SBIN/CRON[9828]: (root) CMD ( cd / &&
> run-parts --report /etc/cron.hourly)
> Oct 15 08:20:01 jupiter2 /USR/SBIN/CRON[10010]: (root) CMD ([ -x
> /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528260] phy0 ->
> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the
> non-full queue 2.
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528262] Please file bug report to
> http://rt2x00.serialmonkey.com.
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528340] phy0 ->
> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the
> non-full queue 2.
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528341] Please file bug report to
> http://rt2x00.serialmonkey.com.
>
> ****** At this point here, I sudo ifconfig wlan0 down. Then I sudo modprobe
> -r rt73usb. Then I sudo modprobe rt73usb. Then I sudo ifconfig wlan0 up.
> Then I reselect the proper network from the NetworkManager drop down, and
> then it connects and I have internet again! ****************
>
>
> Oct 15 08:28:48 jupiter2 avahi-daemon[5359]: Interface wlan0.IPv4 no longer
> relevant for mDNS.
> Oct 15 08:28:48 jupiter2 avahi-daemon[5359]: Leaving mDNS multicast group
> on interface wlan0.IP...

Revision history for this message
Ivo Jimenez (ivotron) wrote :

Following IanW comments, I've created a new bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/306087

Cheers

Revision history for this message
Georg Neis (gn) wrote :

On Sun, Dec 7, 2008 at 11:59 PM, joshyg6 <email address hidden> wrote:
> need to make sure your backports module is the same as your linux kernel
> (uname -r)... could be the problem... ? dl using synaptic?

I'm running 2.6.27-9-generic, so that should be fine.

Revision history for this message
Stuart Bishop (stub) wrote :

Unknown symbol problems here with both 2.6.27-9 and 2.6.27-10. D-Link DWA-110 rt73 based USB stick, as per Bug #258985

Revision history for this message
Stuart Bishop (stub) wrote :

joshyg6 - Any other thoughts on how you managed to use the -backports module? Many of us see nothing but unknown symbol errors (Bug #306087).

I'm running 64 bit - could that make a difference?

Revision history for this message
Owen Tuz (owentuz) wrote :

Backports solved this problem for me but I'm on a new laptop which had some unrelated wireless issues (damn Atheros drivers) and thought this might be helpful?

http://wireless.kernel.org/en/users/Download#DownloadlatestLinuxwirelessdrivers

Hope it helps in some way.

Revision history for this message
joshyg6 (josheg) wrote :
Download full text (15.2 KiB)

yeah, 64 b could be the diff. i am on 32 b ubuntu.

On Sat, Dec 20, 2008 at 11:01 PM, Stuart Bishop <<email address hidden>
> wrote:

> joshyg6 - Any other thoughts on how you managed to use the -backports
> module? Many of us see nothing but unknown symbol errors (Bug #306087).
>
> I'm running 64 bit - could that make a difference?
>
> --
> rt73usb intrepid 8.10 beta -- wireless connection periodically lost; must
> restart driver
> https://bugs.launchpad.net/bugs/283759
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The rt2x00 Project: New
> Status in Ubuntu: Fix Released
> Status in Fedora: Confirmed
> Status in Mandriva Linux: In Progress
>
> Bug description:
> I may have something.. So I blacklisted the recompiled/newly installed
> legacy rt73 drivers, and i went back to using the rt73usb included initially
> with intrepid. i was using the Internet as normal, and then it crapped out,
> and these are the tail logs..
>
> Quote:
> Oct 15 07:53:19 jupiter2 NetworkManager: <debug> [1224071599.522971]
> periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:3D:39:10:96
> (LODGER)
> Oct 15 07:55:13 jupiter2 NetworkManager: <debug> [1224071713.601943]
> periodic_update(): Roamed from BSSID 00:0F:3D:39:10:96 (LODGER) to (none)
> ((none))
> Oct 15 07:55:19 jupiter2 NetworkManager: <debug> [1224071719.605557]
> periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:3D:39:10:96
> (LODGER)
>
> ****** Connection seemed to crap out around this point!!!********
>
> Oct 15 08:00:01 jupiter2 /USR/SBIN/CRON[9353]: (root) CMD ([ -x
> /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
> Oct 15 08:03:26 jupiter2 kernel: [ 4474.961767] usb 8-5.2: reset high speed
> USB device using ehci_hcd and address 4
> Oct 15 08:10:01 jupiter2 /USR/SBIN/CRON[9577]: (root) CMD ([ -x
> /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
> Oct 15 08:17:01 jupiter2 /USR/SBIN/CRON[9828]: (root) CMD ( cd / &&
> run-parts --report /etc/cron.hourly)
> Oct 15 08:20:01 jupiter2 /USR/SBIN/CRON[10010]: (root) CMD ([ -x
> /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528260] phy0 ->
> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the
> non-full queue 2.
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528262] Please file bug report to
> http://rt2x00.serialmonkey.com.
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528340] phy0 ->
> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the
> non-full queue 2.
> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528341] Please file bug report to
> http://rt2x00.serialmonkey.com.
>
> ****** At this point here, I sudo ifconfig wlan0 down. Then I sudo modprobe
> -r rt73usb. Then I sudo modprobe rt73usb. Then I sudo ifconfig wlan0 up.
> Then I reselect the proper network from the NetworkManager drop down, and
> then it connects and I have internet again! ****************
>
>
> Oct 15 08:28:48 jupiter2 avahi-daemon[5359]: Interface wlan0.IPv4 no longer
> relevant for mDNS.
> Oct 15 08:28:48 jupiter2 avahi-daemon[5359]: Leaving mDNS multicast group
> on interface wlan0.IPv4 with address 1...

Revision history for this message
joshyg6 (josheg) wrote :
Download full text (15.9 KiB)

p.s. i was working initially with some thinking from this forum:
http://rt2x00.serialmonkey.com/phpBB/search.php?keywords=backports&terms=all&author=&sc=1&sf=all&sk=t&sd=d&sr=posts&st=0&ch=300&t=0&submit=Search
read through the forums. one of the lead dev guys comments well.

On Sun, Dec 21, 2008 at 9:24 AM, <email address hidden> <email address hidden>wrote:

> yeah, 64 b could be the diff. i am on 32 b ubuntu.
>
> On Sat, Dec 20, 2008 at 11:01 PM, Stuart Bishop <
> <email address hidden>> wrote:
>
>> joshyg6 - Any other thoughts on how you managed to use the -backports
>> module? Many of us see nothing but unknown symbol errors (Bug #306087).
>>
>> I'm running 64 bit - could that make a difference?
>>
>> --
>> rt73usb intrepid 8.10 beta -- wireless connection periodically lost; must
>> restart driver
>> https://bugs.launchpad.net/bugs/283759
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>> Status in The rt2x00 Project: New
>> Status in Ubuntu: Fix Released
>> Status in Fedora: Confirmed
>> Status in Mandriva Linux: In Progress
>>
>> Bug description:
>> I may have something.. So I blacklisted the recompiled/newly installed
>> legacy rt73 drivers, and i went back to using the rt73usb included initially
>> with intrepid. i was using the Internet as normal, and then it crapped out,
>> and these are the tail logs..
>>
>> Quote:
>> Oct 15 07:53:19 jupiter2 NetworkManager: <debug> [1224071599.522971]
>> periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:3D:39:10:96
>> (LODGER)
>> Oct 15 07:55:13 jupiter2 NetworkManager: <debug> [1224071713.601943]
>> periodic_update(): Roamed from BSSID 00:0F:3D:39:10:96 (LODGER) to (none)
>> ((none))
>> Oct 15 07:55:19 jupiter2 NetworkManager: <debug> [1224071719.605557]
>> periodic_update(): Roamed from BSSID (none) ((none)) to 00:0F:3D:39:10:96
>> (LODGER)
>>
>> ****** Connection seemed to crap out around this point!!!********
>>
>> Oct 15 08:00:01 jupiter2 /USR/SBIN/CRON[9353]: (root) CMD ([ -x
>> /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
>> Oct 15 08:03:26 jupiter2 kernel: [ 4474.961767] usb 8-5.2: reset high
>> speed USB device using ehci_hcd and address 4
>> Oct 15 08:10:01 jupiter2 /USR/SBIN/CRON[9577]: (root) CMD ([ -x
>> /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
>> Oct 15 08:17:01 jupiter2 /USR/SBIN/CRON[9828]: (root) CMD ( cd / &&
>> run-parts --report /etc/cron.hourly)
>> Oct 15 08:20:01 jupiter2 /USR/SBIN/CRON[10010]: (root) CMD ([ -x
>> /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
>> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528260] phy0 ->
>> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the
>> non-full queue 2.
>> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528262] Please file bug report to
>> http://rt2x00.serialmonkey.com.
>> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528340] phy0 ->
>> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the
>> non-full queue 2.
>> Oct 15 08:22:12 jupiter2 kernel: [ 5601.528341] Please file bug report to
>> http://rt2x00.serialmonkey.com.
>>
>> ****** At this point here, I sudo ifconfig wlan0 down. Then I sudo
>> modprobe -r rt...

Revision history for this message
Stuart Bishop (stub) wrote :

On Sun, Dec 21, 2008 at 5:23 PM, Owen Tuz wrote:
> Backports solved this problem for me but I'm on a new laptop which had
> some unrelated wireless issues (damn Atheros drivers) and thought this
> might be helpful?
>
> http://wireless.kernel.org/en/users/Download#DownloadlatestLinuxwirelessdrivers
>
> Hope it helps in some way.

It does help. The installation procedure works smoothly as documented
and I've had no dropouts after an hour of heavy usage. This is the
21-12-2008 download with the 2.6.27-11 kernel and a D-Link DWA-110
usb stick (rt73 chipset). It all Just Works, even Network Manager.

Revision history for this message
Arton Pereira Dorneles (artondorneles) wrote :

This solution: http://wireless.kernel.org/en/users/Download#DownloadlatestLinuxwirelessdrivers work greats in ubuntu 8.10. Thanks!

Revision history for this message
Stuart Bishop (stub) wrote :

I was having no dropouts but signal strength seemed low with compat-wireless-2008-12-21. I just upgraded to compat-wireless-2009-01-10 and my signal strength is back to 100%.

Revision history for this message
Stuart Bishop (stub) wrote :

(Single strength might be due to the newer 2.6.27-11.11 kernel in proposed too, likely since the changelog for compat-wireless doesn't show anything interesting)

Revision history for this message
Ivo Jimenez (ivotron) wrote :

Hi,

I couldn't test the latest drivers and test them (lack of time), but on the most recent update my wireless card started to work correctly. I, however, had to remove the network-manager and configure it manually in /etc/network/interfaces.

Cheers!!

No more cables for me, thanks to the Open Source community

Revision history for this message
Ivo Jimenez (ivotron) wrote :

Forgot to mention, the kernel version that includes the working driver version is linux-image-2.6.27-11-generic

Revision history for this message
Ivo Jimenez (ivotron) wrote :

Not!!

My connection kept going down (approx. every 2 hours). I haven't realize how easy it's to add the drivers on http://wireless.kernel.org/ so I gave it a try and everything is working nicely!!

Thanks much

Revision history for this message
Peter Hoeg (peterhoeg) wrote :

I am running on a 64-bit kernel and was experiencing the "error -19" error when using the stock .27-11 kernel as well as the same symbol errors as reported earlier by others when trying the backported modules.

I couldn't use the wireless.kernel.org drivers either (segfault), but the custom kernel done by Ubuntu's Andy Whitcroft and available from his PPA finally did the trick for me:

http://people.ubuntu.com/~apw/lp258985-intrepid/

It's finally working. Thanks Andy!

Revision history for this message
Andy Whitcroft (apw) wrote :

@Peter -- it is more likley you have recieved an updated backports driver, we did have one upload which somehow was dammaged. It was re-uploaded as a result and is now whole again so the symbols errors may well have gone away as a result of that.

Revision history for this message
Peter Hoeg (peterhoeg) wrote :

@Andy. Hmmm... This is getting rather odd. I spoke too soon earlier but it took a lot longer to trigger the error this time around.

I then bit the apple and downloaded the latest jaunty alternate install cd and upgraded to jaunty. Same problem...

The connecting keeps dropping and my log is full of "error -19" messages. Restarting and/or unloading/loading the rt73usb works like one out of 10 - the machine needs to be physically powered off before it works again.

I'm willing to try anything you can throw my way in terms of sorting this one out.

/Peter

Revision history for this message
Andy Whitcroft (apw) wrote : Re: [Bug 283759] Re: rt73usb intrepid 8.10 beta -- wireless connection periodically lost; must restart driver

On Wed, Mar 25, 2009 at 02:22:42PM -0000, Peter Hoeg wrote:
> The connecting keeps dropping and my log is full of "error -19"
> messages. Restarting and/or unloading/loading the rt73usb works like one
> out of 10 - the machine needs to be physically powered off before it
> works again.

Could you paste in a section of the errors that you are seeing from
whichever releases you are seeing it on, perhaps include the whole dmesg
if that helps. Please indicate which release you are reporting against.

Revision history for this message
Peter Hoeg (peterhoeg) wrote :

OK, this is against jaunty with all packages updated as of 2009-03-26 and with l-b-m installed - keep in mind I was getting the same error on intrepid.

[ 162.075171] rt73usb 1-9:1.0: firmware: requesting rt73.bin
[ 162.169579] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 172.979832] wlan0: authenticate with AP ffff8800379e4aa0
[ 172.982964] wlan0: authenticated
[ 172.982967] wlan0: associate with AP ffff8800379e4aa0
[ 172.985595] wlan0: RX AssocResp from ffff88012d84c03e (capab=0x411 status=0 aid=1)
[ 172.985598] wlan0: associated
[ 172.998106] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 183.440011] wlan0: no IPv6 routers present
[ 399.397583] usb 1-9: USB disconnect, address 10
[ 399.400427] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3040 with error -19.
[ 399.400515] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3040 with error -19.
[ 399.400601] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3028 with error -19.
[ 399.400687] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3064 with error -19.
[ 399.400772] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0c failed for offset 0x0000 with error -19.
[ 399.400863] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
[ 399.401019] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
[ 399.401125] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
[ 399.401232] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
[ 399.412044] wlan0: deauthenticating by local choice (reason=3)

This is then following later by lots of:
[ 536.908015] wlan0: direct probe to AP ffff88012d84eaa0 try 1
[ 536.910249] wlan0 direct probe responded
[ 536.910252] wlan0: authenticate with AP ffff88012d84eaa0
[ 536.911995] wlan0: authenticated
[ 536.911997] wlan0: associate with AP ffff88012d84eaa0
[ 536.914625] wlan0: RX ReassocResp from ffff8800ca5cb03e (capab=0x411 status=0 aid=1)
[ 536.914627] wlan0: associated
[ 541.943211] wlan0: deauthenticated (Reason: 16)
[ 542.940015] wlan0: direct probe to AP ffff88012d84eaa0 try 1
[ 542.942460] wlan0 direct probe responded
[ 542.942463] wlan0: authenticate with AP ffff88012d84eaa0
[ 542.944309] wlan0: authenticated
[ 542.944311] wlan0: associate with AP ffff88012d84eaa0
[ 542.946833] wlan0: RX ReassocResp from ffff8800ca5cc03e (capab=0x411 status=0 aid=1)
[ 542.946835] wlan0: associated
[ 547.974415] wlan0: deauthenticated (Reason: 16)
[ 548.972010] wlan0: direct probe to AP ffff88012d84eaa0 try 1

I have attached the complete log. Let me know what you want me to try out.

Revision history for this message
Peter Hoeg (peterhoeg) wrote :

lsusb

Just fyi, the wifi card is built in, so I can't really unplug it to test.

Revision history for this message
Peter Hoeg (peterhoeg) wrote :

lspci

Revision history for this message
Peter Hoeg (peterhoeg) wrote :
Download full text (5.0 KiB)

Today I also had an oops thrown in for good measure after having used the system just fine for a number of hours.

Mar 26 20:42:13 dolores kernel: [16405.704602] ------------[ cut here ]------------
Mar 26 20:42:13 dolores kernel: [16405.704605] WARNING: at /build/buildd/linux-2.6.28/fs/sysfs/group.c:138 sysfs_remove_group+0xd9/0xe0()
Mar 26 20:42:13 dolores kernel: [16405.704608] sysfs group ffffffff80904c80 not found for kobject 'wlan0'
Mar 26 20:42:13 dolores kernel: [16405.704610] Modules linked in: binfmt_misc ppdev bnep vboxnetflt vboxdrv bridge stp kvm_intel kvm video output xfs dm_crypt vhba coretemp it87 hwmon_vid sbp2 lp parport arc4 ecb snd_hda_intel tda18271 snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi tda8290 snd_seq_midi_event snd_seq tda10048 snd_timer rt73usb crc_itu_t snd_seq_device rt2x00usb rt2x00lib led_class input_polldev cx23885 snd lbm_cw_mac80211 cx2341x videobuf_dma_sg soundcore snd_page_alloc nvidia(P) serio_raw lirc_mceusb2 lbm_cw_cfg80211 lirc_dev videobuf_dvb dvb_core videobuf_core v4l2_common videodev v4l1_compat v4l2_compat_ioctl32 btcx_risc tveeprom usbhid usb_storage forcedeth ohci1394 ieee1394 fbcon tileblit font bitblit softcursor
Mar 26 20:42:13 dolores kernel: [16405.704677] Pid: 41, comm: khubd Tainted: P 2.6.28-11-generic #37-Ubuntu
Mar 26 20:42:13 dolores kernel: [16405.704679] Call Trace:
Mar 26 20:42:13 dolores kernel: [16405.704685] [<ffffffff80250927>] warn_slowpath+0xb7/0xf0
Mar 26 20:42:13 dolores kernel: [16405.704689] [<ffffffff802e26fc>] ? __slab_free+0xac/0x110
Mar 26 20:42:13 dolores kernel: [16405.704694] [<ffffffff802fdc6c>] ? ifind_fast+0x9c/0xa0
Mar 26 20:42:13 dolores kernel: [16405.704697] [<ffffffff802fdca6>] ? ilookup+0x36/0x50
Mar 26 20:42:13 dolores kernel: [16405.704701] [<ffffffff80348ca1>] ? release_sysfs_dirent+0x61/0xe0
Mar 26 20:42:13 dolores kernel: [16405.704704] [<ffffffff803483dd>] ? sysfs_find_dirent+0x2d/0x40
Mar 26 20:42:13 dolores kernel: [16405.704707] [<ffffffff80349fe9>] sysfs_remove_group+0xd9/0xe0
Mar 26 20:42:13 dolores kernel: [16405.704713] [<ffffffff804b7578>] device_remove_attrs+0x48/0xe0
Mar 26 20:42:13 dolores kernel: [16405.704717] [<ffffffff804b7710>] device_del+0x100/0x1d0
Mar 26 20:42:13 dolores kernel: [16405.704722] [<ffffffff805c4957>] netdev_unregister_kobject+0x27/0x30
Mar 26 20:42:13 dolores kernel: [16405.704726] [<ffffffff805b51d6>] rollback_registered+0xa6/0x130
Mar 26 20:42:13 dolores kernel: [16405.704729] [<ffffffff805b527d>] unregister_netdevice+0x1d/0x70
Mar 26 20:42:13 dolores kernel: [16405.704747] [<ffffffffa0923dfc>] ieee80211_remove_interfaces+0x7c/0xb0 [lbm_cw_mac80211]
Mar 26 20:42:13 dolores kernel: [16405.704762] [<ffffffffa09170d1>] lbm_cw_ieee80211_unregister_hw+0x31/0xf0 [lbm_cw_mac80211]
Mar 26 20:42:13 dolores kernel: [16405.704770] [<ffffffffa09995a9>] rt2x00lib_remove_hw+0x89/0xa0 [rt2x00lib]
Mar 26 20:42:13 dolores kernel: [16405.704776] [<ffffffffa0999600>] rt2x00lib_remove_dev+0x40/0x60 [rt2x00lib]
Mar 26 20:42:13 dolores kernel: [16405.704783] [<ffffffffa09a60ea>] rt2x00usb_disconnect+0x2a/0x70 [rt2x00usb]
Mar 26 20:42:13 dolores kernel: [16405.704788] ...

Read more...

Revision history for this message
Peter Hoeg (peterhoeg) wrote :

Problem still persists in latest intrepid/jaunty, hence not fixed.

Revision history for this message
Peter Hoeg (peterhoeg) wrote :

I've just tried with a self-compiled version from linuxwireless.org with the same outcome. Funny thing is, that this seems to be a recurring problem for ages. Look at this bug report: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/86980 which is over 2 years old.

Could it have anything to do with that 'USB disconnect' message showing - the card is built-in so it obviously isn't being jerked out, but for some reason a disconnect is being registered and maybe the driver just doesn't handle that very gracefully.

I have usb autosuspend deactivated so that's not it.

Revision history for this message
Peter Hoeg (peterhoeg) wrote :

Did a little more investigating into this - error -19 is 'ENODEV' or 'No such device' so obviously the problem is that the device is being pulled away, the driver noticing it (hence the error -19) and then not handling it properly.

@Andy - any ideas as to what we can try to find out how come the device is being disconnected?

As I see it, there are two problems:

a) The device disappears for unknown reasons, and
b) The driver bombs when trying to deal with that situation

The 2 are actually unrelated in the sense that fixing either of them would (theoretically) solve the problem although the right thing is obviously to fix both.

Bug Watch Updater (bug-watch-updater)
Changed in mandriva:
status: In Progress → Invalid
Bug Watch Updater (bug-watch-updater)
Changed in fedora:
status: Confirmed → Invalid
Revision history for this message
papukaija (papukaija) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

affects: ubuntu → rt73 (Ubuntu)
Changed in rt73 (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
papukaija (papukaija) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
papukaija (papukaija) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in rt2x00:
status: New → Invalid
Changed in rt73 (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
papukaija (papukaija) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 258985, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.