Alan Stern wrote: > On Sat, 2 Mar 2013, Clemens Ladisch wrote: >> But the "timed out" messages come regularly every two seconds, which >> appears to indicate that the test program doesn't manage to do what it >> wants to do. > > Possibly. The program uses a 2-second timeout, which explains the > regular timing of the messages. > > The timeout means that _something_ is wrong. It could be the bug I was > testing for, but more likely it is something else. > >> Are these messages normal? > > Well, let's say that they are normal when something goes wrong. :-) > > With a well-behaved host and a well-behaved flash drive, nothing should > go wrong. But it's not all that surprising for a problem to arise. I > wrote the test program for one specific purpose, so it doesn't have > lots of diagnostic or recovery code. Maybe you're hitting a different > bug, one that affects AMD SB* controllers. > > At any rate, if you're interested in finding out what the problem might > be, the best place to start would be with a usbmon trace. ehci-test: ffff8801e96c06c0 2335244662 S Bo:1:018:1 -115 31 = 55534243 65000000 00000400 00000a28 00000000 00000200 00000000 000000 usb-storage: ffff88021037c480 3386301775 S Bo:1:021:1 -115 31 = 55534243 54000000 00100000 80000a28 0000ef4f 3e000008 00000000 000000 With the patch below, it runs just fine. (And doesn't find EHCI bugs.) Regards, Clemens --- ehci-test.c +++ ehci-test.c @@ -192,7 +192,7 @@ int send_READ10(void) (NUM_BLOCKS << 1) & 0xff, (NUM_BLOCKS >> 7) & 0xff, (NUM_BLOCKS >> 15) & 0xff, - 0, 0, 10, /* Flags, LUN, Length of CDB */ + 0x80, 0, 10, /* Flags, LUN, Length of CDB */ 0x28, 0, /* CDB: READ(10), LUN 0 */ 0, 0, 0, 0, /* LBA = 0 */ 0, /* Reserved */ -- 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
