From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932351AbZHCXAw (ORCPT ); Mon, 3 Aug 2009 19:00:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932338AbZHCXAu (ORCPT ); Mon, 3 Aug 2009 19:00:50 -0400 Received: from mail-fx0-f217.google.com ([209.85.220.217]:42669 "EHLO mail-fx0-f217.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932336AbZHCXAr convert rfc822-to-8bit (ORCPT ); Mon, 3 Aug 2009 19:00:47 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=gzSZMAiKaDxf9bk+E6rM+VIixFocIA9M8N46jzeM8FFWaAByh8DrvVVC5eh2uRVxZo G+o3FCiLq+3+WJQsqQfpRkU0n0HxA5ws/Ssv/gCtHDKCv86pDuKnBUvOj3AEwC6gCRKB IdW/zwO7fwJoK5jAFTS9x4XoRDEzIopXLpHGU= MIME-Version: 1.0 In-Reply-To: References: <20090803212015.GC28579@kroah.com> Date: Mon, 3 Aug 2009 19:00:47 -0400 X-Google-Sender-Auth: 568331a004e8c97c Message-ID: Subject: Re: Is anyone maintaining (or even using) usbtmc? From: Andrew Lutomirski To: Greg KH Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, gregkh@suse.de Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 3, 2009 at 6:01 PM, Andrew Lutomirski wrote: > On Mon, Aug 3, 2009 at 5:49 PM, Andrew Lutomirski wrote: >> On Mon, Aug 3, 2009 at 5:20 PM, Greg KH 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