On Sat, 28 Feb 2009, Paul O'Keefe wrote:
> Here's 2.6.27-11-generic (Ubuntu Intrepid)
>
> 14:15:45.584430 open("/dev/bus/usb/007/005", O_RDWR) = 3
> 14:15:45.584589 ioctl(3, USBDEVFS_CONTROL, 0xbfc9330c) = 1
> 14:15:45.584971 ioctl(3, USBDEVFS_CLAIMINTERFACE, 0xbfc93324) = 0
> 14:15:45.585088 ioctl(3, USBDEVFS_CLEAR_HALT, 0xbfc93334) = 0
> 14:15:45.585471 nanosleep({0, 100000000}, NULL) = 0
> 14:15:45.685725 ioctl(3, USBDEVFS_CLEAR_HALT, 0xbfc93334) = 0
> 14:15:45.686101 nanosleep({0, 100000000}, NULL) = 0
> 14:15:45.786501 gettimeofday({1235848545, 786565}, NULL) = 0
> 14:15:45.786637 ioctl(3, USBDEVFS_SUBMITURB, 0xbfc931d4) = 0
> -------------------- our friendly timeout was there in 2.6.27--v
> 14:15:45.786763 ioctl(3, USBDEVFS_REAPURBNDELAY, 0xbfc93218) = -1 EAGAIN
> (Resource temporarily unavailable)
> 14:15:45.786916 select(4, NULL, [3], NULL, {0, 1000}) = 1 (out [3], left
> {0, 1000})
> 14:15:45.787055 gettimeofday({1235848545, 787095}, NULL) = 0
> ---------------- clears on first try --------------------------v
> 14:15:45.787157 ioctl(3, USBDEVFS_REAPURBNDELAY, 0xbfc93218) = 0
>
> The rest looks similar. Some timeouts, recoveries and it moves on.
Once again, these are neither timeouts nor errors. This is the way
libusb normally works.
> So we need to separate the issue of the timeout (which recovers) from
> the issue of the device getting lost because it didn't get enough time
> to reset. I don't see a heck of a lot of difference between my 2.6.27
> and 2.6.28 straces. I can post them completely if it is of any help.
I think you have already solved all your problems and you just don't
realize it.
Alan Stern
--
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
