From: Patrick Mansfield <patmans@us.ibm.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Radovan Garabik <garabik@kassiopeia.juls.savba.sk>,
USB Storage list <usb-storage@lists.one-eyed-alien.net>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [usb-storage] Re: MPIO HS200 Gigabox weird behaviour again
Date: Fri, 11 Feb 2005 11:07:41 -0800 [thread overview]
Message-ID: <20050211190741.GA8641@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0502111326540.937-100000@ida.rowland.org>
On Fri, Feb 11, 2005 at 01:31:30PM -0500, Alan Stern wrote:
> On Fri, 11 Feb 2005, James Bottomley wrote:
>
> > On Fri, 2005-02-11 at 11:00 -0500, Alan Stern wrote:
> > > SCSI developers: Is there any hope of this?
> >
> > Well, IBM also has some old buggy piece of hardware that apparently
> > gives fatal errors but actually wants them retried:
> >
> > http://marc.theaimsgroup.com/?t=110088696100005
> >
> > After a bit of argument, they agreed to do it as a blacklist flag, so
> > you should be able to add the same flag to your gigabox.
> >
> > I planned to put the patch in just as soon as they managed to send the
> > patch unmangled by a mailer, but they went very quiet.
>
> Thanks, James.
>
> Radovan: Below is an updated version of the patch James mentioned, with an
> entry included for your Gigabox drive. It's meant to apply to
> 2.6.11-rc3-bk5, but it will probably go with older kernels too. Try it
> out and let me know how it works. If it solves your problem, I'll submit
> it for inclusion in the official kernel.
Do you have the asc/ascq for the USB device?
Longer term, it would be nice to have a black list modifiable via sysfs
(similiar to the scsi devinfo one) with a vendor + model + sense key + asc
+ ascq, for both this USB device and for the IBM one. AFAIUI, the IBM
ESS/2105 really wants certain hardware errors retried not all of them, I
don't know if the IBM ESS/storage developers were OK with Martin's patch
(I never see responses from them to anything posted on linux-scsi).
The sense black list could be used for quirks plus vendor specific
asc/ascq values. It could also be used by dm multipath, if error codes
(like Mike C's old patch) and not sense data were passed up.
James - would you be OK with such an approach?
It should be populated after loading scsi_mod, but before loading HBA
drivers (the same is true for devinfo); I think this means manually
loading scsi_mod, populate the tables, then allow hotplug loading of HBA
drivers.
We still need a nice way to display and modify a list or array in sysfs (for
both the devinfo or this asc/ascq table).
-- Patrick Mansfield
next prev parent reply other threads:[~2005-02-11 19:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050210134432.GA12229@kassiopeia.juls.savba.sk>
2005-02-11 16:00 ` [usb-storage] Re: MPIO HS200 Gigabox weird behaviour again Alan Stern
2005-02-11 16:18 ` James Bottomley
2005-02-11 18:31 ` Alan Stern
2005-02-11 19:07 ` Patrick Mansfield [this message]
2005-02-11 19:41 ` Alan Stern
2005-02-16 14:37 ` Radovan Garabik
2005-02-16 16:53 ` [PATCH as468] Retry supposedly "unrecoverable" hardware errors Alan Stern
2005-02-17 4:27 ` Douglas Gilbert
2005-02-17 5:06 ` Douglas Gilbert
2005-02-17 15:20 ` Alan Stern
2005-02-17 15:11 ` James Bottomley
2005-02-18 0:49 ` Douglas Gilbert
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=20050211190741.GA8641@us.ibm.com \
--to=patmans@us.ibm.com \
--cc=garabik@kassiopeia.juls.savba.sk \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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