Date: Wed, 14 Dec 2016 12:44:45 -0700 From: Stephen Mcconnell <stephen.mcconnell@broadcom.com> To: geoffroy desvernay <dgeo@centrale-marseille.fr>, freebsd-scsi@freebsd.org Subject: RE: mpr(4) bug ? Message-ID: <853ce95f576625f247b625268a8a8b98@mail.gmail.com> In-Reply-To: <8d5ee1d2-e7c4-8a3f-5f8d-b1ef29995e9b@centrale-marseille.fr> References: <2ae74eaa-80da-2b81-900b-9b9d21080e5c@centrale-marseille.fr> <95d92193-ba66-ba40-e417-01f29510e73c@centrale-marseille.fr> <5fcf45f2ccbf3b4b195bfc16164bc843@mail.gmail.com> <489d892d-7734-e148-98d3-77bc6e62bac1@centrale-marseille.fr> <8d5ee1d2-e7c4-8a3f-5f8d-b1ef29995e9b@centrale-marseille.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
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 yo= u should be getting a different error (ASC of 21 instead of 20). And one othe= r 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, mayb= e you can do that and see what happens. Steve > -----Original Message----- > From: owner-freebsd-scsi@freebsd.org [mailto:owner-freebsd- > scsi@freebsd.org] On Behalf Of geoffroy desvernay > Sent: Wednesday, December 14, 2016 12:00 PM > To: freebsd-scsi@freebsd.org > Subject: Re: mpr(4) bug ? > > Oups, just overwritten it: it was truncated=E2=80=A6 the new may be more = complete=E2=80=A6 > > 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=3D0xFFFF > > dd if=3D/dev/zero of=3D/dev/da20 bs=3D1M and > > > > http://dgeo.perso.ec-m.fr/mfi0_dd_dmesg.log > > > > Do you prefer bs=3D127k or bs=3D128k ? > > > > > -- > geoffroy desvernay > C.R.I - Administration syst=C3=A8mes et r=C3=A9seaux Ecole Centrale de Ma= rseille > Tel: (+33|0)4 91 05 45 24 > Fax: (+33|0)4 91 05 45 98 > dgeo@centrale-marseille.fr >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?853ce95f576625f247b625268a8a8b98>