From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Gustavo Guillermo Pérez" <gustavo@compunauta.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
Andrew Morton <akpm@osdl.org>,
linux-scsi@vger.kernel.org
Subject: Re: SCSI trow USB-STORAGE or SBP2 Debug for buggy device Kernels 2.6.X
Date: Tue, 25 Apr 2006 08:09:17 +0200 [thread overview]
Message-ID: <444DBD0D.9010309@s5r6.in-berlin.de> (raw)
In-Reply-To: <200604241712.26445.gustavo@compunauta.com>
Gustavo Guillermo Pérez wrote:
> El Lunes, 24 de Abril de 2006 17:02, James Bottomley escribió:
>>So, I could change the long write in progress to a retry. However, I
>>suspect the reason we got that return is because this device is untagged
>>(doesn't accept multiple commands at once) and perhaps a better fix
>>might be to reduce the queue depth down to one to prevent more than one
>>command being outstanding at any one time.
>
> It would not be better to include some handling on the black list? it means
> doing a new BLACK_CONST to handle just this special case?.
For now you can and should test a queue depth of one via sbp2:
# modprobe sbp2 serialize_io=1
But isn't usb-storage's queue depth already 1?
Dou you use all the different Pioneer drives with the same
IDE/USB+FireWire bridge or do you have different bridges?
--
Stefan Richter
-=====-=-==- -=-- ==--=
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-04-25 6:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 15:29 SCSI trow USB-STORAGE or SBP2 Debug for buggy device Kernels 2.6.X Gustavo Guillermo Pérez
2006-04-24 18:38 ` James Bottomley
2006-04-24 21:30 ` Gustavo Guillermo Pérez
2006-04-24 22:02 ` James Bottomley
2006-04-24 22:12 ` Gustavo Guillermo Pérez
2006-04-25 6:09 ` Stefan Richter [this message]
2006-04-25 21:41 ` Gustavo Guillermo Pérez
2006-04-25 21:48 ` James Bottomley
2006-04-27 17:40 ` Gustavo Guillermo Pérez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=444DBD0D.9010309@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=gustavo@compunauta.com \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox