<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Oct 27, 2014 at 10:25 AM, Mike Cloaked <span dir="ltr"><<a href="mailto:mike.cloaked@gmail.com" target="_blank">mike.cloaked@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div><div class="h5"><div class="gmail_quote">On Sun, Oct 26, 2014 at 4:28 PM, Mike Cloaked <span dir="ltr"><<a href="mailto:mike.cloaked@gmail.com" target="_blank">mike.cloaked@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><span><div class="gmail_quote">On Tue, Sep 23, 2014 at 11:57 PM, Olaf Meeuwissen <span dir="ltr"><<a href="mailto:olaf.meeuwissen@avasys.jp" target="_blank">olaf.meeuwissen@avasys.jp</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span><br>
m. allan noah writes:<br>
<br>
> Mike- when you get back to the machine, maybe you could make some<br>
> logs. If we could see a usb log of what scanimage does and what<br>
> vuescan does, we might be able to find a difference. The problem will<br>
> be figuring out how to both reduce the volume of data the the bare<br>
> minimum which reproduces the problem, and also doing exactly the same<br>
> thing in both cases. I might be as simple as a 'scanimage --help'<br>
> multiple times in a row, and starting/stopping vuescan multiple times.<br>
> I'm not sure how to tell the kernel to enable usb logging, but I bet<br>
> google will tell you :)<br>
<br>
</span> $ sudo modprobe usbmon<br>
$ sudo wireshark<br>
<br>
and selecting the right USB bus to capture traffic on. The `usbmon#`<br>
numbers match the bus numbers that `lsusb` outputs.<br>
<br>
Hope that helps,<br><span><font color="#888888"><br>
</font></span></blockquote></div><br></span>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.<span><font color="#888888"><br clear="all"><div><br></div>-- <br>mike c
</font></span></div></div>
</blockquote></div><br></div></div>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. </div><div class="gmail_extra"><br></div><div class="gmail_extra">The relevant sane package versions are:</div><div class="gmail_extra"><br></div><div class="gmail_extra"> [root@lenovo2 ~]# pacman -Qs sane</div><div class="gmail_extra">local/kdegraphics-ksaneplugin 4.14.2-1</div><div class="gmail_extra"> A scan plugin that implements the scanning</div><div class="gmail_extra">local/libksane 4.14.2-1</div><div class="gmail_extra"> An image scanning library</div><div class="gmail_extra">local/perl-common-sense 3.73-1</div><div class="gmail_extra"> Implements some sane defaults for Perl programs</div><div class="gmail_extra">local/sane 1.0.24-3</div><div class="gmail_extra"> Scanner Access Now Easy</div><div class="gmail_extra">local/sane-frontends 1.0.14-7</div><div class="gmail_extra"> A set of frontends for SANE.</div><div class="gmail_extra">local/xsane 0.999-1</div><div class="gmail_extra"> A GTK-based X11 frontend for SANE and plugin for Gimp.</div><div class="gmail_extra">local/xsane-gimp 0.999-1</div><div class="gmail_extra"> XSane Gimp plugin</div><div><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">I was following the guide at <a href="https://www.kernel.org/doc/Documentation/usb/usbmon.txt" target="_blank">https://www.kernel.org/doc/Documentation/usb/usbmon.txt</a></div><div class="gmail_extra"><br></div><div class="gmail_extra">I found that the usbmon directory was already mounted: </div><div class="gmail_extra"># ls /sys/kernel/debug/usb/usbmon/<div class="gmail_extra">0s 0u 1s 1t 1u 2s 2t 2u 3s 3t 3u 4s 4t 4u</div><div class="gmail_extra"><br></div><div class="gmail_extra">Checking which bus was used when the scanner was plugged in was bus 1 from the lsusb command.</div><div class="gmail_extra"><br></div><div class="gmail_extra">The after pulling the usb cable out I did</div><div class="gmail_extra"># cat /sys/kernel/debug/usb/usbmon/1u > /home/mike/Documents/debugging/scanner/vuescan.mon.out<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">and then re-inserted the scanner usb cable into the usb3 port, and started up vuescan.</div><div class="gmail_extra"><br></div><div class="gmail_extra">After doing a single scan I stopped the log and saved it.</div><div class="gmail_extra"><br></div><div class="gmail_extra">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.</div><div class="gmail_extra"><br></div><div class="gmail_extra">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.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Are these two log files a help in getting some diagnostics?</div><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks</div><span class="HOEnZb"><font color="#888888"><div class="gmail_extra"><br></div><div class="gmail_extra">Mike</div><div><br></div>-- <br>mike c
</font></span></div></div>
</blockquote></div><br>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?</div><div class="gmail_extra"><br></div><div class="gmail_extra">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. </div><div class="gmail_extra"><div><br></div>-- <br>mike c
</div></div>