mpr(4) bug ?

[Stephen Mcconnell]

I don't see anything new that helps. Again, the driver looks like it's
operating properly - just reporting the error that it gets. All I can think
of is that the requested LBA is out of range, but if that were that case you
should be getting a different error (ASC of 21 instead of 20). And one other
thing I see is that the debug output from MPR only shows errors for
da20:mpr0:0:24:0. The errors at the beginning of the log show several
drives, so I'm not sure what to make of that.

Are you using the same disks for FreeBSD as you are for Linux? If not, maybe
you can do that and see what happens.

Steve

> -----Original Message-----
> From: owner-freebsd-scsi at freebsd.org [mailto:owner-freebsd-
> scsi at freebsd.org] On Behalf Of geoffroy desvernay
> Sent: Wednesday, December 14, 2016 12:00 PM
> To: freebsd-scsi at freebsd.org
> Subject: Re: mpr(4) bug ?
>
> Oups, just overwritten it: it was truncated… the new may be more complete…
>
> On 12/14/2016 07:57 PM, geoffroy desvernay wrote:
> > On 12/14/2016 07:36 PM, Stephen Mcconnell via freebsd-scsi wrote:
> >> Hi Geoffroy,
> >>
> >> I looked through the logs. It's strange. I don't know why there would
> >> be sense data for 'Invalid OP Code' for the read(10)/write(10)
> >> commands. The driver looks like it's doing everything correctly. It's
> >> just passing up the error and the command fails. Can you retry with
> debug_level set to 0xFFFF?
> >> It might not give more info, but we can see.
> >>
> >> Steve
> >>
> >
> > Thank you :)
> >
> > here is a dmesg exerpt, after
> >
> > sysctl dev.mpr.0.debug_level=0xFFFF
> > dd if=/dev/zero of=/dev/da20 bs=1M and
> >
> > http://dgeo.perso.ec-m.fr/mfi0_dd_dmesg.log
> >
> > Do you prefer bs=127k or bs=128k ?
> >
>
>
> --
> geoffroy desvernay
> C.R.I - Administration systèmes et réseaux Ecole Centrale de Marseille
> Tel: (+33|0)4 91 05 45 24
> Fax: (+33|0)4 91 05 45 98
> dgeo at centrale-marseille.fr
>