Bug 190253 - Zyd: device timeout after a while.
Summary: Zyd: device timeout after a while.
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: usb (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-usb (Nobody)
Depends on:
Reported: 2014-05-26 10:10 UTC by neoedmund
Modified: 2018-05-28 19:42 UTC (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description neoedmund 2014-05-26 10:10:00 UTC
Just like written in
I found it has no response and I have the almost same problem.

My device info using "usbconfig dump_device_desc":

ugen3.3: <USB2.0 WLAN ZyDAS> at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0200 
  bDeviceClass = 0x00ff 
  bDeviceSubClass = 0x00ff 
  bDeviceProtocol = 0x00ff 
  bMaxPacketSize0 = 0x0040 
  idVendor = 0x0ace 
  idProduct = 0x1215 
  bcdDevice = 0x4810 
  iManufacturer = 0x0010  <ZyDAS>
  iProduct = 0x0020  <USB2.0 WLAN>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001 

In my case, I have to replug the wifi usb stick times and times again.
But I found only if I use openvpn, it works stable.

How-To-Repeat: 1.) Plug in the USB WLAN stick and make sure your internet is working
2.) Load a few pages or download a file at an average speed.

After all that, if you want to make it work again, you have to re-plug the
USB WLAN stick.

in /var/log/messages there is "zyd0: device timeout"
Comment 1 Yuri Victorovich freebsd_committer 2016-10-09 06:18:53 UTC
Duplicate of https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=138292
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:42:28 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
- Untouched since 2018-01-01.
- Affects Base System OR Documentation


Reset to open status.

I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.