On Sun, Jan 10, 2010 at 7:29 AM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > On Sat, 9 Jan 2010, Ryan May wrote: > >> Oh, ok. I'll get you those when I get the chance. In the meanwhile, >> here is the output from dd | hexdump -C. > > Wow. Are you sure you issued the same command for the patched and > unpatched versions of 2.6.31? The outputs are completely different. > > Assuming the computer is sending the same commands to the device (which > you can check by doing a "blockdev --flushbufs /dev/sdb" before the > "dd" and using usbmon), the device itself must be behaving very > strangely. Or else the kernel's block cache has gotten messed up, > which is very unlikely. Well, I'm not sure that it's the device itself, given that the purpose of the entry in unusual_dev.h is adjusting the number of blocks reported by the drive. To my untrained eyes, it would seem that the with unpatched 2.6.31, the drive is reading one block off from where it should be. But that just be the crazy rambling of a non-kernel hacker. (Still working on getting the full set of the usbmon traces.) Ryan -- Ryan May Graduate Research Assistant School of Meteorology University of Oklahoma -- 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
