But under some conditions, the last TEST UNIT READY is not being sent
and because of that, on this device: Kingston DT 101 G2, the drive's
activity light keeps on blinking even though nothing is being done (no
read/writes/inquiries).
In addition to Matt's comments, it's worth pointing out that this
behavior is an oddity of the device. Hosts are not obliged to send
TEST UNIT READY commands at any time, and it's not fair to say that
lack of such commands is a bug that needs to be fixed.
What I thought of as a bug is the difference in behaviour between
count=96 and count=97. It just looks weird. It's not about the lack of
the command, it's more about the command not being sent regularly.
And the same device with its oddities works alright in an older Linux.
If I find the code that caused that regression, I can patch at least my
kernel and let the developers know.
Anyway, Matt made it clear that it's not linux-usb related. So I'm going
up the stack. His message helped a lot.
Eduardo.
PD: By the way, nothing to do with fairness and I don't remember having
said it had to be fixed, I guess you have wontfix, worksforme, invalid
and tags like that. I keep on using the device and try to ignore the
light :). But since it's no longer working as expected, I thought I'd
report it, just in case. That's how I open source gets better and
better, false positives included.
--
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
