Re: ibmvscsi badness (Re: 2.6.13-mm3)

Anton Blanchard
2005-09-13T01:40:56Z

Hi,

> > 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
> > 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 10468794

What virtual scsi server are you using?

> Interesting. It could be Andi's recent mempolicy.c changes
> (convert-mempolicies-to-nodemask_t.patch) or it could be some recent ppc64
> change or it could be something else ;)
>
> Could the ppc64 guys please take a look? In particular, it would be good
> to know if convert-mempolicies-to-nodemask_t.patch is innocent - I was
> planning on merging that upstream today.

Looking into it now.

Anton