usb wireless device zd1211rw 5-2:1.0: zd_chip_control_leds error -19

[amichair]

I'm using a Zydas based usb wireless device on Kubuntu Edgy. It works well. However, after a random period of time (between minutes and hours, more than once a day) the network simply dies. running lsusb (or kcontrol -> usb devices) hangs, unplugging/replugging the USB device has no effect, and it seems as though the USB bus is dead. The only way to get it working again is a reboot - several time a day!

I'm not sure what info may be relevant, so here's a guess (I'm a newbie, which unfortunately had to tinker with these things while trying to find a solution):

It's the only connected USB device.

The system log, at the point where it gets stuck, shows:
"usb 5-2: USB disconnect, address 2"
and after that a whole lot of:
"zd1211rw 5-2:1.0: error ioread32(CR_REG1): -19"

$ uname -a
Linux myhost 2.6.17-10-generic #2 SMP Fri Oct 13 18:45:35 UTC 2006 i686 GNU/Linux

$ lsmod | grep usb
usbcore 134912 4 zd1211rw,ehci_hcd,uhci_hcd

$ lspci | grep USB
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)

[Brian Murray (brian-murray)]

Thanks for your bug report. Could you please add the full output of 'lsusb' and 'dmesg' to your bug report as attachments? Thanks in advance.

[amichair (amichai2)]

As I mentioned in the report, lsusb had no output - it simply hung. As for dmesg I also mentioned the only lines from syslog that looked like they might have something to do with it. Since the system was practically unusable in that state, I moved things around to use a wired connection on this computer, but if there's anything else in particular you'd like me to look for, I can try to recreate it once again with the wireless connection.

[Brian Murray (brian-murray)]

I believe the kernel team will want the full output of 'dmesg' to be able to better troubleshoot your issue and see the context of the error messages you reported. Please try to get that output. Thanks in advance.

[Brian Murray (brian-murray)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.

[amichair (amichai2)]

I've installed Feisty Beta (clean installation) on the same machine, and connected via KNetworkManager as before. The connection was working well. I came back a few hours later, and encountered the same old problem - no network, KNetworkManager hung when I tried to reconnect, lsusb hung as well, etc. and even system shutdown got stuck. A hard reboot brought the system back to normal. I've attached the dmesg output. If there's anything other info that can help, I'd be happy to provide it...

[Tim Gardner (timg-tpi)]

Try a more current driver by blacklisting zd1211rw:

edit /etc/modprobe.d/blacklist and add zd1211rw
edit /etc/modules and add zd1211rw-mac80211

Either reboot or 'modprobe zd1211rw-mac80211', then insert the zd1211.

[sakrofag (sakrofag)]

I have the same problem to. I'v also upgradet to fiesty. I tested doing as you told but it doesn't work for me.

[Mark Anderson (manderson23)]

I also see this bug in Feisty. I have attached the dmesg output. The device is a Belkin Wireless G FD7050UK v4000.

[romu (rboudot)]

I also see this bug in Feisty.

The device is a Sagem USB dongle plugged in a USB hub. It hangs randomly after minutes or hours.
Interestingly when rebooting in windows after a crash the dongle remains crashed, so it seems it is hardlocked

I can see lots of this message in syslog :

May 21 10:43:39 laborieux kernel: [ 9573.676098] zd1211rw 4-4.3:1.0: zd_chip_control_leds error -19

dmesg, lsusb -vvv attached

Please feel free to ask for further data points ; I could enable debug in the driver if needed.

[Andreas Gnau (rondom)]

Well, I can confirm this. At first I thought this was related to the room temperature (overheat), but from now, I can't confirm this. It occurs pretty randomly.

[Andreas Gnau (rondom)]

I meant I _can_ confirm the problem described here. What I _can't_ confirm is that it is related to the temperature.

[BobMcD (mcbobbo)]

Disclaimer: This could be COMPLETELY UNRELATED, but...

I solved this same persistant problem on my system (Feisty 2.6.20-16) by using the instructions at this link:

http://www.vmware.com/community/message.jspa?messageID=575305#575305

Specifically:

<quote>
Found this information from another post in the Ubuntu Linux forums, maybe it is relevant in other linux ditros...

USB Devices Are Not Available on Some Linux hosts, the VM > Removable Devices > USB Devices Menu Is Empty

In short, the problem was Ubuntu not mounting USBFS to /proc/bus/usb.

Solution:
sudo mount -t usbfs none /proc/bus/usb

and add the following line in the /etc/fstab file:
usbfs /proc/bus/usb usbfs auto 0 0
</quote>

[Tom (tompijls)]

BobMcD,

this put me in the right direction as well:

For me wireless worked sometimes, sometimes not.
Thanks to your post, found out that the times it worked, I had attached an external USB drive (which i assume triggered the mount usbfs), and when it didn't work, no drive was attached.

When it didn't work, it was able to see the wireless networks, and was able to connect, but never received an IP.

[romu (rboudot)]

Well I think we have 2 unrelated issues :

1/ the usbfs not mounted, which prevents the device from working _from the beginning_
 2/the random crash : device begins to operate, receive an IP address, user is able to browse etc then suddendly everything stops with the led messages in the syslog

On the host where I encounter the 2nd issue usbfs is mounted (though line in /etc/fstab, I think it is mounted by hotplug) and I _think_ other peripherals are attached to the bus so issue 1 doesn't trigger

[Aitese (tes-odigie)]

I am using a Belkin Wireless G FD7050UK v4000 on Ubuntu Feisty (2.6.20-16) and have solved this using Tim Gardner's advice above, although I am now restricted to WEP security as WPA is not supported by the zd1211rw-mac80211 driver.

[Iron Bishop (ironbishop)]

Same situation and same error message here, I'm using Debian Etch (with kernel 2.6.21.5) and Ubuntu Feisty (repository kernel). I will post dmesg / lsusb when the problem occur next time.

[Iron Bishop (ironbishop)]

another dmesg

[Chuck Short (zulcss)]

Does this still affect you under gutsy?

Thanks
chuck

[cmpn76 (cmpn76)]

Hi,
I have the same bug under gutsy.
The strange think is that I noticed that after I bought a usb keyboard and connected it.
Before I remember that sometime the network stop to work but it was not so frequent.

At the moment I have the following devices connected via usb

marco@marco-desktop:~$ lsusb
Bus 004 Device 006: ID 05ac:0221 Apple Computer, Inc.
Bus 004 Device 004: ID 0586:3410 ZyXEL Communications Corp.
Bus 004 Device 002: ID 05ac:1006 Apple Computer, Inc.
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 002: ID 0a5c:200a Broadcom Corp.
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 04b3:310b IBM Corp. Red Wheel Mouse
Bus 001 Device 001: ID 0000:0000

The error in my case is this:

Nov 24 23:13:06 marco-desktop kernel: [ 8561.165840] usb 4-1: USB disconnect, address 2
Nov 24 23:13:07 marco-desktop kernel: [ 8561.165850] usb 4-1.2: USB disconnect, address 6
Nov 24 23:13:07 marco-desktop kernel: [ 8561.435521] usb 4-1: new high speed USB device using ehci_hcd and address 7
Nov 24 23:13:08 marco-desktop kernel: [ 8562.303008] zd1211rw 4-4:1.0: zd_chip_control_leds error -110
Nov 24 23:13:10 marco-desktop kernel: [ 8564.301648] zd1211rw 4-4:1.0: zd_chip_control_leds error -110
Nov 24 23:13:12 marco-desktop kernel: [ 8566.300300] zd1211rw 4-4:1.0: zd_chip_control_leds error -110

[dmatt (martind)]

Hi,

I have same bug happening randomly under gutsy with my usb wifi dongle running on HP NX9010. It took quite a long time today to occur ...

 uname -a
Linux harvlin 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

 lsusb (before problem)
Bus 003 Device 003: ID 07b8:6001 D-Link Corp.
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 002: ID 0f62:1001 Acrox Technologies Co., Ltd
Bus 001 Device 001: ID 0000:0000

 lsusb (after problem occurs)
hangs - does not return anything and couldn't be stopped with CTRL-C

 /var/log/messages relevant part
Dec 8 23:13:57 harvlin -- MARK --
Dec 8 23:24:37 harvlin kernel: [22285.256000] usb 1-4: USB disconnect, address 3

 lsmod | grep usb
usbhid 29536 0
hid 28928 1 usbhid
usbcore 138632 5 zd1211rw,usbhid,uhci_hcd,ehci_hcd

 lspci | grep USB
00:0b.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 50)
00:0b.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 50)
00:0b.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51)

When I try shutdown, it freezes as well (I think the last action listed is attempt to stop some network deamon).

I used to have much bigger problems with this dongle when gutsy came but it was solved when I stopped using extending usb cable and connected it directly to notebook.

[Darryl McGinnis (darrylmcginnis)]

I have the same problem with a Belkin Wireless G USB Network Adapter. I am running Gutsy.
Initially I had the problem (Wireless works for a while, but quits randomly requiring a reboot to connect again) with a Airlink 802.11g Wireless LAN PCI Card. Without much troubleshooting at that point, I pulled the card out and began using the Belkin USB dongle. It had the same issue so I began looking for answers...

lsusb (before problem strikes):
Bus 001 Device 006: ID 050d:705c Belkin Components
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc.
Bus 001 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 003 Device 008: ID 062a:0001 Creative Labs Notebook Optical Mouse
Bus 003 Device 001: ID 0000:0000

lsusb after problem strikes results in the terminal freezing.

lspci | grep USB
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)

lsmod | grep usb
usbhid 29536 0
hid 28928 1 usbhid
usbcore 138632 5 ehci_hcd,zd1211rw,usbhid,uhci_hcd

I have attached the result of dmesg after the problem occurs in dmesg_after.txt

Additional information:
My mouse is connected via USB and it continues to function normally.
However, after the problem occurs the system does not recognize any USB flash drive being plugged in. (I have never had one already plugged in at the time the wireless quits, so I don't know whether it remains function or if it quits as well.)
After the problem occurs, restarting the computer ENDS with a message stating that the system Will Restart - but doesn't. Requires Ctrl-Alt-Delete or Reset button.
Attempting to reset the USB with the following command:
sudo modprobe -r -v ehci_hcd && sudo modprobe -v ehci_hcd
displays the removal, but not the insert. I've never attempted to run the commands individually, so honestly I don't know whether the first command truly completes normally...
...and finally: Eventually enough dinking around with it results in sudo anything freezing (unable to ctrl-c).

Let me know if any other information would be helpful.

[dmatt (martind)]

I noticed khubd deamon always changes state to "D" after problem occurs, Under normal circumstances it is in "S"(leep) state.

 ps -aux

  PID TTY STAT TIME COMMAND
  2003 ? D< 0:00 [khubd]

This way I easily distinguish between temporary problem with my provider and the bug.

[Nick Davis (argoneus)]

i noticed similar behavior under ubuntu 7.10 with a belkin wireless USB device. Specifically, my wireless networking stops working and network manager becomes unresponsive when I unplug the device and plug it back in. A proper system restart or shutdown also freezes the computer when it reaches the point where the network services are being terminated (I have to it the power button to manually shut down). Here's some output from various system resources that may be helpful:

uname -a:
Linux durden 2.6.22-14-generic #1 SMP Tue Dec 18 05:28:27 UTC 2007 x86_64 GNU/Linux

lsusb:
Bus 005 Device 002: ID 050d:705c Belkin Components
Bus 005 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 004: ID 046d:c512 Logitech, Inc.
Bus 001 Device 001: ID 0000:0000

lsmod | grep usb:
usbhid 32576 0
hid 33408 1 usbhid
usbcore 161584 5 zd1211rw,usbhid,ehci_hcd,uhci_hcd

in /var/log/syslog these lines are repeated several times:
Dec 24 00:32:50 durden kernel: [ 5723.676241] zd1211rw 5-1:1.0: zd_chip_control_leds error -19
Dec 24 00:32:50 durden kernel: [ 5724.296166] zd1211rw 5-1:1.0: error ioread32(CR_REG1): -19

Please let me know if there's any other info I can provide that would help. Thanks.

[Nick Davis (argoneus)]

a slight clarification of my comment above: the USB device stops working randomly on its own, and at that point i try to remedy the situation by unplugging the device/plugging back in. i'm not unplugging it haphazardly for giggles trying to test its robustness (which is the way my earlier post could be construed) :-)

[Kevin Pinto (kevin-pinto)]

I have a similar problem with Gutsy's kernel. I have a USB Brother MFC printer/scanner and an external USB hard drive that used to work flawlessly in Edgy with uptimes of months on end.

Now I see that the entire USB subsystem seems to hang at some point. All USB peripherals thereafter have some problems. For instance, the UPS which is also connected by USB loses communication

uname -a:
Linux kpas1 2.6.22-14-generic #1 SMP Tue Dec 18 05:28:27 UTC 2007 x86_64 GNU/Linux

dmesg log is attached.

lsusb has hung so I cannot attach the log. I will reboot and attempt to attach it.

[Andreas Gnau (rondom)]

This sounds like a completely different bug. Please file a seperate bug for your problem.

[Kevin Pinto (kevin-pinto)]

More info:
lsmod | grep -i usb
usblp 16896 0
usbhid 32576 0
hid 33408 1 usbhid
usbcore 161584 7 rtl8187,xpad,usblp,usbhid,ehci_hcd,ohci_hcd

lspci | grep -i usb
00:0a.0 USB Controller: nVidia Corporation MCP55 USB Controller (rev a1)
00:0a.1 USB Controller: nVidia Corporation MCP55 USB Controller (rev a2)

I've attached the output of lsusb after a reboot. Before the reboot, lsusb just hung and could not be terminated even with Control + C

[Kevin Pinto (kevin-pinto)]

It seems that my problem is fairly close to the original poster who says:
...and it seems as though the USB bus is dead. The only way to get it working again is a reboot...

I would be happy to file a different bug report, but the problem seems related to the bus going dead, not the specific USB peripheral.

[jemand (ich-22)]

I've got the same problem here:

$ uname -a
Linux kiste 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux

$ lspci | grep -i usb
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)

$ lsusb
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 046d:c051 Logitech, Inc.
Bus 002 Device 002: ID 16c0:05dc
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 004 Device 002: ID 0ace:1211 ZyDAS 802.11b/g USB2 WiFi
Bus 004 Device 001: ID 0000:0000

When the wlan-stick stops working, the system slows down; opening a gnome-terminal takes about 10s.
Another thing is that the bus stops working partly, which means that this logitech mouse keeps working on, but other devices as for example a flash-memory-stick won't work.
With kernel 2.6.24 it isn't any better.

former dmesg (not fitting to the outputs above):
[ 650.880000] zd1211rw 5-1:1.0: zd_chip_control_leds error -110
[ 1801.884000] zd1211rw 5-1:1.0: zd_chip_control_leds error -110
[ 3266.644000] usb 5-1: USB disconnect, address 4
[ 3266.884000] zd1211rw 5-1:1.0: zd_chip_control_leds error -19
[ 3267.884000] zd1211rw 5-1:1.0: zd_chip_control_leds error -19 << repeated on and on

Searching for the cause of this bug, I read somewhere else that those via 1.1 hubs should be responsible for this bug. But I'm not shure about this as the stick is attachted to Bus 004 (lsusb) and according to lspci the controller of this bus is a usb 2.0 controller. So I'm very confused but hope to still have been able to help.

[Doug Mills (thunder-dude44)]

I'm also having this issue. I'm running Kubuntu 7.10. I switched to gnome after installing the OS though, and so now I have kubuntu with gnome installed. I have no idea if that matters in terms of this bug, but all kinds of things can be noteworthy with these bugs. I've got an AirLink 101 300N usb wireless card. The model number is AWLL6080. I've seen posts about how this card works with people who have ubuntu 7.10, so I know this card should work. I'll post my diagnostic outputs after I get them when I reboot into linux. I'm using Windows to post this due to the problem in linux. I've got the same problem as most of those who posted here: I have a wireless usb card that works and connects to networks and gives me access to the internet and then suddenly the card hangs and stops blinking. All of my usb ports are unresponsive except for things that don't require output (aka a usb hard drive) like a wireless usb mouse. As soon as I unplug anything that continues to work, due to only needing input, it won't work again in any port, even the one I just unplugged it from.

I'm wondering what could the cause of this bug be. It seems to range over a broad set of cards, with each of those cards having exact same symptoms. Some of these cards are claimed to work with linux and not have problems. Is it possible that the issue is due to a hardware problem as well as a software (kernel issue) one? Does our hardware all have something in common, such as similar usb hub makers or similar wireless card parts or both?

[jemand (ich-22)]

Good news to everyone:
I'm now using kernel 2.6.24-5-generic for 4 days and this bug did not occur anymore.
I got this kernel from the ubuntu hardy alpha repositorys.
Seems as if the kernel-team was successful. Thanks to them.

[dmatt (martind)]

The bug just manifested on my
Linux ******** 2.6.24-11-generic #1 SMP Fri Feb 29 22:08:31 UTC 2008 i686 GNU/Linux
It is not solved.

O remember having this problem for long time - probably from edgy through feisty, gutsy and now in heron from alpha 1 to last update few hours ago (alpha 6 I suppose).

I would suggest 2 things to all suffering from this bug:
1, do not use cable to connect your usb dongle, stick it right into usb. This way I reduced my wifi problems down to random freeze every few hours (similar to original bug text)
2, do not use power button, use ALT SYSRQ keyboard combination: http://fosswire.com/2007/09/08/fix-a-frozen-system-with-the-magic-sysrq-keys/

I suspect this bug could be the combination of hardware and software failure. First something goes wrong with dongle connection, which unregister it from the usb bus. Then zd1211rw (or kernel) does not handle this situation correctly. zd1211 continues to try reading from disconnected dongle and partly hangs the whole usb subsystem.

Is there a way to restart usb subsystem without restarting the whole computer?
What else could be done to investigate this?

Last suggestion (to use zd1211rw-mac80211 which I tested unsuccessfully) is almost year old. I would love to help to solve it, just give me some direction what to test.

[IlBaroneRampante (marciume)]

this dman usb key makes me mad.
i lost connection every 15 minutes or something like that.
i've got this error message

[ 3031.168000] usb 4-3: USB disconnect, address 3
[ 3031.896000] zd1211rw 4-3:1.0: zd_chip_control_leds error -19
[ 3032.896000] zd1211rw 4-3:1.0: zd_chip_control_leds error -19
[ 3033.896000] zd1211rw 4-3:1.0: zd_chip_control_leds error -19
[ 3034.896000] zd1211rw 4-3:1.0: zd_chip_control_leds error -19
[ 3035.896000] zd1211rw 4-3:1.0: zd_chip_control_leds error -19
[ 3036.896000] zd1211rw 4-3:1.0: zd_chip_control_leds error -19

can someone help me?

i've got ubuntu gutsy on acer aspire, amd athlon xp-m

[sheikki (sheikki2302)]

I've got a usb dongle from A-link

Mar 25 03:36:59 linux-1337 kernel: zd1211rw 4-7:1.0: zd_chip_control_leds error -110
Mar 25 03:37:12 linux-1337 syslog-ng[2249]: last message repeated 2 times
Mar 25 03:37:32 linux-1337 kernel: zd1211rw 4-7:1.0: zd_chip_control_leds error -110
Mar 25 03:38:12 linux-1337 syslog-ng[2249]: last message repeated 3 times
Mar 25 03:38:45 linux-1337 kernel: zd1211rw 4-7:1.0: zd_chip_control_leds error -110
Mar 25 03:38:45 linux-1337 kernel: zd1211rw 4-7:1.0: zd_chip_control_leds error -110
Mar 25 03:39:13 linux-1337 kernel: zd1211rw 4-7:1.0: zd_chip_control_leds error -110
Mar 25 03:40:18 linux-1337 kernel: zd1211rw 4-7:1.0: zd_chip_control_leds error -110
Mar 25 03:41:12 linux-1337 syslog-ng[2249]: last message repeated 5 times
Mar 25 03:41:33 linux-1337 kernel: zd1211rw 4-7:1.0: zd_chip_control_leds error -110
Mar 25 03:42:20 linux-1337 kernel: zd1211rw 4-7:1.0: zd_chip_control_leds error -110

I'm using openSUSE 10.3 with 2.6.22-17-0.1 Kernel. Perhaps not the right place to post this, but yeah this bug is inter-distro..

All was fine for perhaps 2 hours and then I mounted a usb hdd for the first time on this system and since then I've been getting this..

[coubi64 (frederic-valentin)]

My system seems to slow down (Hardy Heron):

[ 120.644068] SoftMAC: Open Authentication completed with 1a:c9:38:7b:3c:60
[ 121.353864] ieee80211_crypt: registered algorithm 'CCMP'
[ 121.764877] padlock: VIA PadLock not detected.
[ 123.260219] ieee80211_crypt: registered algorithm 'TKIP'
[ 124.801347] SoftMAC: Open Authentication completed with 1a:c9:38:7b:3c:60
[ 136.803633] SoftMAC: Open Authentication completed with 1a:c9:38:7b:3c:60
[ 137.498783] SoftMAC: Open Authentication completed with 1a:c9:38:7b:3c:60
[ 149.495099] SoftMAC: Open Authentication completed with 1a:c9:38:7b:3c:60
[ 164.476428] SoftMAC: Open Authentication completed with 1a:c9:38:7b:3c:60
[ 176.514438] SoftMAC: Open Authentication completed with 1a:c9:38:7b:3c:60
[ 194.528301] SoftMAC: Open Authentication completed with 1a:c9:38:7b:3c:60
[ 206.514947] SoftMAC: Open Authentication completed with 1a:c9:38:7b:3c:60
[ 210.888375] SoftMAC: Open Authentication completed with 1a:c9:38:7b:3c:60
[ 222.864929] SoftMAC: Open Authentication completed with 1a:c9:38:7b:3c:60
[ 253.973485] SoftMAC: Open Authentication completed with 1a:c9:38:7b:3c:60
[ 265.997366] SoftMAC: Open Authentication completed with 1a:c9:38:7b:3c:60
[ 266.731984] SoftMAC: Open Authentication completed with 1a:c9:38:7b:3c:60
[ 266.733494] SoftMAC: Open Authentication completed with 1a:c9:38:7b:3c:60
[ 1535.441869] zd1211rw 4-2:1.0: error ioread32(CR_REG1): -110

[maju (k-m-junkersdorf)]

I (Ubuntu 7.10 Gutsy) have the same problem with my wifi usb stick. After certain time it gets disconnected. This is the part of syslog:

Apr 16 19:11:51 Keller kernel: [ 3385.384817] usb 4-1: USB disconnect, address 2
Apr 16 19:11:51 Keller kernel: [ 3385.503758] zd1211rw 4-1:1.0: zd_chip_control_leds error -19
Apr 16 19:11:52 Keller kernel: [ 3386.502122] zd1211rw 4-1:1.0: zd_chip_control_leds error -19
Apr 16 19:11:53 Keller kernel: [ 3387.500516] zd1211rw 4-1:1.0: zd_chip_control_leds error -19

[Ricardo Velhote (rvelhote)]

Same problem here. All USB devices just disconnect randomly. Same messages as above.

For now, I've managed to get the USB devices up with

sudo modprobe ehci_hcd

When the USB goes down I just run that command in the terminal. There is no difference if you run sudo modprobe ehci_hcd or sudo rmmod ehci_hcd. Everything comes back up again.

-------------------
Linux ric-desktop 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux
Ubuntu 8.04

[Ricardo Velhote (rvelhote)]

After some more testing I've come to the conclusion that sudo modprobe/rmmod ehci_hcd doesn't always work. :( It worked a few times but it's not consistent.

Another thing I'd like to ask to everyone that has this problem is if you have the usbkbd module loaded. My USB Wifi has been running for 4 hours now without crashing since I disabled it.

This module is blacklisted in 8.04 but I need it because my keyboard doesn't work very well connected to the PS/2 port. (using a USB to PS/2 converter).

[Archie (aavaliani)]

I have Ubuntu 8.04. I have the similar problem. But for me it only happens when my router changes the IP every 48 hours. The network is showing on the icon that it tries to reconnect, it also finds my router, but the reconnection process never finishes. Even if I disable and enable networking, or unplug and plugin my USB Wlan, I don't get any reconnection. Only the restart helps. Any ideas?

Archie

[SnowTDM (eortega)]

Hello everybody,

I have an USB wireless card with chip Zydas 1211rw using module zd1211rw. It used to run perfectly in Ubuntu 7.10, but I've upgraded to 8.04 and it doesn't connect or show any wireless network. It also doesn't connect booting with desktop CD or upgrading from 7.10 to 8.04 without any CD.

But if I start 8.04 version with 7.10 kernel (2.6.22) card connects perfectly, including with WAP encryption. It also connect if I boot with 7.10 desktop CD.

I think it is a problem with driver or module zd1211rw in conjunction with new kernel.

I attach some log of the 2.6.24 kernel of Ubuntu 8.10.

Any help?

Thanks in advance

[SnowTDM (eortega)]

Hello everybody,

I've solved the problem change the port of the stick from the usb hub to a port connected directly to motherboard.

It seems a problem with the hub instead with the drivers.

Thanks

[coubi64 (frederic-valentin)]

I have often freezes of the system at startup while trying to connect with network manager applet.

It would be nice to solve this problem.

Thanks.

[Mark Krapivner (mark125)]

don't know if ths is related, but after every restart my wireless card (using zd1211rw) stops working, if comes back after remove it and plug it back a few times.
"dmesg | grep -i zd1211rw" output:
[ 97.264635] zd1211rw 5-1:1.0: eth1
[ 97.264659] usbcore: registered new interface driver zd1211rw
[ 97.359527] zd1211rw 5-1:1.0: couldn't load firmware. Error number -32
[ 100.980931] zd1211rw 5-1:1.0: couldn't load firmware. Error number -110
[ 123.986189] zd1211rw 5-1:1.0: couldn't load firmware. Error number -110
[ 135.162881] zd1211rw 5-1:1.0: couldn't load firmware. Error number -110
[ 146.991315] zd1211rw 5-1:1.0: couldn't load firmware. Error number -110

[weez (trs-e0z9g4)]

I purchased a MyEssentials Wireless G ME1001-USB dongle to make my desktop headless and move it out of my office. I was connecting to the desktop through VNC and streaming 256KB ogg files off of it through SSHFS for several hours when it quit working. At the time it croaked the only thing plugged into the computer besides the wifi dongle (directly into the motherboard) was the power cable.

When I hauled in the monitor, mouse and keyboard, I saw that knetworkmanager was waiting for the kwallet password. supplying the kwallet password and then reselecting my network in knetworkmanager to renew the IP got the connection back up. usb did not appear to be hung.

This ominous message was in dmesg which brought me to this page:
zd1211rw 5-1:1.0: error ioread32(CR_REG1): -110

System is a fresh install of 8.04 on an intel 975bx motherboard with an Nvidia graphics card.

I will make sure to leave open kwallet this time to see if I see this happen again.

Attached is my dmesg (mac addresses masked to protect the innocent).

[weez (trs-e0z9g4)]

this is my lsusb (under normal circumstances there would be no mouse/keyboard)

[jemand (ich-22)]

in the meanwhile i have been using the wireless-everything kernel, the 25.rc3 kernel, and a patched ubuntu 2.6.26-19. All with mac80211. Sadly i have to say, that this problem is not fixed by using mac80211.

Some other thing is: with the ubuntu 2.6.26-18 kernel and -19 (unpatched, original) the usb does not freeze, the modules can be unloaded and reloaded again, but it will not work again.

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[whitelightme (inspheration-deactivatedaccount)]

I am one of the ppl who have this boring bug, too.
Initially, i thought the problem was the hub, but it is not.
(However, i think you should consider that connecting the device directly causes this bug less frequently; but still persists).
Feel free to ask for more info, greetings. :)

[Leann Ogasawara (leannogasawara)]

Hi Guys,

Can anyone still experiencing this bug test with the latest Alpha for the upcoming Intrepid Ibex 8.10 release. It is actively being worked on by the developers. If you can also attach an updated dmesg output which reflects the error messages that would be great as well. Thanks.

[Mark Krapivner (mark125)]

the bug still exists on intrepid alpha 4. the dmesg output is the same as displayed in the comments above.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Mark Krapivner (mark125)]

i worked with alpha 6 a few days and i didn't encounter this bug (with Kernel 2.6.27), if any one else can confirm it's fixed too please do so :-)

BUT, this bug still exists on kernel 2.6.24 that comes with hardy, which is an LTS release.

[Leann Ogasawara (leannogasawara)]

Thanks Mark. Can anyone else verify this is resolved for Intrepid?

[lars (larsrss)]

Hi i run Intrepid ubuntu i got myusb wlan zd1211 disconecte some times

[Markus Marschall (marschall-m)]

Intrepid: Doesn't work, still the same bug.

[Iron Bishop (ironbishop)]

I don't know if this is related, but on a different pc (Ubuntu Hardy, AMD Sempron, 2.6.24-22-generic) I keep getting kernel panics related to the zd1211 usb device.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Keng-Yu Lin (lexical)]

This bug report was marked as Incomplete a while ago and has not had any feedback to provide the requested information. As a result this bug is being closed. Please reopen if this is still an issue in the latest Karmic 9.10 Alpha release http://cdimage.ubuntu.com/releases/karmic/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.