Alan > The driver _did_ enqueue commands after the timeout errors. Got it ! The USB analyzer indicates that same CBW was repeated three times in row because the device did not generate ACK for the CBW. After three failed attempts, usb_stor_Bulk_reset is invoked. Is there a way to increase the retry count from its current value of 3 ?
Note also that when the same key attached to a linux PC, successfully generates ACK for all the CBW. Thanks. Regards Vivek > -----Original Message----- > From: Alan Stern [mailto:[EMAIL PROTECTED] > Sent: Monday, September 25, 2006 12:40 PM > To: Vivek Dharmadhikari > Cc: [email protected] > Subject: Re: [linux-usb-devel] USB DISK does not work > > On Mon, 25 Sep 2006, Vivek Dharmadhikari wrote: > > > Alan > > > > > But if you want to create one anyway, this is how to it. > > > Edit unusual_devs.h in drivers/usb/storage/ in the kernel > source. > > > Add an entry for the POCKET USB device, with the > appropriate vendor, > > > product and revision numbers, and use the US_FL_NO_WP_DETECT flag. > > > > I created unusal device entry with US_FL_NO_WP_DETECT and > > US_FL_SINGLE_LUN. That seems to make the device happy as the scsi > > drivers consistently recognize the device and its partition > as shown > > below. Without the flags, the scsi driver used to take long time to > > recognize the device. > > Good. > > > However, the mount operation somestimes succeed and > sometimes not. The > > usb storage log below is for the case when the mount > operation do not > > succeed. The corresponding USB trace on the analyzer indicates that > > the device do not generate ACK three times in a row and host driver > > then cause reset. Is there any way to make the driver enque > a command > > after ohci driver reports "timeout or NAK" error for it ? > > The driver _did_ enqueue commands after the timeout errors. > > > Any other suggestion > > ? > > You could try upgrading to a more recent version of the Linux > kernel, but I don't think it will help. That device > repeatedly returned a failure status code when asked to read > a particular sector, and when the computer asked for the > detailed error information, the device didn't reply at all. > > I think you should try using a different mass-storage device. > This one clearly doesn't work very well. > > Alan Stern > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
