linux-kernel - Re: nonzero write bulk status received: -62

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.1104051010250.1972-100000@iolanthe.rowland.org>
Date:	Tue, 5 Apr 2011 10:12:58 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	David Newall <davidn@...idnewall.com>
cc:	linux-usb@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: nonzero write bulk status received: -62

On Tue, 5 Apr 2011, David Newall wrote:

> I'm getting the above error on a recent installation, when printing to a 
> USB connected printer, and only the first half of the page is printed.  
> Searching Google, I found that this is surprisingly common (I was 
> surprised), both using usb parallel converters as well as usb-connected 
> printers, and the only suggestion seems to be to change CUPS's device 
> URI to parallel:/dev/usb/lpN - it's currently 
> usb://OKI%20MICROLINE%20something.  (Even though it seems somewhat 
> bizarre, I am trying the suggestion, but haven't heard the results yet.)
> 
>  From UTSLing I see that error 62 is ETIME, but finding the timer 
> involved requires getting arms-deep into the USB code.

It isn't a software timer; it is a hardware requirement.  ETIME means
the printer failed to acknowledge to a packet sent by the computer
within the required 3-microsecond limit (or whatever the actual value
is -- something like that).

>  I found no 
> discussion on this, and wonder if I just missed it, or if there really 
> is some issue that worth looking at.  Something about extended output 
> and ETIME makes me think it is worth looking at.
> 
> I'd appreciate pointers, either to discussions and solutions that I 
> missed, or to places in the code where I might start looking.

You could capture a usbmon trace.  See the instructions in the kernel 
source file Documentation/usb/usbmon.txt.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/