Re: ibmvscsi badness (Re: 2.6.13-mm3)

Dave C Boutcher
2005-09-13T05:10:10Z

On Mon, Sep 12, 2005 at 04:10:13PM -0700, Andrew Morton wrote:
> serue@us.ibm.com wrote:
> >
> > Trying to get 2.6.13-mm running on a power5 lpar, I'm
> > having scsi problems.
>
> You should have cc'ed the scsi mailing list, no?
>
> > With -mm2, I only get things like:
> > sd 0:0:0:0: SCSI error: return code = 0x8000002
> > sda: Current: sense key: Aborted Command
> > Additional sense: No additional sense information
> > Info fld=0x0
> > end_request: I/O error, dev sda, sector 10468770
> > sd 0:0:0:0: SCSI error: return code = 0x8000002
> > sda: Current: sense key: Aborted Command
> > Additional sense: No additional sense information
> > Info fld=0x0
> > end_request: I/O error, dev sda, sector 10468778
> > sd 0:0:0:0: SCSI error: return code = 0x8000002
> > sda: Current: sense key: Aborted Command
> > Additional sense: No additional sense information
> > Info fld=0x0
> > end_request: I/O error, dev sda, sector 10468786

Well, I know why you get these errors with mm2. mm2 ibmvscsi
allows transferring longer scatterlists between the initiator
and the target than before. However that breaks compatibility
with the older target that was shipped with SLES 9. Longer
scatterlists ARE supported with the target I recently posted
as an RFC.

I'm thinking we'll have to add a module paramter to limit
scatterlist sizes that defaults to the old behaviour. Let
me sleep on that and kick it around with Linda tomorrow and
we'll figure out some kind of solution.

As Anton already reported, mm3 has an additional set of
breakages...

--
Dave Boutcher