On Fri, 5 Jan 2007, Pete Zaitcev wrote: > First we read capacity > ffff810076399980 3448281218 S Co:004:00 s 21 00 0000 0000 000c 12 = 25000000 > 00000000 00000000 > ffff810076399480 3448284202 C Bi:003:02 0 18 = 70000200 0000000a 00000000 > 3a000000 0000 > ffff810076399980 3448284212 C Co:004:00 0 12 > > ffff81007dbe50c0 3448284226 S Bi:004:01 -115 8 < > ffff81007dbe50c0 3448293201 C Bi:004:01 0 8 = 000007ff 00000200 > ffff810076399980 3448293210 S Ii:004:03 -115 2 < > ffff810076399980 3448313201 C Ii:004:03 0 2 = 0000 > > Then we issue 0x5A, which fails > ffff810076399980 3448313369 S Co:004:00 s 21 00 0000 0000 000c 12 = 5a003f00 > 00000000 08000000 > ffff810076399980 3448316213 C Co:004:00 0 12 > > ffff81007dbe50c0 3448316227 S Bi:004:01 -115 192 < > ffff81007dbe50c0 3448319208 C Bi:004:01 -32 0 > ffff810076399980 3448319794 S Co:004:00 s 02 01 0000 0081 0000 0 > ffff810076399980 3448322202 C Co:004:00 0 0 > > Oh noes, it's key 5 ASC 0x20, so use_10_for_ms is cleared > ffff810076399980 3448322210 S Co:004:00 s 21 00 0000 0000 000c 12 = 03000000 > 12000000 00000000 > ffff810076399980 3448325202 C Co:004:00 0 12 > > ffff810076399980 3448325210 S Bi:004:01 -115 18 < > ffff810076399980 3448328201 C Bi:004:01 0 18 = 70000500 0000000a 00000000 > 20000000 0000 > ffff810076399980 3448328208 S Ii:004:03 -115 2 < > ffff810076399980 3448345202 C Ii:004:03 0 2 = 0000 > > The next command hangs forever (ok, for a minute) > ffff810076399980 3448345220 S Co:004:00 s 21 00 0000 0000 000c 12 = 1a003f00 > c0000000 00000000 > ffff810076399980 3448348203 C Co:004:00 0 12 > > ffff81007dbe59c0 3448348216 S Bi:004:01 -115 192 < > .......... > ffff81007dbe59c0 3478345200 C Bi:004:01 -104 0
So the device claims not to understand MODE SENSE(10) and it hangs when it receives MODE SENSE(6). Bad device! :-) As a last resort, you can always create an unusual_devs entry for it with the US_FL_NO_WP_DETECT flag. > > Speaking of which, and completely OT, I have a request for a usbmon API > > change. When reporting an Isochronous URB, would it be possible to > > present urb->number_of_packets? It would be useful for debugging. > > Hmm. I have to find where to stuff it. > > Anything else you want to see? How about urb->interval? I guess that would be nice also. You can sort of deduce it from the timestamps but getting the actual value will be more accurate. Note that interval applies to Interrupt as well as Isochronous, and the HCD may change its value (so the completion message could have a different interval from the submission message). urb->start_frame (Iso only) is another possibility. Then I think the only thing left is urb->transfer_flags, but that's not likely to be useful. 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 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
