[sane-devel] Scanner failure when connected via USB3

[m. allan noah]

try compressing your attachments.

allan

On Mon, Oct 27, 2014 at 7:00 AM, Mike Cloaked <mike.cloaked at gmail.com> wrote:
> On Mon, Oct 27, 2014 at 10:25 AM, Mike Cloaked <mike.cloaked at gmail.com>
> wrote:
>>
>> On Sun, Oct 26, 2014 at 4:28 PM, Mike Cloaked <mike.cloaked at gmail.com>
>> wrote:
>>>
>>> On Tue, Sep 23, 2014 at 11:57 PM, Olaf Meeuwissen
>>> <olaf.meeuwissen at avasys.jp> wrote:
>>>>
>>>>
>>>> m. allan noah writes:
>>>>
>>>> > Mike- when you get back to the machine, maybe you could make some
>>>> > logs. If we could see a usb log of what scanimage does and what
>>>> > vuescan does, we might be able to find a difference. The problem will
>>>> > be figuring out how to both reduce the volume of data the the bare
>>>> > minimum which reproduces the problem, and also doing exactly the same
>>>> > thing in both cases. I might be as simple as a 'scanimage --help'
>>>> > multiple times in a row, and starting/stopping vuescan multiple times.
>>>> > I'm not sure how to tell the kernel to enable usb logging, but I bet
>>>> > google will tell you :)
>>>>
>>>>   $ sudo modprobe usbmon
>>>>   $ sudo wireshark
>>>>
>>>> and selecting the right USB bus to capture traffic on.  The `usbmon#`
>>>> numbers match the bus numbers that `lsusb` outputs.
>>>>
>>>> Hope that helps,
>>>>
>>>
>>> Sorry about the delay - things got a bit hectic this month - the coming
>>> week looks a little easier so I will set up to test the scanner for usb logs
>>> during the coming week, and once I have captured some logging information I
>>> will post back.
>>>
>>> --
>>> mike c
>>
>>
>> I had a little time this morning available to test the scanner.  I am
>> testing on a Lenovo Y510p laptop with usb3 ports. The laptop is running arch
>> linux fully up to date  with kernel 3.17.1-1-ARCH.
>>
>> The relevant sane package versions are:
>>
>>  [root at lenovo2 ~]# pacman -Qs sane
>> local/kdegraphics-ksaneplugin 4.14.2-1
>>     A scan plugin that implements the scanning
>> local/libksane 4.14.2-1
>>     An image scanning library
>> local/perl-common-sense 3.73-1
>>     Implements some sane defaults for Perl programs
>> local/sane 1.0.24-3
>>     Scanner Access Now Easy
>> local/sane-frontends 1.0.14-7
>>     A set of frontends for SANE.
>> local/xsane 0.999-1
>>     A GTK-based X11 frontend for SANE and plugin for Gimp.
>> local/xsane-gimp 0.999-1
>>     XSane Gimp plugin
>>
>>
>> I was following the guide at
>> https://www.kernel.org/doc/Documentation/usb/usbmon.txt
>>
>> I found that the usbmon directory was already mounted:
>> # ls /sys/kernel/debug/usb/usbmon/
>> 0s  0u  1s  1t  1u  2s  2t  2u  3s  3t  3u  4s  4t  4u
>>
>> Checking which bus was used when the scanner was plugged in was bus 1 from
>> the lsusb command.
>>
>> The after pulling the usb cable out I did
>> # cat /sys/kernel/debug/usb/usbmon/1u >
>> /home/mike/Documents/debugging/scanner/vuescan.mon.out
>>
>> and then re-inserted the scanner usb cable into the usb3 port, and started
>> up vuescan.
>>
>> After doing a single scan I stopped the log and saved it.
>>
>> Then I did the same but using xsane from the GIMP - and it reliably
>> crashed xsane, but it also zeroed out the usb monitor log file!  Eventually
>> I was able to stop the monitor stream and save the file before xsane
>> finished crashing, and whilst the scanner was still producing a continuous
>> screaming noise, I safeguarded the file as xsane1.mon.out.
>>
>> Both these files are attached.  I have not tried to get wireshark to
>> analyse the data as I am not sure how to do it.
>>
>> Are these two log files a help in getting some diagnostics?
>>
>> Thanks
>>
>> Mike
>>
>> --
>> mike c
>
>
> I am re-sending this without the logfile attachments as they were too big to
> be accepted on the list and the original is held for moderation. I could
> post the logs to a cloud temporary file?
>
> By the way with xsane when I first plug in the scanner and start xsane via
> the GIMP it does begin to work and indeed completes a pre-scan.  However if
> I select 300dpi resolution and ask it to to a full scan then that is when it
> reliably crashes and the scanner screams for some time but eventually stops.
> If I restart xsane it sometimes crashes almost straight away but sometimes
> looks as though it has started again but crashes almost as soon as I try to
> do anything with it.
>
> --
> mike c



-- 
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"