Correcting myself. I apparently don't have this adapter in any of my other Illumos systems. This has the 3216 chip, my other systems have the 3008.
Any running one of these HBAs on Illumos? Googling I'm only finding my old email on this list asking about these in 2017. On that old system, I swapped them out to get the system going. -Chip On Wed, May 12, 2021 at 8:22 AM Schweiss, Chip <c...@innovates.com> wrote: > I had triggered the fault manager to disable the adapter by allowing it to > boot with no firmware on the HBA while I was redoing my FreeDOS ISO with > the correct firmware. Fixing that, the HBA will still not initialize and > now the boot hangs. The same hang happens when booting OmniOSce r151030,36 > or 38 isos. Also tried downgrading the firmware. > > I have this same HBA in other servers running OmniOSce r151030, the only > significant difference in this system is the AMD Rome 2 (AMD EPYC 7402P) > instead of Intel CPUs. > > With debug boot enabled, the hang happens here: > ... > /pci@6f,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0): > MPT Firmware version v12.0.0.0 (SAS3216) > /pci@6f,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0): > mpt_sas0 SAS 3 Supported > pseudo-device: llc10 > llc10 is /pseudo/llc1@0 > pseudo-device: lockstat0 > lockstat0 is /pseudo/lockstat@0 > pseudo-device: lofi0 > lofi0 is /pseudo/lofi@0 > pseudo-device: profile0 > profile0 is /pseudo/profile@0 > pseudo-device: ramdisk1024 > ramdisk1024 is /pseudo/ramdisk@1024 > pseudo-device: sdt0 > sdt0 is /pseudo/sdt@0 > pseudo-device: stmf0 > stmf0 is /pseudo/stmf@0 > pseudo-device: systrace0 > systrace0 is /pseudo/systrace@0 > pseudo-device: ucode0 > ucode0 is /pseudo/ucode@0 > Block device: blkdev@w5CD2E453E6770100,0, blkdev0 > blkdev0 is /pci@a6,0/pci1022,1483@1,1/pci8086,4802@0 > /blkdev@w5CD2E453E6770100,0 > /pci@a6,0/pci1022,1483@1,1/pci8086,4802@0/blkdev@w5CD2E453E6770100,0 > (blkdev0) online > pseudo-device: bpf0 > bpf0 is /pseudo/bpf@0 > /pci@6f,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0): > mpt0: IOC Operational. > pseudo-device: fssnap0 > fssnap0 is /pseudo/fssnap@0 > pseudo-device: inotify0 > inotify0 is /pseudo/inotify@0 > pseudo-device: nsmb0 > nsmb0 is /pseudo/nsmb@0 > pseudo-device: signalfd0 > signalfd0 is /pseudo/signalfd@0 > pseudo-device: timerfd0 > timerfd0 is /pseudo/timerfd@0 > WARNING: /pci@6f,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0): > mptsas_get_sas_io_unit_page_hndshk failed! > WARNING: /pci@6f,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0): > attach failed > > Please let me know what more information I can provide to debug this > problem. > > Thanks! > -Chip > > > > On Tue, May 11, 2021 at 3:44 PM Schweiss, Chip <c...@innovates.com> wrote: > >> Digging a bit deeper. >> >> It is showing up in 'prtconf -Dd' in OmniOS: >> >> pci1022,1483 (pciex1022,1483) [Advanced Micro Devices, Inc. [AMD] >> Starship/Matisse GPP Bridge], instance #17 (driver name: pcieb) >> pci1000,3180 (pciex1000,c9) [Broadcom / LSI SAS3216 >> PCI-Express Fusion-MPT SAS-3] (driver name: mpt_sas) >> >> Disks are not being discovered. >> >> In the system log: >> >> May 11 14:03:46 localhost scsi: [ID 365881 kern.info] /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas0 supports >> power management. >> May 11 14:03:46 localhost scsi: [ID 365881 kern.info] /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas0 supports >> power management. >> May 11 14:03:46 localhost scsi: [ID 107833 kern.warning] WARNING: /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas bad flash >> signature >> May 11 14:03:46 localhost scsi: [ID 107833 kern.warning] WARNING: /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas chip >> initialization >> failed >> May 11 14:03:46 localhost scsi: [ID 107833 kern.warning] WARNING: /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011attach failed >> May 11 14:03:46 localhost scsi: [ID 365881 kern.info] /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas0 supports >> power management. >> May 11 14:03:46 localhost scsi: [ID 365881 kern.info] /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas0 supports >> power management. >> May 11 14:03:46 localhost scsi: [ID 107833 kern.warning] WARNING: /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas bad flash >> signature >> May 11 14:03:46 localhost scsi: [ID 107833 kern.warning] WARNING: /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas chip >> initialization >> failed >> May 11 14:03:46 localhost scsi: [ID 107833 kern.warning] WARNING: /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011attach failed >> May 11 14:03:46 localhost fmd: [ID 377184 daemon.error] SUNW-MSG-ID: >> PCIEX-8000-0A, TYPE: Fault, VER: 1, SEVERITY: Critical#012EVENT-TIME: Tue >> May 11 09: >> 03:45 CDT 2021#012PLATFORM: AS--1114S-WN10RT, CSN: S407507X1210260, >> HOSTNAME: mir-zfs06#012SOURCE: eft, REV: 1.16#012EVENT-ID: >> 792045f1-b22c-42b2-a835-c5 >> 08757005c1#012DESC: A problem was detected for a PCIEX device.#012 Refer >> to http://illumos.org/msg/PCIEX-8000-0A for more >> information.#012AUTO-RESPONSE: >> One or more device instances may be disabled#012#012IMPACT: Loss of >> services provided by the device instances associated with this >> fault#012#012REC-ACTI >> ON: Schedule a repair procedure to replace the affected device. Use >> fmadm faulty to identify the device or contact your illumos distribution >> team for su >> pport.#012 >> May 11 14:03:47 localhost ahci: [ID 432157 kern.warning] WARNING: ahci2: >> Cannot allocate ports structure >> May 11 14:03:47 localhost scsi: [ID 365881 kern.info] /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas0 supports >> power management. >> May 11 14:03:47 localhost scsi: [ID 365881 kern.info] /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas0 supports >> power management. >> May 11 14:03:47 localhost scsi: [ID 107833 kern.warning] WARNING: /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas bad flash >> signature >> May 11 14:03:47 localhost scsi: [ID 107833 kern.warning] WARNING: /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas chip >> initialization >> failed >> May 11 14:03:47 localhost scsi: [ID 107833 kern.warning] WARNING: /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011attach failed >> May 11 14:03:47 localhost scsi: [ID 365881 kern.info] /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas0 supports >> power management. >> May 11 14:03:47 localhost scsi: [ID 365881 kern.info] /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas0 supports >> power management. >> May 11 14:03:47 localhost scsi: [ID 107833 kern.warning] WARNING: /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas bad flash >> signature >> May 11 14:03:47 localhost scsi: [ID 107833 kern.warning] WARNING: /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas chip >> initialization >> failed >> May 11 14:03:47 localhost scsi: [ID 107833 kern.warning] WARNING: /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011attach failed >> May 11 14:03:47 localhost scsi: [ID 365881 kern.info] /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas0 supports >> power management. >> May 11 14:03:47 localhost scsi: [ID 365881 kern.info] /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas0 supports >> power management. >> May 11 14:03:47 localhost scsi: [ID 107833 kern.warning] WARNING: /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas bad flash >> signature >> May 11 14:03:47 localhost scsi: [ID 107833 kern.warning] WARNING: /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011mptsas chip >> initialization >> failed >> May 11 14:03:47 localhost scsi: [ID 107833 kern.warning] WARNING: /pci@6f >> ,0/pci1022,1483@1,1/pci1000,3180@0 (mpt_sas0):#012#011attach failed >> >> >> >> >> On Tue, May 11, 2021 at 3:27 PM Schweiss, Chip <c...@innovates.com> >> wrote: >> >>> I have a new 9306-16e that is not showing up in OmniOS r151038. It is >>> working fine when booting to CentOS 7. It is not even listed in lspci on >>> OmniOS. These HBAs were added quite some time ago. The ID doesn't seem >>> to have changed (1000:c9). >>> >>> I upgraded the firmware to version 16 before installing OmniOS. >>> >>> Any help on getting this HBA working under OmniOS would be appreciated. >>> >>> Thanks, >>> -Chip >>> >>> From CentOS 7 'lspci -vvv -nn': >>> >>> 81:00.0 Serial Attached SCSI controller [0107]: Broadcom / LSI SAS3216 >>> PCI-Express Fusion-MPT SAS-3 [1000:00c9] (rev 01) >>> Subsystem: Broadcom / LSI Device [1000:3180] >>> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- >>> ParErr- Stepping- SERR- FastB2B- DisINTx+ >>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- >>> <TAbort- <MAbort- >SERR- <PERR- INTx- >>> Latency: 0, Cache Line Size: 64 bytes >>> Interrupt: pin A routed to IRQ 551 >>> NUMA node: 0 >>> Region 0: I/O ports at b000 [size=256] >>> Region 1: Memory at f0100000 (64-bit, non-prefetchable) >>> [size=64K] >>> Expansion ROM at f0000000 [disabled] [size=1M] >>> Capabilities: [50] Power Management version 3 >>> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA >>> PME(D0-,D1-,D2-,D3hot-,D3cold-) >>> Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- >>> Capabilities: [68] Express (v2) Endpoint, MSI 00 >>> DevCap: MaxPayload 4096 bytes, PhantFunc 0, Latency L0s >>> <64ns, L1 <1us >>> ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ >>> SlotPowerLimit 75.000W >>> DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ >>> Unsupported- >>> RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop+ >>> FLReset- >>> MaxPayload 512 bytes, MaxReadReq 512 bytes >>> DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- >>> TransPend- >>> LnkCap: Port #0, Speed 8GT/s, Width x8, ASPM not >>> supported, Exit Latency L0s <2us, L1 <4us >>> ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ >>> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ >>> ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- >>> LnkSta: Speed 8GT/s, Width x8, TrErr- Train- SlotClk+ >>> DLActive- BWMgmt- ABWMgmt- >>> DevCap2: Completion Timeout: Range BC, TimeoutDis+, >>> LTR-, OBFF Not Supported >>> DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, >>> LTR-, OBFF Disabled >>> LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- >>> SpeedDis- >>> Transmit Margin: Normal Operating Range, >>> EnterModifiedCompliance- ComplianceSOS- >>> Compliance De-emphasis: -6dB >>> LnkSta2: Current De-emphasis Level: -3.5dB, >>> EqualizationComplete+, EqualizationPhase1+ >>> EqualizationPhase2+, EqualizationPhase3+, >>> LinkEqualizationRequest- >>> Capabilities: [a8] MSI: Enable- Count=1/1 Maskable+ 64bit+ >>> Address: 0000000000000000 Data: 0000 >>> Masking: 00000000 Pending: 00000000 >>> Capabilities: [c0] MSI-X: Enable+ Count=96 Masked- >>> Vector table: BAR=1 offset=0000e000 >>> PBA: BAR=1 offset=0000f000 >>> Capabilities: [100 v2] Advanced Error Reporting >>> UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- >>> UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- >>> UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- >>> UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- >>> UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- >>> UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- >>> CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- >>> NonFatalErr- >>> CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- >>> NonFatalErr+ >>> AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- >>> ChkEn- >>> Capabilities: [1e0 v1] #19 >>> Capabilities: [1c0 v1] Power Budgeting <?> >>> Capabilities: [190 v1] #16 >>> Capabilities: [148 v1] Alternative Routing-ID Interpretation >>> (ARI) >>> ARICap: MFVC- ACS-, Next Function: 0 >>> ARICtl: MFVC- ACS-, Function Group: 0 >>> Kernel driver in use: mpt3sas >>> Kernel modules: mpt3sas >>> ------------------------------------------ illumos: illumos-discuss Permalink: https://illumos.topicbox.com/groups/discuss/T93c638c994b26488-M4ff40e1e9e0df6b4dcda838d Delivery options: https://illumos.topicbox.com/groups/discuss/subscription
