What happened to your line wrapping? On Wed, 20 Mar 2013, Mike wrote: > Alan Stern <stern@...> writes: > > Did you stop the trace too > quickly? It looks like there should > be more > > data. > > My log is WAY bigger, but I shortened > it, because I got an error saying my > mail is too long. But the last part > seems to repeat anyway, so I thought > it's ok to let it off. If the part you cut off is just a lot of repeats of the last 19 or so lines then you were right to leave it out. > If you like, I could send the log as > an attachment via email. > > > You said that you are using an > Ubuntu kernel based 3.2, right? That > > may be the problem. This looks > like an issue that was fixed in the > 3.8 > > kernel by commit 53ad570be625 > ([SCSI] sd: Use SCSI read/write(16) > with > > > 32-bit LBA drives). > > > > I don't know if your Ubuntu kernel > includes that commit. You ought to > > try booting a newer kernel, > something based on 3.8. It may fix > your > > problem. > > > > Thanks a lot. As it is a LTS version, > I don't want to boot another kernel. > But I will ask them to backport this > patch in their 3.2 kernel. > > Are you sure about the fix or do you > want to have a look at a longer > usbmon log? Not if the log contains only a lot of repeated stuff. I can't be certain that the commit will fix your problem, but it seems likely. The commit was originally written in order to fix a similar problem with a JMicron USB-SATA bridge attached to a disk larger than 2 TB. Of course, if the kernel you are using already contains that commit then we'll have to try something else. My guess is that it doesn't. 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
