Date: Tue, 3 May 2011 11:35:08 -0600 From: "Kenneth D. Merry" <ken@freebsd.org> To: Dmitry Morozovsky <marck@rinet.ru> Cc: freebsd-stable@freebsd.org Subject: Re: mps driver instability under stable/8 Message-ID: <20110503173508.GA75740@nargothrond.kdm.org> In-Reply-To: <alpine.BSF.2.00.1105032117420.77472@woozle.rinet.ru> References: <alpine.BSF.2.00.1104291145080.29081@woozle.rinet.ru> <20110430211927.GA67374@nargothrond.kdm.org> <alpine.BSF.2.00.1105011434360.29081@woozle.rinet.ru> <20110503034737.GA52416@nargothrond.kdm.org> <alpine.BSF.2.00.1105031736270.77472@woozle.rinet.ru> <alpine.BSF.2.00.1105031852180.77472@woozle.rinet.ru> <alpine.BSF.2.00.1105032117420.77472@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 03, 2011 at 21:28:27 +0400, Dmitry Morozovsky wrote: > > On Tue, 3 May 2011, Dmitry Morozovsky wrote: > > DM> DM> Well, I tried, and unfortunately I can not say that I'm happy after the > DM> DM> upgrade. :( > DM> DM> > DM> DM> Particularly, adapter now takes *VERY* long time (>10 minutes) to initialize, > DM> DM> and report as "ERROR" in BIOS utility (while seeing all 24 disks; however, it > DM> DM> reports 8 x36 expanders instead of one). > DM> DM> > DM> DM> I can't boot the system off this array yet; will experiment further :( > DM> > DM> booted from USB stick, I have constantly repeating > DM> > DM> (ses3:mps0:0:25:0): lost device > DM> (ses3:mps0:0:25:0): removing device entry > DM> ses3 at mps0 bus 0 scbus0 target 25 lun 0 > DM> ses3: <LSI CORP SAS2X36 0417> Fixed Enclosure Services SCSI-5 device > DM> ses3: 600.000MB/s transfers > DM> ses3: Command Queueing enabled > DM> ses3: SCSI-3 SES Device > DM> > DM> for different sesN, which are detected many times: > DM> > DM> <ATA WDC WD2003FYYS-0 1D01> at scbus0 target 0 lun 0 (da0,pass0) > DM> <ATA WDC WD2003FYYS-0 1D01> at scbus0 target 1 lun 0 (da1,pass1) > DM> <ATA WDC WD2003FYYS-0 1D01> at scbus0 target 2 lun 0 (da2,pass2) > DM> <ATA WDC WD2003FYYS-0 1D01> at scbus0 target 3 lun 0 (pass11,da4) > DM> <ATA WDC WD2003FYYS-0 1D01> at scbus0 target 4 lun 0 (pass12,da5) > DM> <ATA WDC WD2003FYYS-0 1D01> at scbus0 target 5 lun 0 (pass9,da3) > DM> <LSI CORP SAS2X36 0417> at scbus0 target 24 lun 0 (pass5,ses3) > DM> <LSI CORP SAS2X36 0417> at scbus0 target 25 lun 0 (pass19,ses5) > DM> <LSI CORP SAS2X36 0417> at scbus0 target 26 lun 0 (pass10,ses4) > DM> <LSI CORP SAS2X36 0417> at scbus0 target 27 lun 0 (pass14,ses7) > DM> <LSI CORP SAS2X36 0417> at scbus0 target 33 lun 0 (pass13,ses6) > DM> <LSI CORP SAS2X36 0417> at scbus0 target 39 lun 0 (pass3,ses0) > DM> <LSI CORP SAS2X36 0417> at scbus0 target 45 lun 0 (pass4,ses1) > DM> <LSI CORP SAS2X36 0417> at scbus0 target 51 lun 0 (pass8,ses2) > DM> <ATA WDC WD2003FYYS-0 1D01> at scbus0 target 55 lun 0 (pass15,da7) > DM> <ATA WDC WD2003FYYS-0 1D01> at scbus0 target 63 lun 0 (pass16,da8) > DM> <ATA WDC WD2003FYYS-0 1D01> at scbus0 target 71 lun 0 (pass17,da9) > DM> <ATA WDC WD2003FYYS-0 1D01> at scbus0 target 79 lun 0 (pass18,da10) > DM> <ATA WDC WD2003FYYS-0 1D01> at scbus0 target 87 lun 0 (pass6,da11) > DM> <ATA WDC WD2003FYYS-0 1D01> at scbus0 target 95 lun 0 (pass20,da12) > DM> <ATA WDC WD2003FYYS-0 1D01> at scbus0 target 103 lun 0 (pass21,da13) > > Well, using > http://kb.lsi.com/KnowledgebaseArticle16414.aspx > I downgraded to version 8-fixed, and at least topology errors disappear. > > Just booted successfully (errm, it was a few nervous hours, to be honest :) > > Now I have in verbose kernel messages > > mps0: <LSI SAS2008> port 0xc000-0xc0ff mem > 0xfb43c000-0xfb43ffff,0xfb440000-0xfb47ffff irq 16 at device 0.0 on pci2 > mps0: Reserved 0x4000 bytes for rid 0x14 type 3 at 0xfb43c000 > mps0: Firmware: 08.00.00.00 > mps0: IOCCapabilities: 185c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,IR> > mps0: attempting to allocate 1 MSI-X vectors (15 supported) > msi: routing MSI-X IRQ 256 to local APIC 0 vector 49 > mps0: using IRQ 256 for MSI-X > mps0: [MPSAFE] > mps0: [ITHREAD] Sorry you ran into all of those problems! Needless to say I haven't seen that with the 9.0 firmware in my environment, but then again I've got a different setup. > Will see whether it helps. Yes. I know the 8.0 firmware also works well. The only issue I ran into there was the topology issues that I'm guessing they fixed in that build. If the firmware doesn't fix it, we'll go down the path of trying to see why the IOC fault is happening. Ken -- Kenneth Merry ken@FreeBSD.ORG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110503173508.GA75740>