> I can't fix the block count issue. That's not a bug in the program; > it's a bug somewhere else. Who can fix it? Should we test another stick? >A workaround for the bug has already been submitted to the various >stable kernel series. The workaround may decrease performance slightly >for things like large data transfers to/from a mass-storage device. I >haven't tried to measure the effect, and it will be different on >different platforms anyway. Will UAS(when operational) on 2.0 be affected? > Evidently hardware from a large number of vendors is affected by this > bug. You have to wonder if they all got the intellectual property > from a common source. Or better who copies/steals from whom? > It will apply to a 3.8 kernel. After applying that patch, you should > find that the EHCI bug doesn't show up. Will retest all boards with a kernel having the patch. Testing only the A50M, in dmesg we get: [ 139.795681] ehci-pci 0000:00:12.2: IAA with IAAD still set? , 150 times [ 141.814383] ehci-pci 0000:00:12.2: shutdown urb ffff88004cdf5d80 ep1in-bulk , 600 times what is alarming is that the test program still fails and prints: 100 200 300 URB timed out; bug may be present Wrong URB completed , with the patch applied the program shouldn't have exited on its own, right? Finally the patch seems somehow wrong because it makes generic assumptions. We shouldn't slowdown the USB controller of a ppc based PS3 or XBOX360 for a PCI(add in cards) and a x86(chipsets) specific issue unless otherwise proven. It is not right to waste an ARM tablet with an AHB USB controller. Are you sure it will not brake anything else? Even in x86 you slowdown half of our machines because the rest are broken. If we were asked, we would blacklist controllers based on pairs of PCI device ID and revision. That is mandatory because blacklisting only vendor will work for intel but not for VIA as the same PCI ID is used on many different chipsets and rev has to be additionally used. When a known pair is met a debug only message can be printed and when an unknown pair is met a normal print asking user to send the results to this list. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
