04c5:11a2 Fujitsu ScanSnap S1500 does not work on USB3 ports

This bug also happens on my other 12.10 64-bit machine.

Status changed to 'Confirmed' because the bug affects multiple users.

This is apparently USB3-port-specific??? Anything plugged into that same stack of two USB3 ports on the back of the desktop have the "microframe" error and don't work. When I plugged this into a different port to test out 32-bit 12.10 and 64-bit 12.04, it worked perfectly. Rebooting into 12.10 64-bit worked perfectly.

I plugged the scanner into the USB3 port on my laptop, as well, when testing to see if it was machine-specific. Plugging my UPS into the USB3 port gives me a "microframe" error. So apparently, this is something USB3-specific.

Time to search for USB3 kernel errors. If there are any, I'll add this as a dupe.

How is this a duplicate of 1006011? That bug is about the USB audio device 'M-Audio Fast Track Ultra', while this is about scanners.

Anyway, I have the same issue with an Epson scanner, including under the latest 3.9-rc6 kernel. The syslog doesn't show any errors; it just doesn't work in USB3 and does in USB2.

The dupe is also about an external device that works just fine in USB2 ports but not USB3 ports, and reports the same "rounding intervals... microframes" error in dmesg. Looks like the same underlying issue to my ignorant eyes.

But I'm no kernel hacker, so if you know it to be a different issue, you're having the same exact problem (with the same microframes message in dmesg), and you're willing to bisect the kernel, then by all means, undupe it! :-)

Ok, the original report probably needs updating then to reference the USB3-microframes issue.

I'm not getting any microframes error messages in dmesg, though. It fails silently.

Yours is probably different then.

I wasn't being sarcastic, though. I AM ignorant of the kernel. That's why I suggest filing a separate bug. Yours doesn't have the "microframes" issue, so I think it's different. Let someone who does know more about the kernel than me say it's a dupe. :-)

I'm also seeing this issue with a fresh install of 13.04. On a new laptop with only USB 3.0 ports I can see the scanner connected in dmesg, but sane-find-scanner doesn't detect it, exactly as the original reporter described. The same scanner works perfectly on older hardware with USB 2.0 ports.

Given that I don't have USB 2.0 available on the new laptop, is there a workaround?

Cliff, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.10-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Okay, it doesn't work in the latest dev release of Saucy. I'll try to do the kernel thing.

Note: I travel for my job, so Monday through Friday I'm often not available to work on this because I don't have the scanner with me.

By the way, this cutesy little naming convention is okay, but maybe put the name it in the "About This Computer" dialog so that someone troubleshooting can figure out what they need to download from the Kernel Mainline archive. Just a thought. :-)

Bah. The link to the Mainline Kernel Archive that you put has two different links to the archive, with two different orderings of the directory listings.

So when you say "Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom.", you mean that you want me to test kernel "v3.10-rc6-saucy" on my 12.10 Quantal machine?

Okay, I did your testing. The Mainline kernel did not fix it. And had the added bonus of making Unity disappear. I wound up having to do this to get it working again. http://askubuntu.com/questions/285627/unity-does-not-start-in-ubuntu-13-04

Cliff, as per http://www.gigabyte.us/products/product-page.aspx?pid=4315#bios an update is available for your BIOS (F14). If you update to this, does it change anything?

If not, could you please provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

Does this issue go away if you boot into the latest 3.2 stable kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.46-precise/

Updated BIOS to F14. Did not fix the problem.
Output of the dmidecodes:
F14
04/17/2013

I realize now, as I re-read some of my later comments, that I've been unclear or downright WRONG in some of the additional information I've given. So please let me clarify.

I have two machines. I have just re-verified that both exhibit the problem when the scanner is plugged into a USB3 port, and work just fine when the scanner is plugged into a USB2 port.

1) Desktop, now running 13.04. This is the machine with the scanner always connected. This is what I'm testing everything on. All of the logs I've uploaded have come from this machine. When I first filed this bug, it was running 12.10.

2) Laptop, still running 12.10. When the scanner didn't work on the desktop, I plugged it into the laptop and got the same "microframes" error from the USB3 port. This was just to verify that there was a problem independent of the desktop.

Please be patient with me. :-) Having to context-shift away from this and travel for work (using the laptop), then come back... sometimes I get things confused.

@jsalisbury
I will test that, though I'm hesitant due to the graphics/Unity problems I had the last time I installed a mainline kernel. So I want to make sure that we're on the same page first. :-)

When I first filed the bug, I was totally unsure and unclear of what had happened and what caused it. I THOUGHT it was the erasure of 12.04 and clean install of 12.10 that made the bug appear. I had just done that, as well as unplug my desktop and cleaned out the dust. After much Googling, searching for bugs, and testing with the laptop, I thought it was 12.10-specific, so I filed the bug.

THEN, while further researching it, I found that other people had that "microframes" error when they plugged certain USB2 devices into USB3 ports. Plugging the scanner into known USB2 ports on the desktop and laptop showed the scanner to be working. I'm guessing that when I plugged everything back in to the desktop after dusting, I plugged the scanner back into a USB3 port instead of a USB2 port. Since then, I've updated the desktop to 13.04, and the laptop remains at 12.10.

Do you still want me to try the 12.04 mainline kernel from that PPA?

Cliff, just to clarify, if you plug the scanner into into your USB 3.0 port in Precise 32-bit, does it work?

Ran 12.04 32-bit from the LiveCD. The scanner worked fine in the USB2 port, but failed in the USB3 port. dmesg showed the same microframes message.

Cliff, thank you for performing the requested test.

While booted into the newest mainline kernel available http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc7-saucy/ , could you please gather a USB trace for a more in depth analysis following http://www.kernel.org/doc/Documentation/usb/usbmon.txt ?

Thank you for your understanding.

Whenever I install a mainline kernel deb, I get the same problem as Bug 1195618. This makes it very difficult to test scanning on the mainline kernels and get back to normal desktop use.

I looked for a workaround, but according to the Internet so far, this is a problem with the late 3.9 and all 3.10 kernels on nearly all versions of the Nvidia drivers.
https://devtalk.nvidia.com/default/topic/549532/linux-3-10-incompatibility-in-function-lsquo-nv_i2c_del_adapter-rsquo-error-void-value-not-igno/

I'm going to try to install Nouveau, or whatever the free version of the Nvidia drivers is, and see if that fixes it so that I can test.

Nouveau was better, in that I had 1024x768 resolution instead of 640x480, but I'd rather not live there. ;-) (and I remember when that resolution was the shiz...:-)

So, I got the usbmon capture. I can't be certain that what I captured was for the scanner because the command in Step 2 (cat /proc/bus/usb/devices) didn't have output because I didn't have a usb directory under /proc/bus. But I tested and I am pretty sure that it's not a capture of my USB keyboard/mouse or hard drives. :-)

1.mon.out is simply the act of turning the scanner on. This is what gives the "microframes" error in dmesg.
2.mon.out is an attempt to access the scanner using gscan2pdf.

Hope this helps!

Just checking in...

1) Are you waiting for me to do something? I don't think I missed anything.

2) I don't want the bug to auto-expire. :-)

3) I ask in all true ignorance (since I don't have the knowledge to read a usbmon capture)... Could this bug be the cause of my problem? http://article.gmane.org/gmane.linux.usb.general/93288

Cliff, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

I have the same problem with a Haswell motherboard and a S1500. On my motherboard, the USB 2 ports are also controlled by the XHCI USB controller. Thus the scanner does not work on any of the USB ports. The machine is running Debian 7, and has the same problem with with a 3.2 and 3.10 kernel. I could give Ubuntu a whirl, but I imagine I'd get the same results.

FWIW, the patch in http://article.gmane.org/gmane.linux.usb.general/93288 has not been committed to the mainline kernel AFAICT. Even if it is the fix, it is probably not in any kernel you are testing unless Ubuntu is carrying that patch (or other XHCI patches) on their daily builds. The only XHCI patch I see Saucy carrying is a fix for bug 1210858.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

This bug is still present in Ubuntu 13.10 using the latest (stable) 3.12-1 kernel from the weekly kernel builds.

Rocko, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions or comments, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

This issue is still present in Ubuntu 14.04.

I am also running into the same problem in Ubuntu 14.04. The error message is the same in dmesg
[ 5313.032199] usb 1-3.3: new high-speed USB device number 24 using xhci_hcd
[ 5313.064156] usb 1-3.3: New USB device found, idVendor=04c5, idProduct=11a2
[ 5313.064161] usb 1-3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 5313.064163] usb 1-3.3: Product: ScanSnap S1500
[ 5313.064165] usb 1-3.3: Manufacturer: Fujitsu
[ 5313.064317] usb 1-3.3: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
[ 5313.064322] usb 1-3.3: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes

savanna, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

I also have a problem with Fujitsu ScanSnap S1500 in Mint 17; it's not being recognized (same problem as yours):
$ dmsg
...
[ 5423.381405] usb 3-5: new high-speed USB device number 11 using xhci_hcd
[ 5423.413007] usb 3-5: New USB device found, idVendor=04c5, idProduct=11a2
[ 5423.413009] usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 5423.413010] usb 3-5: Product: ScanSnap S1500
[ 5423.413011] usb 3-5: Manufacturer: Fujitsu
[ 5423.413130] usb 3-5: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
[ 5423.413131] usb 3-5: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes

My system: Linux sky 3.13.0-24-generic, 64 bits, NVIDIA GK107 GeForce GTX650 Nvidia 331.38-0ubuntu7.1
Motherboard MSI B85M-G43

It fails in both USB2 and USB3 motherboard ports. Somehow if I plug/unplug the scanner, start gscan2pdf, I see the scanner
listed but I then soon get if I select the device "Error opening device, error durring device IO".

***AMAZINGLY*** in Mint 16, with a GA-Z87X-UD3H Gigabyte motherboard I had similar troubles that were completely solved when I installed a USB2.0 card in the motherboard (that motherboard has only USB 3 ports).

The scanner works fine on an old laptop, mint 16 64 bits, USB 2 port...

Weird, no?

loop10, this bug report is about Ubuntu, not Linux Mint. If you are having a problem in Ubuntu, so your hardware and problem may be tracked, please file a new report with Ubuntu (not Linux Mint) by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Christopher (penalvch):

Thank you for your reply. I am not totally sure if you reply means that I need to install Ubuntu (instead of Mint 17) to file the bug?

As a desperate attempt I bought a USB2.0 PCI-e card and installed it in my motherboard (Syba PCI-express USB2.0 5 port host controller card). This has SOLVED my problem (for $23).

If I plug the Fujitsu SnapScan S1500 back into a motherboard USB 2.0 port I get the exact same error as before (bellow).

In summary: I have “solved” this recognition problem of the Fujitsu SnapScan S1500 in both Mint 16 and Mint 17 with both GA-Z87X-UD3H Gigabyte motherboard and MSI B85M-G43 motherboard. My solution is to buy a USB2 PCI-e board. From the posts this happens the same way in Ubuntu and Mint (I searched but did not find any Mint forum addressing this). Contrarily to what I previously thought this does not seem to be related to USB 2.0 vs USB 3.0 (I need a PCI-e USB 3 card to be sure).

Hope my long report is of some help. Let me know if I can help further without a new install.

$ dmesg
[ 872.748353] usb 6-6: Product: ScanSnap S1500
[ 872.748354] usb 6-6: Manufacturer: Fujitsu
[ 872.748473] usb 6-6: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes

Again, some system info:
Linux sky 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux, Mint 17, Cinnamon 64 bits 2.2.16
Motherboard: Motherboard MSI B85M-G43 Intel I7-4770 CPU
Graphics card and driver: NVIDIA GK107 GeForce GTX650 Nvidia 331.38-0ubuntu7.1

Update on my report of 2014-11-05:

On the same system as before (see my 2014-11-05 message), still running Mint 17 64bits, I have now installed both a USB2.0 board in the Motherboard (Syba PCI-express USB2.0 5 port host controller card) and a USB3.0 board (Anker USB 3.0 PCI-E card).

 My Fujitsu SnapScan S1500 works fine with the USB2.0 and fails with the USB3.0 board (running gscand2pdf). Strangely the MSI B85M-G43 Motherboard ports that are labelled USB2.0 and the Motherboard ports labeled USB3.0 both fail (bizarre).

So (in summary) it seems that installing a USB 2.0 (not USB 3.0) card in the motherboard will "solve" the problem of using the Fujitsu SnapScan S1500 in Mint 17.

loop10, you are not the original reporter, so providing "Me too!" comments is not helpful here. If you want to be helpful, please file a report as already previously requested of you in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1102797/comments/53 .

This a upstream kernel bug.
Its been recently reported and confirmed on the linux-usb maillist:
http://comments.gmane.org/gmane.linux.usb.general/110579

Its is extermely annoying to say the least.

Its affects my scanner, an epson 1300i also.

Interestingly its been reported working on a CentOS6 machine:
http://www.openfusion.net/linux/scansnap_1300i

and on Arch:
http://kabads.monkeez.org/2014/07/using-fujitsu-scansnap-s1300i-on-arch-linux-going-paperless/

and on a Rpi:
http://www.splitbrain.org/blog/2014-08/23-paper_backup_1_scanner_setup

So I would surmise that they are all either running on machines without xhci controllers or on kernels which are not affected.

To follow up, I went into my laptops BIOS , disabled USB3, checked in dmesg that xhci_hcd was no longer being used:

[Sun Nov 30 14:39:28 2014] usb 1-1.2: new high-speed USB device number 12 using ehci-pci
[Sun Nov 30 14:39:28 2014] usb 1-1.2: New USB device found, idVendor=04c5, idProduct=128d
[Sun Nov 30 14:39:28 2014] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[Sun Nov 30 14:39:28 2014] usb 1-1.2: Product: ScanSnap S1300i
[Sun Nov 30 14:39:28 2014] usb 1-1.2: Manufacturer: FUJITSU

And lo and behold, no more "rounding interval to 128 microframes" mesgs in dmesg and scanner works fine.

Would be nice if ubuntu kernel devs could trac the discussion in the usb maillist and perhaps back port any patches that hopefully eventuates to fix this.

Maksim Lin, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Had the same problem the last few weeks - and updated (without checking what packages where updated) regulary.
But when I recently tried the scanner out both worked - USB 2 + USB 3 (Using an ASRock J1900 Mainboard with Netrunner Frontier (Kubuntu 14.04 based)).

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]