Re: [PATCH] JMicron JM20337 USB-SATA data corruption bugfix - device152d:2338

From: Alan Stern
Date: Tue Jul 22 2008 - 22:38:46 EST

On Tue, 22 Jul 2008, Tomas Styblo wrote:

> * Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> [Tue, 22 Jul 2008]:
> > On Mon, 21 Jul 2008, Robert Hancock wrote:
> > > > this message includes a patch that provides a workaround for
> > > > a silent data corruption bug caused by incorrect error handling in
> > > > the JMicron JM20337 Hi-Speed USB to SATA & PATA Combo Bridge chipset,
> > > > USB device id 152d:2338.
> >
> > The two of you should read through
> >
> >
> >
> > which concerns this very problem.
> I had found this bugreport and read through it before I posted my
> patch. I don't think this is the same problem. The error messages
> and the description of the problem are different from what I've
> been trying to fix.

Maybe the initial descriptions are. If you read through the entire
report, though, you'll see that the underlying problems are exactly
the same:

A READ fails to transfer all the data requested. The device
sends back Check Condition status, but the sense data is all
0, indicating that nothing was wrong. The system does not
retry the READ, leading to data corruption.

A WRITE fails and times out after 30 seconds. The system
tries to reset the device, but the reset fails.

The system doesn't detect the first problem for two reasons: The
scsi_eh_prep_cmnd routine fails to preserve scmd->underflow, and
usb-storage fails to check for underflow when the device returns Check
Condition status. The Bugzilla report contains fixes for both of
these, and they solve the problem.

The second problem is harder. The device is supposed to send a STALL
to cut the WRITE short -- and a USB trace under Windows seems to
indicate that it does -- but under Linux no STALL is received. I
don't know why not. But since Linux does not respond in the way the
device expects, the device crashes.

> Anyway, I'll send the patch to this person so he can try it.
> I guess it won't fix his problem. This patch is much simpler and doesn't
> need any delays - I really think this is a different situation.

It isn't. And your patch is an ad-hoc correction that doesn't address
the true underlying reasons for the errors.

You should also try adding the delay mentioned in the bug report.
There's an excellent chance it will also prevent your problems.

> I sometimes experience the problems described by this person, as I
> noted in the first message with the patch. When these "reset high
> speed USB device" messages appear, it is usually necessary to
> disconnect and power off the device.

Because the device's firmware has crashed. That's why the reset fails.

Alan Stern

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at