On Tue, 23 Feb 2010, Oliver Neukum wrote: > Hi, > > I've been looking at the sense stuff coming from a resumed device. > And this stuff makes no sense (no pun intended) > ffff88010e685440 575751499 S Bo:2:003:1 -115 31 = 55534243 64000000 12000000 80000603 00000012 00000000 00000000 000000 > ffff88010e685440 575751653 C Bo:2:003:1 0 31 > > ffff8800b1b7eb00 575751789 S Bi:2:003:2 -115 18 < > ffff8800b1b7eb00 575751921 C Bi:2:003:2 0 18 = 00000000 00000000 00000000 00000000 0000 > > Autosense is done. > Up to now everything was normal. An error had occured but was handled. > But now the device returns a sense buffer of all zeros. > > Feb 23 15:58:41 vanamonde kernel: usb-storage: Bulk Status S 0x53425355 T 0x64 R 0 Stat 0x0 > Feb 23 15:58:41 vanamonde kernel: usb-storage: -- Result from auto-sense is 0 > Feb 23 15:58:41 vanamonde kernel: usb-storage: -- code: 0xf0, key: 0x6, ASC: 0x28, ASCQ: 0x0 > Feb 23 15:58:41 vanamonde kernel: usb-storage: Unit Attention: Not ready to ready change, medium may have changed > Feb 23 15:58:41 vanamonde kernel: usb-storage: scsi cmd done, result=0x2 > > But the storage driver reports something else entirely. > Somebody please tell me what I am overlooking. What kernel version and what HCD are you using? This could be related to the new sg-list processing, which involved changes to message.c, ehci-q.c, and usbmon. Maybe the data is getting transmitted correctly but usbmon is looking in the wrong place. 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
