Re: device reset
On 8/27/2011 9:00 AM, Hans Petter Selasky wrote: On Saturday 27 August 2011 14:59:50 Marcin Wisnicki wrote: On Sat, Aug 27, 2011 at 14:04, Hans Petter Selasky hsela...@c2i.net wrote: On Saturday 27 August 2011 13:19:35 Marcin Wisnicki wrote: Would it be possible to reinstate ability to power-cycle particular port the way it was ~year ago ? This is still possible. There is a sysctl to disable this feature: sysctl hw.usb.no_cs_fail=1 $ sysctl hw.usb.no_cs_fail sysctl: unknown oid 'hw.usb.no_cs_fail' $ uname -v FreeBSD 8.2-STABLE #4: Sun Jun 26 15:10:04 CEST 2011 r...@ghost.pnet.one.pl:/home/obj/usr/src/sys/SERWER_DDB You need the kernel from the latest 8-stable. How do you power cycle just one port ? ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: device reset
On Monday 29 August 2011 14:15:59 Mike Tancsa wrote: On 8/27/2011 9:00 AM, Hans Petter Selasky wrote: On Saturday 27 August 2011 14:59:50 Marcin Wisnicki wrote: On Sat, Aug 27, 2011 at 14:04, Hans Petter Selasky hsela...@c2i.net wrote: On Saturday 27 August 2011 13:19:35 Marcin Wisnicki wrote: Would it be possible to reinstate ability to power-cycle particular port the way it was ~year ago ? This is still possible. There is a sysctl to disable this feature: sysctl hw.usb.no_cs_fail=1 $ sysctl hw.usb.no_cs_fail sysctl: unknown oid 'hw.usb.no_cs_fail' $ uname -v FreeBSD 8.2-STABLE #4: Sun Jun 26 15:10:04 CEST 2011 r...@ghost.pnet.one.pl:/home/obj/usr/src/sys/SERWER_DDB You need the kernel from the latest 8-stable. How do you power cycle just one port ? ---Mike You need to send a custom control request. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: device reset
On Fri, 26 Aug 2011 08:55:52 +0200, Hans Petter Selasky wrote: On Thursday 25 August 2011 21:56:43 Mike Tancsa wrote: On 8/25/2011 3:40 PM, Hans Petter Selasky wrote: After 22nd of July, r223414: http://svn.freebsd.org/changeset/base/223414 That looks to be June 22nd ? In that case, I have that in my kernel already http://lists.freebsd.org/pipermail/svn-src-stable-8/2011- June/005683.html Any other tricks you can think of to reset the device short of installing a HUB at each location ? No. Upgrading the modem firmware. Talking to the vendor about it. --HPS Would it be possible to reinstate ability to power-cycle particular port the way it was ~year ago ? ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: device reset
On 8/26/2011 2:55 AM, Hans Petter Selasky wrote: Any other tricks you can think of to reset the device short of installing a HUB at each location ? No. Upgrading the modem firmware. Talking to the vendor about it. Understood. I did some more testing with the version of the kernel I have in the field locally. When the 3g modem has not crashed, I can reset it just fine using usbcontrol reset. I also found a Dlink hub that when I issue a usbcontrol power_off and power_on it really does power off and on the port. This will be handy for a couple of remote sites for me... ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
device reset
I am having periodic problems with the odd u3g device that gets hung. If I try and reset it, it totally locks up and I need to do a reboot of the box the recover. Apart from usbconfig reset are is there anything else I can do to recover from such a situation ? usbconfig -d 1.3 dump_info ugen1.3: ZTE CDMA Technologies MSM ZTE, Incorporated at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON usbconfig -d 1.3 dump_all_config_desc ugen1.3: ZTE CDMA Technologies MSM ZTE, Incorporated at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0100 bNumInterfaces = 0x0004 bConfigurationValue = 0x0001 iConfiguration = 0x no string bmAttributes = 0x00a0 bMaxPower = 0x00fa Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x00ff iInterface = 0x no string Additional Descriptor bLength = 0x05 dmesg shows at bootup time ugen0.2: APC at usbus0 ugen1.3: ZTE, Incorporated at usbus1 ugen1.3: ZTE, Incorporated at usbus1 (disconnected) ugen1.3: ZTE, Incorporated at usbus1 u3g0: ZTE, Incorporated ZTE CDMA Technologies MSM, class 0/0, rev 2.00/0.00, addr 3 on usbus1 u3g0: Found 1 port. umass0: ZTE, Incorporated ZTE CDMA Technologies MSM, class 0/0, rev 2.00/0.00, addr 3 on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x umass0:0:0:-1: Attached to scbus0 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI status: Check Condition (probe0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: ZTE MMC Storage 322 Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present if I do a usbconfig -d 1.3 reset I get u3g0: at uhub1, port 1, addr 3 (disconnected) umass0: at uhub1, port 1, addr 3 (disconnected) (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) I have also tried post reset # usbconfig -d 1.3 set_config 255 # usbconfig -d 1.3 set_config 0 usbconfig: could not set config index: Input/output error # This is RELENG_8 on an alix box from July 14th. -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: device reset
On 8/25/2011 3:02 PM, Hans Petter Selasky wrote: On Thursday 25 August 2011 21:00:17 Mike Tancsa wrote: I am having periodic problems with the odd u3g device that gets hung. If I try and reset it, it totally locks up and I need to do a reboot of the box the recover. Apart from usbconfig reset are is there anything else I can do to recover from such a situation ? Hi, Have you tried using an external self-powered HUB? Yes, seems to work with the hub There has been some patches to auto-reset non-responding USB devices, which you might try which was committed to 8-stable not long ago. How recent were those patches applied ? I am running stable from July 14th. ---Mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: device reset
On Thursday 25 August 2011 21:31:41 Mike Tancsa ppsupport wrote: On 8/25/2011 3:02 PM, Hans Petter Selasky wrote: On Thursday 25 August 2011 21:00:17 Mike Tancsa wrote: I am having periodic problems with the odd u3g device that gets hung. If I try and reset it, it totally locks up and I need to do a reboot of the box the recover. Apart from usbconfig reset are is there anything else I can do to recover from such a situation ? Hi, Have you tried using an external self-powered HUB? Yes, seems to work with the hub There has been some patches to auto-reset non-responding USB devices, which you might try which was committed to 8-stable not long ago. How recent were those patches applied ? I am running stable from July 14th. ---Mike After 22nd of July, r223414: http://svn.freebsd.org/changeset/base/223414 --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: device reset
On Thursday 25 August 2011 21:40:25 Hans Petter Selasky wrote: On Thursday 25 August 2011 21:31:41 Mike Tancsa ppsupport wrote: On 8/25/2011 3:02 PM, Hans Petter Selasky wrote: On Thursday 25 August 2011 21:00:17 Mike Tancsa wrote: I am having periodic problems with the odd u3g device that gets hung. If I try and reset it, it totally locks up and I need to do a reboot of the box the recover. Apart from usbconfig reset are is there anything else I can do to recover from such a situation ? Hi, Have you tried using an external self-powered HUB? Yes, seems to work with the hub There has been some patches to auto-reset non-responding USB devices, which you might try which was committed to 8-stable not long ago. How recent were those patches applied ? I am running stable from July 14th. ---Mike After 22nd of July, r223414: ^^^ oops 22nd of June --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Device reset
HPS, In FBSD7 I committed an ioctl on the ugen.c (some time ago) that allowed for resetting the device. Not a port on the device, but the device itself. This was a function that was unimplemented in libusb1 up to then. For example some Atmel devices need a reset after you uploaded the firmware. I cannot seem to find this functionality in usb_ioctl.h in teh FBSD8 USB stack. Another use for this feature is to be able to reset a device into a known state, like the 3G dongles that freeze. Power-cycling them is the short way out of the situation. Cheers, Nick ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Device reset
On Thursday 25 June 2009 15:24:02 Nick Hibma wrote: HPS, In FBSD7 I committed an ioctl on the ugen.c (some time ago) that allowed for resetting the device. Not a port on the device, but the device itself. This was a function that was unimplemented in libusb1 up to then. For example some Atmel devices need a reset after you uploaded the firmware. I cannot seem to find this functionality in usb_ioctl.h in teh FBSD8 USB stack. Another use for this feature is to be able to reset a device into a known state, like the 3G dongles that freeze. Power-cycling them is the short way out of the situation. Cheers, Hi Nick, It's still there: See USB_DEVICEENUMERATE(). Supported by by libusb and libsub20. Also see: usbconfig -u X -a Y reset --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Device reset
Hm, ik DEVICEENUMERATE wasn't in my search. Thanks. Nick On Thursday 25 June 2009 15:24:02 Nick Hibma wrote: HPS, In FBSD7 I committed an ioctl on the ugen.c (some time ago) that allowed for resetting the device. Not a port on the device, but the device itself. This was a function that was unimplemented in libusb1 up to then. For example some Atmel devices need a reset after you uploaded the firmware. I cannot seem to find this functionality in usb_ioctl.h in teh FBSD8 USB stack. Another use for this feature is to be able to reset a device into a known state, like the 3G dongles that freeze. Power-cycling them is the short way out of the situation. Cheers, Hi Nick, It's still there: See USB_DEVICEENUMERATE(). Supported by by libusb and libsub20. Also see: usbconfig -u X -a Y reset --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
