On Mon, Aug 03, 2009 at 07:00:47PM -0400, Andrew Lutomirski wrote: > On Mon, Aug 3, 2009 at 6:01 PM, Andrew Lutomirski<luto@xxxxxxx> wrote: > > On Mon, Aug 3, 2009 at 5:49 PM, Andrew Lutomirski<luto@xxxxxxx> wrote: > >> On Mon, Aug 3, 2009 at 5:20 PM, Greg KH<greg@xxxxxxxxx> wrote: > >>> On Mon, Aug 03, 2009 at 05:14:56PM -0400, Andrew Lutomirski wrote: > >>>> Hi all- > >>>> > >>>> I'm trying to use usbtmc on an Aglient N9310A (The only TMC device I > >>>> have), and it sort of works, but it seems to be both extremely buggy > >>>> and missing a good deal of rather important functionality. Is there > >>>> anyone maintaining it? > >>> > >>> Yes, me. > >>> > >>>> If the answer is yes, I can describe the bugs (logspam, spurious > >>>> errors, delayed messages, inability to read status, etc.) in greater > >>>> detail. > >>> > >>> Please do, but also please use the latest version, in 2.6.30.3, we fixed > >>> some bad problems in it recently. > >> > >> I am. > >> > >> Almost anything I do triggers this: > >> > >> usbtmc 3-1:1.0: Unable to read data, error -110 > >> > > My N9310A is now totally wedged. Anything I can think of doing (send > queries, send *RST, or any of the CLEAR ioctls) fails and spews stuff > like this: > > [360946.881771] usbtmc 3-1:1.0: Unable to send data, error -110 > [360946.890770] usbtmc 3-1:1.0: usb_bulk_msg returned -110 > [360965.303400] usb 3-1: usb_control_msg returned -110 > [360965.312404] usb 3-1: usb_control_msg returned -110 > [361052.364626] usbtmc 3-1:1.0: usb_bulk_msg returned -110 > [361055.114579] usbtmc 3-1:1.0: Unable to send data, error -110 > [361055.123574] usbtmc 3-1:1.0: usb_bulk_msg returned -110 > > I'm going to leave it like this in case you want me to try something. I really don't know, sorry. Bad firmware on the device? odd. greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html