mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lutomirski <luto@mit.edu>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, gregkh@suse.de
Subject: Re: Is anyone maintaining (or even using) usbtmc?
Date: Mon, 3 Aug 2009 19:00:47 -0400	[thread overview]
Message-ID: <cb0375e10908031600v4db81c51hd98094ef9a0a5a16@mail.gmail.com> (raw)
In-Reply-To: <cb0375e10908031501w610d1e27ya69d7c2011f93555@mail.gmail.com>

On Mon, Aug 3, 2009 at 6:01 PM, Andrew Lutomirski<luto@mit.edu> wrote:
> On Mon, Aug 3, 2009 at 5:49 PM, Andrew Lutomirski<luto@mit.edu> wrote:
>> On Mon, Aug 3, 2009 at 5:20 PM, Greg KH<greg@kroah.com> 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.

--Andy

  reply	other threads:[~2009-08-03 23:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03 21:14 Andrew Lutomirski
2009-08-03 21:20 ` Greg KH
2009-08-03 21:49   ` Andrew Lutomirski
2009-08-03 22:01     ` Andrew Lutomirski
2009-08-03 23:00       ` Andrew Lutomirski [this message]
2009-08-04 15:32         ` Juergen Beisert
2009-08-06 19:55         ` Greg KH
2009-08-06 19:54     ` Greg KH
2009-08-06 12:19 ` Zimmermann Christoph
2009-08-06 15:38   ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cb0375e10908031600v4db81c51hd98094ef9a0a5a16@mail.gmail.com \
    --to=luto@mit.edu \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®