On Thu, Sep 27, 2007 at 08:45:09AM +0200, Stefan Richter wrote: > Al Viro wrote: > > On Wed, Sep 26, 2007 at 10:55:11PM +0200, Stefan Richter wrote: > >> Strange. I haven't heard of this before. From which vendor and model > >> is the device, and do you know which chip is on its IDE bridge board? > > > > I've seen it, all right. 8 bytes stuck in FIFO, pl3507 IDE bridge, > > and judging by google search that turd is b0rken regardless of the > > OS (along the lines of "works under Windows if you power-cycle it > > once in about half an hour"). > > > > Suggested fix: use as a barf-bag; the authors of that thing certainly had > > done that. > > Sounds plausible. I wasn't aware of the particular 8-byte-garbage > symptom (or heard of it and forgot it). IIRC, it can be triggered by the second INQUIRY during the same firewire session (i.e. device survives only one INQUIRY after login and using e.g. scsiinfo -i afterwards triggers that behaviour). Can't verify that, since the hardware in question had been met its end (after a week spent debugging that mess). It was of the "can't upgrade the firmware" variety and frankly, it's easier to spend $20 on a working enclosure than to waste time on that dreck. - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
