Date: Wed, 14 Dec 2016 11:36:23 -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: <5fcf45f2ccbf3b4b195bfc16164bc843@mail.gmail.com> In-Reply-To: <95d92193-ba66-ba40-e417-01f29510e73c@centrale-marseille.fr> References: <2ae74eaa-80da-2b81-900b-9b9d21080e5c@centrale-marseille.fr> <95d92193-ba66-ba40-e417-01f29510e73c@centrale-marseille.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
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 > -----Original Message----- > From: owner-freebsd-scsi@freebsd.org [mailto:owner-freebsd- > scsi@freebsd.org] On Behalf Of geoffroy desvernay > Sent: Wednesday, December 14, 2016 10:49 AM > To: freebsd-scsi@freebsd.org > Subject: Re: mpr(4) bug ? > > Did I say something silly, is there an obvious thing I'm missing ? Isn't > it the right > mailing list to post this ? > > The very same setup works flawlessly under debian or centos=E2=80=A6 Isn'= t there > something to investigate ? > > Is there someone from Avago around ? > > Thank you for reading=E2=80=A6 > > On 12/12/2016 03:30 PM, geoffroy desvernay wrote: > > Hi all, > > > > First, I'm not fluently speaking SCSI nor kernel-c, so please don't > > byte too hard if I'm missing something obvious :) > > > > I tried some thing before posting here, from testing the hardware > > under linux (it work flawlessly there) and vendor's tests software, > > changing the adapter (for a different one, but with same chipset, > > that's all I have), upgrading firmwares where available (card and dell > > enclosure), trying to read mpr(4)'s code=E2=80=A6 well this is beyond m= y > > knowledge. > > > > Hardware: dell PowerEgde R430 with an LSI SAS3008 card and an MD1420 > > enclosure with 24 2T Seagate sas drives. > > This machine also have an embedded SAS3008 (dell perc H330) in > > non-raid mode (mrsas driver) with 4 SSD drives to be used as ZFS > > cache/log=E2=80=A6 > > > > System: FreeBSD 11.0-RELEASE-p3 > > > > Please tell me if there are tests I could do, patches to try, or ? > > Currently compiling 11-STABLE kernel with sys/dev/mpr from CURRENT, > > but with no clues=E2=80=A6 > > > > #pciconf -lv: > > mpr0@pci0:4:0:0: class=3D0x010700 card=3D0x1f461028 chip=3D0x009= 71000 > > rev=3D0x02 hdr=3D0x00 > > vendor =3D 'LSI Logic / Symbios Logic' > > device =3D 'SAS3008 PCI-Express Fusion-MPT SAS-3' > > class =3D mass storage > > subclass =3D SAS > > > > Symptoms: any zpool create fails with > > # zpool create ztest raidz da20 da21 da22 cannot create 'ztest': > > invalid argument for this pool operation > > > > # dmesg show a buncf of messages like this one: > > (da22:mpr0:0:26:0): READ(10). CDB: 28 00 e8 e0 88 af 00 00 01 00 > > (da22:mpr0:0:26:0): CAM status: SCSI Status Error > > (da22:mpr0:0:26:0): SCSI status: Check Condition > > (da22:mpr0:0:26:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid > > command operation code) > > (da22:mpr0:0:26:0): Error 22, Unretryable error > > > > (see http://dgeo.perso.ec-m.fr/mpr_fail.txt for full related dmesg) > > > > # camcontrol devlist 2 seems normal to me: > > <ATA INTEL SSDSC2BX20 DL2B> at scbus1 target 0 lun 0 (pass0,da0) > > <ATA INTEL SSDSC2BX20 DL2B> at scbus1 target 1 lun 0 (pass1,da1) > > <ATA INTEL SSDSC2BA40 DL2B> at scbus1 target 2 lun 0 (pass2,da2) > > <ATA INTEL SSDSC2BA40 DL2B> at scbus1 target 3 lun 0 (pass3,da3) > > <DP BP13G+ 2.23> at scbus1 target 32 lun 0 > > (pass4,ses0) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 8 lun 0 (pass5,da4) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 9 lun 0 (pass6,da5) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 10 lun 0 (pass7,da6= ) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 11 lun 0 (pass8,da7= ) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 12 lun 0 (pass9,da8= ) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 13 lun 0 > > (pass10,da9) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 14 lun 0 > > (pass11,da10) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 15 lun 0 > > (pass12,da11) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 16 lun 0 > > (pass13,da12) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 17 lun 0 > > (pass14,da13) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 18 lun 0 > > (pass15,da14) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 19 lun 0 > > (pass16,da15) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 20 lun 0 > > (pass17,da16) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 21 lun 0 > > (pass18,da17) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 22 lun 0 > > (pass19,da18) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 23 lun 0 > > (pass20,da19) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 24 lun 0 > > (pass21,da20) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 25 lun 0 > > (pass22,da21) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 26 lun 0 > > (pass23,da22) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 27 lun 0 > > (pass24,da23) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 28 lun 0 > > (pass25,da24) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 29 lun 0 > > (pass26,da25) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 30 lun 0 > > (pass27,da26) > > <SEAGATE ST2000NX0433 NS02> at scbus2 target 31 lun 0 > > (pass28,da27) > > <DELL MD1420 1.07> at scbus2 target 32 lun 0 > > (pass29,ses1) > > <AHCI SGPIO Enclosure 1.00 0001> at scbus7 target 0 lun 0 > > (pass30,ses2) > > > > With dev.mpr.0.debug_level: 1023, I tried a simple dd test: dd reports > > success if bs < 127k; fails if >=3D 128k (in both tests there are > > ILLEGAL REQUEST in logs): > > dd if=3D/tmp/rnd of=3D/dev/da20 bs=3D127k: > > http://dgeo.perso.ec-m.fr/dd_bs_127k.debug.log > > > > bs=3D128k: http://dgeo.perso.ec-m.fr/dd_bs_128k.debug.log > > > > > > > -- > 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?5fcf45f2ccbf3b4b195bfc16164bc843>