Lenovo YUM Repository
Release and Change History
Lenovo YUM Repository
Release and Change History
| Bundle Release Information: |
| Targeted Server Family (Machine Type): ThinkSystem SR630 (7X01, 7X02) |
| Targeted Operating System: RHEL7.3 |
| YUM Repository Build Date: 2019_04_23 |
| Device: |
| ThinkSystem RAID 530-8i PCIe 12Gb Adapter | Part Number: 7Y37A01082 Feature Code: AUKM |
||||
|---|---|---|---|---|---|
| PCIe Sub Vendor ID: 0x1D49 PCIe Sub Device ID: 0x0500 |
| Release History: |
| Continued Support in 19A - Latest Release | Change History Documents |
| Firmware | Firmware Name | Version | |
|---|---|---|---|
| BIOS and Firmware Update for ThinkSystem RAID 530-x Adapters (50.3.0-1032) | 530-50.3.0-1032 | ||
| Drivers | Driver Name | Discreate Package Download | Version |
| megaraid_sas kernel driver |
kmod-megaraid_sas- 07.703.07.00_el7.3-1.x86_64.rpm | 07.703.07.00_el7.3 | |
| Release 18A Change History Documents |
BIOS and Firmware Update for ThinkSystem RAID 530-x Adapters Supported Adapters: ThinkSystem RAID 530-8i PCIe 12Gb Adapter ThinkSystem RAID 530-8i Dense Adapter ThinkSystem RAID 530-4i Flex Adapter NOTE TO SERVICE - Reference RETAIN #N/A Version 50.3.0-1032 - Moderate Impact/Low Probability of Occurrence ------------------- BIOS: 7.03.02.0 UEFI Driver: 0x07030400 HII: 07.03.11.00 MR FW: 5.030.01-1232 PACKAGE=50.3.0-1032 Fixes: - Purley Cosmo/Cable/Cyborg/Ventura Raid card 530-8i loss during MQT2 Test (Bug 123240) - Open Timeout Error Handling is too drastic(SCGCQ00089824) - SPV: Virtual Expander does not reply to SMP Report Zone Manager Password Request.(SCGCQ00135037) - Fault x265D running random expander reset test in emulated external storage configuration(SCGCQ00135537) - Receipt of HARD_RESET data pattern causes firmware to perform error recovery in Target mode only(SCGCQ00135796) - SPV: Add check to verify if a Virtual Function is allowed to access a Virtual Port.(SCGCQ00136685) - SASWideMaxQueueDepth not being set for direct attached wide port SSP target devices(SCGCQ00136975 ) - Thunderbolt: PhySlowInit workaround should not be turned on(SCGCQ00138029) - Underlength Read on Falcon(SCGCQ00138247) - BT1680: pl: Unquiesce of TM doesn't restore subsystem id.(SCGCQ00140924) - Change hardcoded fault code to a properly defined code.(SCGCQ00141606) - Calculation of pl memory may be bigger than necessary for some regions.(SCGCQ00141622) - Read Long command to SATA device does not complete(SCGCQ00143655) - FPGA : FPE FW - Add a non zero value to Max completion Queue Read Count(SCGCQ00143659) - FPGA: Bugs in TBM code(SCGCQ00143878 ) - SAS Device Page 1 data for first drive or single drive was all zero(SCGCQ00144104 ) - Diag commands pl fpe mgrdsff and mgrdsfff didn't work, mgrds was exectuted instead(SCGCQ00144374 ) - pl fpe diag command (mgrds shows too little data(SCGCQ00144379) - Fix Sata Init(SCGCQ00144557 ) - Obtaining proper value of Standby condition timer from Power condition mode page (page 0x1a for a mode select command.(SCGCQ00144748 ) - 0x6009 Fault During TARGET RESET TM Completion(SCGCQ00145193 ) - x5891 Fault After OPEN Timeout(SCGCQ00145434 ) - Gen3 TaskMgmt: TMs that send an SSP TASK IU always timeout and complete unsuccessfully(SCGCQ00145553) - Converting SATA Standby count to proper Standby condition timer value in Power condition mode page (page 0x1a for mode sense(SCGCQ00145610 ) command. - Fault D062(SCGCQ00145624 ) - FPGA: Gen3 TaskMgmt: 0x265D Fault When Processing Multiple TARGET RESET TMs(SCGCQ00145645) - Typo in SATA init code could result in wrong block size reported for non-512 SATA drives(SCGCQ00146128 ) - FPGA: Gen3 TaskMgmt: 0x5110 Fault on Overlapped TARGET RESETs to SATA devices(SCGCQ00146626 ) - Expander goes missing during Expander phy reset testing(SCGCQ00146846) - FW hangs when sending sense data back to the host for a sata I/O(SCGCQ00146936 ) - Fault 5804 on Firmware startup(SCGCQ00146974 ) - Postponing and Disabled IO Path Bits Not Being Updated Through CudaMgr(SCGCQ00147136) - FPGA: Gen3 TaskMgmt: 0x1901 Fault On TM Completion(SCGCQ00147805 ) - Device won't do Fast Path IO after hot plug/pull done (no IO running(SCGCQ00147819) - FPGA: Gen3 TaskMgmt: 0x6827 fault when cleaning up port layer errors(SCGCQ00147864 ) - Dev State table mem alloc size should be PLI_MEMORY_MULTIPLIER_NUM_DEVICES_PLUS(SCGCQ00148214) - Enable Requestor/completor after port enable completes instead of waiting for associated discovery to complete.(SCGCQ00148644) - Fault 6004 on a target reset TM to an expander attached SAS drive running FP IOs(SCGCQ00149004) - Invalid Count Mismatch Error Handling for Fast Path IOs(SCGCQ00149150) - Fw hang (and fault during IO increment with FPE disabled.(SCGCQ00149621) - (Sata Only : Non auto SCSI command to a fast path enabled SATA drive times out.(SCGCQ00150032) - TBM: Normal mode entries are missing after pliStartOfDay(SCGCQ00150202) - When devices are removed / added the I/Os hang.(SCGCQ00151027) - (SATA Only : fault 0x7C33 while running fast path IOs to expander attached SATA drive(SCGCQ00151194) - SEP device incorrectly getting marked as Fast Path Capable by device manager(SCGCQ00151367) - SATA: infinite loop on sending IO while format is running(SCGCQ00151613) - wrong ComponentId values used to identify Cobra expander(SCGCQ00154786 ) - EDFB DMAGroup not set properly(SCGCQ00155513) - EDFB tracking of used DMA Groups not working(SCGCQ00155516) - FPGA: Fault 5890 after drive pull in Linux while running Medusa Stress(SCGCQ00155628) - F/W hangs when sending IO while requester is disbaled(SCGCQ00155750) - 0x6001 Fault while running TM Target resets durin Fast Path IO testing(SCGCQ00156005 ) - PL library linkerr error(SCGCQ00156105) - 0x6700 Fault(SCGCQ00156772 ) - FPGA: Clearing Sata DMA Passthru Interrupt not occurring.(SCGCQ00157384) - SATA FPE IOs get stuck(SCGCQ00158983) - Internal Task Management requests may be improperly constructed(SCGCQ00159014) - FPE: FP_DISABLED exception handling needs to check for a valid devhandle using the same checks as pliStartScsIO((SCGCQ00160011) - FPGA: SAS device page 0 fast path bit(s not properly set(SCGCQ00160469 ) - Debug tracking value was not correctly reset on PL->Fast Path started IO(SCGCQ00160504) - FPE - fix print statement in the frame ownership function(SCGCQ00162942) - Get the formatting/alignment of columns to match up.(SCGCQ00163733 ) - FPGA: Dynamic Queue Depth variations for SAS Targets broken for powers of 2(SCGCQ00163962) - Fault 0xd012 while using Cuda timer when timeout is set to less than 3 seconds(SCGCQ00165753) - Fast Path will be enabled for ATAPI tape device after a reset and init in CM(SCGCQ00165930) - FPGA: Target Mode error injection testing results in a 0x265D fault.(SCGCQ00166409) - FPGA: FPE: 0xD063 fault while running fast path IOs(SCGCQ00167839 ) - FPE fault D094(SCGCQ00167842) - Fault 0xD071 seen when sending down Abort Task Task Management(s(SCGCQ00169004) - PL is faulting with fault code 0xd075 when an IO times out(SCGCQ00170147) - SATA I/O timeout while loading OS drivers(SCGCQ00170253) - Fast Path Timer errors not seen after intial timer error(SCGCQ00172024) - Verification discovered scenario where 2 identical OPEN requests may come from SASCore for same device/IO(SCGCQ00172541) - Format unit progress indication is not being updated correctly(SCGCQ00172663) - FPGA: 0x5111 fault during Target Mode testing(SCGCQ00172991) - ReadBuf Command hangs(SCGCQ00174555 ) - Fault 0x4A00(SCGCQ00175661) - Build fails because of Small Data Area overflow(SCGCQ00176456 ) - 6001 Fault During IR RAID0 Volume Creation Under Linux SLES11(SCGCQ00177106) - Fault 0x4d05 seen to ATAPI SEP device when internal request sense is issued.(SCGCQ00177620) - TxCtxMgr interrupt handling uses incorrect register to determine which context is in error(SCGCQ00179621) - TM: Fault 0xD0ED while running task management(SCGCQ00179989) - TM: 670A Fault in task management(SCGCQ00180216) - D110 fault while doing Block Move test(SCGCQ00181603) - invalid parameter checks in TBM interface(SCGCQ00181781) - write buffer command (via a sata passthrough request during stress causes the adapter to reset.(SCGCQ00181783) - Fault 0x5826 when running Task Management tests(SCGCQ00183297) - Fix 2 unguarded loops in Control Queue Cleanup(SCGCQ00183881) - Build all fails with error(SCGCQ00184424) - Phy power code is using the wrong mask(SCGCQ00186364) - Controller faults with code 6004(SCGCQ00187146 ) - Phy link rate does not follow MaxMinLinkRate in sas io unit page 1(SCGCQ00187614) - TBM Recursive Fault(SCGCQ00187763 ) - Ensure that PL stops FPE on any PL sourced fault(SCGCQ00187765 - Controller faults with code 5891 while running task management tests(SCGCQ00187778) - Controller faults with code 6003 while running task management tests(SCGCQ00187962 ) - IOs stop to sata drives(SCGCQ00188083) - Fault 0x5896(SCGCQ00188925) - Debug print was mis-formatted(SCGCQ00188926) - Multiple Timers could be added for single IO(SCGCQ00189781) - Running I/Os to SATA HDDs w/Jammer scripts results in fault 0x265D(SCGCQ00189790 ) - Gen3: A Jammer script sends too much data for a Read command which results in SysDmaParity fault.(SCGCQ00190412) - Fault 0xD071 while doing message unit reset(SCGCQ00190417) - Fixe pl.h compile when ENABLE_TRACEBUFFER_MANAGER is not on(SCGCQ00190928) - Linking error with PL library(SCGCQ00192806) - When an extra Data frame, or data is sent by SAS device for a READ, the device isn't sent a Task Management.(SCGCQ00192944 ) - SATA 4k sector size will not start IO.(SCGCQ00193363 ) - Firmware repeatedly sending a event whenever it get a spinup notify causes target mode initialization to stall(SCGCQ00194444 ) - SATA write I/Os timeout especially behind expander(SCGCQ00194464 ) - FPE Status values passed to iopiFPEHandleException( weren't included in PLI release(SCGCQ00194558) - 6101 Fault while running Task Management Stress test(SCGCQ00194569 ) - Invalid Loginfo value seen when a Wrong Relative Offset error encountered on transmit data path(SCGCQ00194925) - IO Timeouts/0x6001 fault during SATA TM Read Mayhem test(SCGCQ00195557 ) - Sata Targets are never initialized(SCGCQ00197633) - FPE: Sata Init code causes recursive call to FPE Exception queue handling(SCGCQ00198255) - Invader A0: phys not coming up after being disabled and then re-enabled(SCGCQ00198822 ) - fault d012 with stress fast path IOs on a single drive(SCGCQ00199529) - Timeout of an Inquiry command to SATA drive which was already completed as failure(SCGCQ00199797 ) - Invader A0: D072 Fault during stress and whole port glitches(SCGCQ00200261) - Gen3 PwrMgmt: Open Address frame has a SAS Address of zero when a device wakes up from PM.(SCGCQ00200472 ) - Gen3PwrMgmt: PM status interrupt fires intermittently.(SCGCQ00200477) - The "CurrentStatus" field in SAS IO Unit Page 6 is not getting updated properly when Port width modulation is disabled.(SCGCQ00201411) - Invader A0: D100 fault while running stress using Write/Read (6 CDB size to a SATA NON-NCQ drives(SCGCQ00202551 ) - IOs timeout when running task management tests(SCGCQ00203055) - Gen3: PM - Global Power Management change requests result in the same event being sent twice to the host.(SCGCQ00203543 ) - Invader A0 (init/targ : 0x7c54 fault during stress and cable breaks(SCGCQ00205569 ) - Drives do not link up reliably(SCGCQ00205778 ) - Large Block IOs to SATA drives timeout(SCGCQ00206603 ) - Invader A0- D027 fault when disabling 3 phys when stress is running in a target and initiator mode setup(SCGCQ00207040 ) - Invader A0: D072 fault during Block Move test(SCGCQ00207153 ) - Gen3: PwrMgmt - fix for BT1251 (exiting Partial/Slumber PwrMgmt results in OOB(SCGCQ00207737) - Region lock release hangs due to AVL tree corruption(SCGCQ00208241) - PL layer notifies IOP layer for 0 timed out IO on receiving timeout interrupt.(SCGCQ00208538) - DMA Engine debug timers initial values cause immediate interrupt and fault(SCGCQ00208650) - Fault d012 due to FPE timer error while running stress loads(SCGCQ00209193) - Gen3: PwrMgmt - SATA Devices not showing up in Discovery(SCGCQ00209549) - Discovery does not complete with Bobcat expander.(SCGCQ00209645) - Fault 0x4852 while running target Modes IOs and disabling phys.(SCGCQ00210183) - Non-TARGET mode builds wouldn't compile(SCGCQ00210303 ) - Non Target build still had a target only function(SCGCQ00210482) - Gen3 PwrMgmt: PwrMgmt memory request accesses IOP function - PLI violation.(SCGCQ00210496 ) - For Target mode when performing send status with data the call to iopiMemoryMove( doesn't reflect the correct address space.(SCGCQ00213224 ) - System DMA error not causing a firmware fault(SCGCQ00213368) - Invader A0: Fault 0xD140 while doing random TMs to FAst Enabled SAS drives running IOs(SCGCQ00215178) - Invader A0: Fault D060 while running Block Move and Task Management Test in CM(SCGCQ00215835 ) - Fault 0x5881(SCGCQ00215843 ) - Gen3: Power Management change request fails when direct-attached to an expander.(SCGCQ00216828 ) - Invader A0: 0xC009 fault on Target side of 12G setup(SCGCQ00217481) - Snooping configuration not set on SAS Core DMA PLB Master(SCGCQ00218116) - Failures connecting to SATA drives or expander attached disks(SCGCQ00218117) - Invader: Updated the FW work around tables for the B0 release.(SCGCQ00218436 ) - fault D025 while running IOs on a mix of SAS and SATA drives(SCGCQ00218687) - Invalid 0x5897 and 0x6828 faults(SCGCQ00218792 ) - Invader A0: Fault 0x6003 while power glitching random enclosures during Block Move Test(SCGCQ00219144) - 0x5841 while doing single Phy cable breaks for 1 second(SCGCQ00219298) - Invader A0 - target Mode Ios hang(SCGCQ00219408 ) - SATA Passthrough Message to Non-SATA device causes DiagReset(SCGCQ00219819) - fault D024 with timeouts while running straight IOs(SCGCQ00220650) - Discovery fails with SMP timeout while cable pull push in a multipath topology(SCGCQ00221089 ) - PL hits TLB error while dumping SGLs(SCGCQ00223497) - Invader A0: 0x5002 on Target when disabling then reenabling Phy(SCGCQ00223630 ) - Fix fault when the trace buffer mode is changed.(SCGCQ00224807 ) - Invader A0: 0x583B fault during IO and Task Management in CM(SCGCQ00225189) - Fault 0x5833(SCGCQ00225772) - Fault x6018(SCGCQ00225835) - Firmware displayed wrong version number(SCGCQ00225971) - 0x61A3 fault during task management(SCGCQ00226954) - Fault 0x5302 when running IO and using Close Clear Affiliation option(SCGCQ00227563) - SMP function failed during enclosure pull/push tests.(SCGCQ00227580 - Invader A0: Fault x5842 with running Block Move and Task Management Test(SCGCQ00227896) - Fault x5900 seen running heavy IO with discovery(SCGCQ00228216) - System hangs or reboots, or Fault x5863(SCGCQ00228819) - Invader A0: CM looses devices during whole port glitches(SCGCQ00228959 ) - Invader A0: 0x4A00 fault while running whole port cable glitches during stress(SCGCQ00229141) - D072 Fault(SCGCQ00229676) - Slow performance of non automated IOs issued to SATA drives(SCGCQ00230305) - Fault 0x7C20 occurs with cable glitches on a large topology(SCGCQ00230957 ) - Debug dump via "pl reg all" UART only dumped 1/2 of the DMA Transmission Q(SCGCQ00233599) - Invader A0: 0x5861 fault during stress and whole port cable glitches(SCGCQ00233716) - Gen3: PwrMgmt - A power management change request may not generate a interrupt.(SCGCQ00233745) - Invader PL CLI show expander prints incomplete information(SCGCQ00235365) - Gen3: PwrMgmt - Host can change power state for direct-attached devices when hardware timers are set.(SCGCQ00235403) - Invader: Fault 0x5831 occurs after PL register dump(SCGCQ00235412) - Fault 0x510B(SCGCQ00237408 ) - Fault 510b during enclosure pull push.(SCGCQ00237445) - Fault 0x5304 during enclosure pull push(SCGCQ00237446 ) - IO timeouts while running stress loads on a mix of SAS and SATA drives(SCGCQ00239369) - Fault 0x2667 when trying to register a diag trace a second time(SCGCQ00242016) - The BT999 Detection Algorithm was removed when WA for fault 4A00 was checked in(SCGCQ00242147) - Fault x5814 while running Initiator and Target mode IO with another controller also doing Initiator and Target mode.(SCGCQ00244719) - Fault 0x583E seen running SATA IO with cable glitching(SCGCQ00246442) - Gen3 : Build failing for the latest tipcode when build all command is issued.(SCGCQ00246801) - Invader A0: 0xD071 fault during stress and whole port cable glitches(SCGCQ00250013) - Add DCR reg info on SASConfig Reg Fault 7C54(SCGCQ00251048) - Invader A0: Update needed for RAID Context usage(SCGCQ00251530) - A region of greater than 3 can cause reading and writing to registers outside the snoop registers.(SCGCQ00253267) - Linking PL library with non-SCG IOP might throw unresolved linker errors(SCGCQ00253272) - Dependency on GHS library for 64 bit multiplication(SCGCQ00253316) - Command Transmitting error fro OPEN FAILED cases doesn't work in out of resource cases.(SCGCQ00254943) - D024 or D025 fault seen when using FPE checkpoints to debug(SCGCQ00255192) - Trace buffer may be missing last chunk, up to 16k.(SCGCQ00255895) - Fault 0x58B4 when trying to run on a 4port controller(SCGCQ00258518) - PL Debug string PL_DBG_STR_CONTROLQ_DISABLE_HANG needs to be fixed so a print does not show up as ??(SCGCQ00258558) - Move FPE and TBM global bits out of PL_INFO_FLAGS and into the FPE_INFO and TBM_INFO fields(SCGCQ00258992) - Ensure parity correctly disabled if BT999 seen(SCGCQ00259200 ) - Gen 3 : Affilation conflict and the SATA drive connected beyond the expander will not be detected(SCGCQ00259968) - Data corruption seen during TLR(SCGCQ00260533) - Fixed name of local variable(SCGCQ00261861) - PL: Need to have unique fault codes(SCGCQ00263726 ) - PL was making call to IOP layer config read function for a READ_CURRENT of PL owned page before Port Enable completes(SCGCQ00266032 ) - Invader B0 was using high initial AWT values(SCGCQ00268857 ) - pldebug.h file is not included in current PL lib releases(SCGCQ00276224) - Controller keeps resetting a SATA drive if the drive is security locked(SCGCQ00276277 ) - Fault x6108 seen when running IO and having TM occur(SCGCQ00277552) - Fault 0x6414(SCGCQ00278271) - Invader A0 TxDMA cleanup code needed a change added back(SCGCQ00278781) - A debug print needs Link # added to be more useful(SCGCQ00279991) - Invader B0: Firmware not sending Close (Clear Affiliation to SATA drive(SCGCQ00280557) - A hardware workaround was incorrectly disabled for B0(SCGCQ00280738) - PL: receive path stalls result in SMP timeouts(SCGCQ00281960) - Invader B0: Adjust SAS Max Qdepth at init to account for Hw Limitations.(SCGCQ00282258 ) - TBM Extended Mode (PLI_TBM_BUFFER_ADDR_LOC_PLB not supported(SCGCQ00282507) - fault 5821 while running IOs on SATA drives (with DEBUG disabled(SCGCQ00282860 ) - Gen3-Invader A0: Nightly Build image faults with 7B00 fault code(SCGCQ00282874 ) - Invader B0: Zero IoCount event in active state should only be turned on for SATA(SCGCQ00283220 ) - Invader B0: Fault 0x5896 while Powercycling Random Enclosures(SCGCQ00284582) - Fixed source level debugging using GHS probe.(SCGCQ00286179 ) - Invader B0: D074 fault occurs during simple IO stress when Fastpath timeout is set to the minimum value (1 second(SCGCQ00286838) - Invader B0: FPE Manager Fault code cleanup and documenation update(SCGCQ00286906 ) - Invader will reset ATAPI SEP Continuously while sending a command with inbound data(SCGCQ00289355) -(SCGCQ00289533 ) - PL: Firmware may not send Notify(Power Loss Expected in accordance with the SAS Spec(SCGCQ00290667) - ATAPI Request Sense Command failing(SCGCQ00290668) - Initiator behavior in dropped ACK/NACK to SSP Command frame compliance test(SCGCQ00292021) - Fault x5801 seen running IO with Task management(SCGCQ00292512) - Invader faults with 0x7C39 when sending Security Protocol Out Disable Password command(SCGCQ00293371 - IO hang while running IOs and enclosure cable pull push(SCGCQ00293701) - Fault 5813 while pulling direct attached SATA drives(SCGCQ00293898) - Fault 0x61a2 while running IOs on a mix of SAS and SATA.(SCGCQ00294588) - 0x584B Fault during whole port cable glitches(SCGCQ00295331) - WriteBuffer in 'Write Data' mode executes with good status when Bufferid=0 and Buffer Offset=non-zero values.(SCGCQ00297369) - WriteBuffer in 'Write Data' mode executes with good status when Bufferid=0 & Param List length != 512.(SCGCQ00297375) - Invader B0: CSET of SCGCQ00237417 incorrectly checks TxDMA Start register(SCGCQ00297565) - Fast path IO is never started after a timer error because RL granted bit is not set in MST(SCGCQ00297968) - Invader B0: All Drives lost (turn red during IO + TM in CM(SCGCQ00298619) - Invader B0: 0xD023 fault when BIOS searching for devices(SCGCQ00299563) - Firmware faults with PL fault code 0x5854(SCGCQ00302792 ) - Invader B0: 0x6001 fault while running a Max Outstanding IO count test with DDR(SCGCQ00304313) - Invader B0: PL not adding timer back when restarting IOs with Requestor Timer Error(SCGCQ00307944) - Invader B0: fault x5854 during I/T switching with IO and expander PHY resets(SCGCQ00307989) - (FPGA changes to firmware for B0 FPGA(SCGCQ00316360) - PL Fault 0x6B0C when performing PHY power management(SCGCQ00318960) - Invader B0: PL register dump doesn't include IOP Completion Queue(SCGCQ00319389) - Invader B0: Fault 0x61A0 while running Block Move Test to Direct Attached Drives(SCGCQ00319503) - Fixed an Error in Code to Allow a Hardware Workaround to Be Correctly Enabled(SCGCQ00321025) - Invader A0 fault 583B fault(SCGCQ00321227) - Invader B0: Fault 0x4101 while power cycling expanders(SCGCQ00321678) - IO timeout for PL owned MID after sending QueryTask(SCGCQ00323459) - Invader B0: pl dbg does not dump TBM registers(SCGCQ00326191) - Invader B0: (PL Fault xD072 during I/T switching with IO and TM(SCGCQ00328713 - Added C0 Hardware Workaround to Prevent Fault x5801 seen running IO with Task management(SCGCQ00329584 ) - Link locks up when jammer is used to create wrong SATA FIS types.(SCGCQ00331579) - Change Hardware Workaround To Only Execute if Actual Cleanup is Done(SCGCQ00334830) - Fixed Problem in Target Mode Code Which Caused 0x26B5 fault(SCGCQ00336232) - Invader: Fixed Debug Print in Port Layer(SCGCQ00336882) - PCIE lockup occurs when running EDFB IO with cable breaks and device removals(SCGCQ00337231 ) - Fixed Link Layer Interrupt Handler to Prevent Fault 0x4101(SCGCQ00338504) - Tape drive [3Gb/sec SAS] not detected with Invader controller(SCGCQ00338996) - PL: Read Log Ext command timeout.(SCGCQ00342412) - Some IO accelerator registers are not yet available on FPGA(SCGCQ00349862 ) - Fixed pl_src build(SCGCQ00355601) - Back end PCI interrupts are not enabled(SCGCQ00357192) - Backend PCIe doesn't handle Legacy interrupts(SCGCQ00361845) - Assertion while enabling MSIx interrupts(SCGCQ00362633) - Bus and device are evaluated properly while configuring device's interrupts.(SCGCQ00363567) - NVMe: FW SGL translation doesn't work properly with buffers larger than 1 host memory page(SCGCQ00377286) - Couple of PDB interrupt handling fixes(SCGCQ00378025) - IOA hardware generates an incorrect AHCI command header(SCGCQ00383642 ) - (CUDA Cuda writes zero to the reply descriptor post FIFO on completion(SCGCQ00386306) - AHCI Asynchronous Notification was not working(SCGCQ00393902) - PCIE IO Unit 0/1 size in header is not correct(SCGCQ00394558) - No functional change(SCGCQ00395325 ) - [Dauntless] SkipCount and Host Chain Support not present for IEEE64 to NVME PRP translation(SCGCQ00395615 ) - Dauntless Firebird header file typos(SCGCQ00397598 ) - Critical Fixes for PCIe IO Unit config pages(SCGCQ00400007 ) - Need Proper Routine for Initializing Cuda Timer Wheel RAM (Reset Sequence(SCGCQ00403591) - 7C32 fault(SCGCQ00404224 ) - Unaligned CE Image causes PL fault 0xd115 when using CE Auto Load(SCGCQ00408789) - Bad pointer access in plPciRcSetPcieLinkWidth(SCGCQ00409869 ) - Backend NVMe devices don't work if stored host page size is invalid(SCGCQ00410848) - IO timeouts with AHCI devices(SCGCQ00412147 ) - NVMe: Nonzero SkipCount doesn't work very well(SCGCQ00412150 ) - A write and verify command with many SGEs can cause a FW fault(SCGCQ00413390) - AHCI: Write and verify 32-byte CDB causes D300 fault(SCGCQ00414013) - AHCI: very large xfer count in one SGE causes fault 0xD300(SCGCQ00414589 ) - (PLLIB Some PL Light routines are not included in the libraries(SCGCQ00415107) - Modify handling of a couple of Stang exceptions(SCGCQ00415459) - Need to handle DATALEN_GT_SGLLEN exception differently(SCGCQ00415490 ) - Unexpected D033 fault(SCGCQ00418247) - NVMe: Fix a few bugs from the SGL breakup code review(SCGCQ00418946 ) - 265D fault running write IO to AHCI device(SCGCQ00419400 ) - Added support for non-standard AHCI-like endpoints(SCGCQ00420921 ) - MaxPayload/MaxReadRequestSize are getting set to strange values in some cases(SCGCQ00420926) - Dauntless FPGA: Data Corruption reported when running 1M IO to AHCI device(SCGCQ00424263) - D115 fault after dumping 'pl pci regs all'(SCGCQ00424915) - 26B5 fault when trying to init AHCI target(SCGCQ00426195) - No access to DDR for backend PCIe devices(SCGCQ00426529) - D065 fault running IO to an AHCI target(SCGCQ00433598) - (PL New Spinup code does not compile with PL_FEATURE_PCI_DEVICE_SUPPORT set to zero(SCGCQ00434738) - SAS3.5: Add ALADIN feature macro and add pliAladin function calls to pliComplianceCheck.c.(SCGCQ00436117) - PCIe Switch upstream and downstream port relative configuration not proper(SCGCQ00436160) - AHCI: an address error will be reported with the wrong error status(SCGCQ00436941) - Firmware hits Fault D10F while creating configuration on AHCI SATA drive(SCGCQ00442131) - Max payload size of virtual bridges not configured during enumeration(SCGCQ00442730) - E00D fault while running firmware translated read + mode sense(SCGCQ00444010) - DDR not mapped for MegaRAID builds(SCGCQ00445331) - Assertion failure fault D300 on PciIoCount adjustment(SCGCQ00447911) - AHCI: Command timeout with mixed auto and nonauto IOs(SCGCQ00448191) - NVMe: PL shouldn't fault when NVMe SGL translation encounters an invalid address(SCGCQ00448246 ) - Incorrect Mid value used looking for unconfirmed response during HW cleanup(SCGCQ00449087) - FW might fault D065 fault when running IOs + Query task to AHCI device(SCGCQ00449578) - Fault 0xd102 hit when IOP issued task management request(SCGCQ00456250) - AHCI: 60D fault on completion of a Write Verify command(SCGCQ00456311) - AHCI: Some internal variable accesses used the wrong index.(SCGCQ00457265) - Data Corruption observed during IO + "random" TM to AHCI(SCGCQ00457786) - Fault 0xd300 hit when a read/write IO to PCI device is unpended and resubmitted to firmware(SCGCQ00462188) - E80D fault running IO in a PCIe Switch config(SCGCQ00462334 ) - PL Hangs in Spinup Retry Request Entry function if 2 AHCI and a SAS devices are connected(SCGCQ00464397 ) - D20C fault when starting CM Block Move with Diagnostic Buffer Posted(SCGCQ00465468) - EC0F Fault when running IO + Abort Task TM to AHCI(SCGCQ00466209) - Dauntless FAULT 5801 running mixed IO with random task management test(SCGCQ00467347) - AHCI: Device discovery failed because of the missing MPI26_EVENT_DATA_PCIE_TOPOLOGY_CHANGE_LIST event(SCGCQ00469381 ) - Dauntless FPGA: 670D fault while collect pl dbg(SCGCQ00471741) - Hitting MPI2_IOCSTATUS_INVALID_SGL.(SCGCQ00473919) - Device added event for the existing devHandle(SCGCQ00475377) - TM Fail ScsiIO Dev:MID Debug Print Displays Address Rather Than Opcode(SCGCQ00476208) - D300 fault during mixed auto/nonauto IO to multiple AHCI devices(SCGCQ00477054) - PL did not clean up resources for internal AHCI encapsulated frame if associated SATA passthrough command failed.(SCGCQ00481908) - Extra validation required for Silverhawk PIM1 settings(SCGCQ00484633) - Dauntless FPGA: D300 fault running IO and TM(SCGCQ00490962) - SAS/SATA drives go missing while running block move IO and Random TMs(SCGCQ00493178 ) - NVMe Encapsulated Path Fixes(SCGCQ00493331) - SAS3.5: PL Status shows parent devH of second switch in cascaded switch setup is zero(SCGCQ00496013) - Backend PCIe completion timeout after a PCIe error message is received(SCGCQ00498112) - NVMe: IO timeouts with high queue depth PL translated read/write IOs(SCGCQ00498179) - Dauntless Fault 6001(SCGCQ00499669) - SATL: WRITE SAME Handling with LBPRZ=1, UNMAP=1, ANCHOR=0 needs an additional check(SCGCQ00524994) - D065 fault occurs during port enable with AHCI devices attached(SCGCQ00531377) - Data corruption runing heavy IO(SCGCQ00551309) - NVMe: fix a couple of async event handling issues(SCGCQ00556769 ) - NVMe: Write Buffer (mode 0x5 translation fails to complete(SCGCQ00557073) - Dauntless: Backend POM Window size should be aligned to number of PCIe devices supported(SCGCQ00558089) - SAS3.5FW: PL: PCI: Use PliRegister for device registration instead of hardcoded value(SCGCQ00558177) - Fault 6230 running Clear Task Set TM(SCGCQ00559714 ) - NVMe: LUN not validated before use in non read write translations(SCGCQ00562314) -(SCGCQ00590504) - PCI command frame is tried to be obtained from non PCI firmware IO(SCGCQ00590513 ) - NVMe: no call from TM during init idle wait(SCGCQ00595468) - (Sata Only Sending 'Ata Passthrough' SCSI command with ATA Command as 'Read Verify Sectors' sometimes results in check condition(SCGCQ00597647) response. - Backend PCIe: possible command timeouts in low resource or queue full cases(SCGCQ00600854 ) - Firmaware fault 0x26B5 observed when sending IOUnit Control Message with OPERATION of SAS_PHY_LINK_RESET to PCIe switch(SCGCQ00601557) dev handle - 1901 fault when a FORMAT command issued to an AHCI target(SCGCQ00601939) - Some of the declarations and typedefs in pliDefs.h not conforming to code standard(SCGCQ00606222) - Ventura: Fix plInit in which VENTURA_PORTING was eliminated causing ARM to crash(SCGCQ00615099) - NVMe: IEEE to PRP translator rollback issues(SCGCQ00626787) - D300 fault seen when SCSI Mode Select is sent to AHCI device(SCGCQ00630246) - Limit the number of phys during spin up configuration for the FPGA(SCGCQ00648198) - NVMe: no retry if initial NVMe init fails(SCGCQ00664181) - Ventura: incorrect bits in interrupt mask(SCGCQ00668609) - Dauntless minimal build failure(SCGCQ00670226) - Fault 0x6230 seen when sending Port Enable(SCGCQ00670926) - Continuous plTxCtxMgrHighInterrupt on SASCORE1 attached SATA drive(SCGCQ00671683) - 4308 fault when using SAS IO Unit Control message with SEND PRIMITIVE operation(SCGCQ00673188) - Ventura PL: Internal flag may be incorrectly disabled during Abort Task operations(SCGCQ00673302) - PL clearing interrupt is not getting reflected in Interrupt observe registers(SCGCQ00674340) - Intruder: Fix unprotected loop in plTargetProcessHardReset((SCGCQ00678870) - PL: Fault 0x4302(SCGCQ00682071) - Intruder: PL Fault 0x4307 while doing init(SCGCQ00682911) - Intruder: Fix plSataPassthrough.c to account for Multi Core work for plSataPassThrough.c(SCGCQ00684321) - PL: Fault 0x6001(SCGCQ00685967) - Ventura: arm_all compile error in SAS SERDES / Phy Files(SCGCQ00686674) - Intruder & Ventura: Fix plFpeHandleCompletorErrorInt( to compile for Ventura(SCGCQ00687645) - Fault xD105 running IO to SATA devices(SCGCQ00692817 ) - SECURITY IN SCSI command timing out to AHCI device due to incorrect SATL translation.(SCGCQ00693169) - Fault x6001 running IO with Task Management(SCGCQ00693865) - PL: 0x6003 fault(SCGCQ00694271 ) - Firmware Fault 0xEF00 seen while running Task Management and IOs to AHCI drives.(SCGCQ00695559) - EF04 fault running Random TM with Mixed IO sizes(SCGCQ00696962) - Intruder FPGA: Destructive Domain (Bobcat's hit fault 0xD0E0(SCGCQ00696975) - Ventura: Need required external defines and header file ordering to include SCS FW libs in IOP(SCGCQ00697063) - Intruder: Reset of SASCore 1 or 2 was not using correct value to clear reset bits(SCGCQ00698911) - Intruder FPGA: 0x26B5 fault seen when accessing RxEEDPBuf of any SAS core(SCGCQ00698951) - Firmware faults when downstream port of attached PCIe switch sends uncorrectable fatal error for malformed TLP it received from(SCGCQ00699010 ) connected device. - PL incorrectly faults when a non read/write IO to AHCI device hits FxCore exception when started through firmware path.(SCGCQ00700211 ) - Debug code was inadvertantly checked in which causes phy layer initialization to not work for second core or phys > 0.(SCGCQ00705330) - NVMe: IoCount not decremented on non read write encapsulated NVM command failure(SCGCQ00705495) - Fast path IOs are timed out.(SCGCQ00706941) - Dauntless FPGA: D205 fault when posting a host trace buffer during IO(SCGCQ00707374) - PL:Restrict access to RxEEDPBuf in pl dbg(SCGCQ00709358) - PL NVMe (Ventura IOCStatus SCSI Task Management Failed when running Abort Task to NVMe(SCGCQ00710213) - Data continues to be sent after RESPONSE for an IO is received before data transmission completed(SCGCQ00710281) - Fix issues in PL diagnostic code(SCGCQ00710497 ) - Intruder: Fix issues in FW controlled spinup(SCGCQ00710609) - Drive SAS Address in gplControllerPhy structure being overwritten, resulting in drive loss(SCGCQ00712955) - 265D fault on AHCI spinup(SCGCQ00714811) - NVMe devices may fail to initialize(SCGCQ00715163) - Intruder FPGA: Drives attached to expanders gradually get dropped during Task Management test(SCGCQ00715652) - Intruder: Don't display all message frames for pl dbg register dump(SCGCQ00716613) - Ventura: IOA Local RAM requires an offset(SCGCQ00717129) - Fault xD015 seen running IO when Task Management occurs(SCGCQ00718761) - Fast path completor engine throws error for IOs that don't have appropriate flags set in fast path mid state table(SCGCQ00719653) - Fault 0x265D(SCGCQ00719768) - pl timestamp print fills ring buffer(SCGCQ00720114) - PL SATL: Fault 6201 When Sending SCSI Security Protocol In Command to SATA Drive(SCGCQ00721212) - Ventura: wrong SAS core address in FPE(SCGCQ00722553) - Ventura: Drives on link 1 always respond with sense data 020411(SCGCQ00725112) - Fixed Known Issues with FIS Port SCSI Unmap Translation(SCGCQ00728088) - Intruder FPGA: Fault 0x584F while running CM Block Move and Task Management Test to two direct-attached SATA drives(SCGCQ00735409) - Ventura: Small Data Area overflow in compile/link operation(SCGCQ00735463) - Intruder FPGA: Fault 0x5828 while power cycling random expanders on both cores(SCGCQ00735635 ) - Fault 0xE00B while running mixed IO sizes with random task managements.(SCGCQ00736592 ) - Fault 0x510B while running stress to 7 cascaded expanders(SCGCQ00736679) - Remove redefinition of IOC_NUM_PHYS(SCGCQ00736730) - Problems in Tx DMA single to dual context mode switch and vice versa on multi SAS core(SCGCQ00737078 ) - Intruder FPGA: Fault 0x584F while initializing PL(SCGCQ00738149) - Fault 0x6001 While running Task Abort to topology of only SATA Drives during I/O.(SCGCQ00740832) - PL: add temporary config page buffer items to gplDynamicMemory(SCGCQ00741788) - Ventura: Bad merge backed out the fix in SCGCQ00716821(SCGCQ00748108) - Dauntless FPGA: Read Error when running Medusa IO with Abort Task Set TM to NVMe drive(SCGCQ00752414 ) - Intruder FPGA: Fault 0x584F while running Initiator Mode SMP Protocol Error Handling(SCGCQ00754410) - Intruder FPGA: Drive loss due to stuck TxDMA.(SCGCQ00754417) - PL: uninitialized NumPhys(SCGCQ00757724) - Backend PCIe: periodic dev init state check shouldn't run if init isn't running(SCGCQ00760618) - Ventura: Processor abort on I/O with sense data(SCGCQ00762270) - Dauntless FPGA: IOs stop in while running task managements to AHCI device(SCGCQ00764902) - Dauntless FPGA: EC38 fault upon initialization(SCGCQ00765364) - Fix compiler-identified errors in plPciRootComplexDauntless.c(SCGCQ00765443) - pliProtos.h contains 2 internal protos for sim/fake IO(SCGCQ00769245) - FW Controlled Spinup: Slot ordered spinup defects(SCGCQ00771112) - Intruder: Fix the spinup register read to get the spinup group for multi SAS core.(SCGCQ00771113) - pl: Unexpected usage of 64 bit math lib in plPciNvmeFillInquiryData((SCGCQ00771167) - NVMe: rename some structure definitions in the NVMe code(SCGCQ00771188) - pl: backend PCIe: couple of PCIe IO Unit Page 1 issues(SCGCQ00776230) - Intruder FPGA: Fault 0x670A on Target Controller during Block Move and Task Management Test(SCGCQ00776306 ) - NVMe: EF08 fault during non target reset task management(SCGCQ00776392) - Intruder FPGA: Data Underruns while doing Target Mode IOs(SCGCQ00776411) - Intruder FPGA: Fault 0xC00C while running Initiator and Target Mode on Intruder Cores(SCGCQ00776417 ) - Ventura: 430B fault with multiple devices attached(SCGCQ00779488 ) - Intruder FPGA: Fix Repeated Rising Edge Spinup Interrupt(SCGCQ00780197) - Intruder: Incorrect parameter is getting passed in plGetQuadPhyIndxFromCorePhyNum((SCGCQ00785455) - PL: incorrect logic in determining setting for CloseOptimize(SCGCQ00786213) - Intruder FPGA: 0xD20C Fault While Running Stress From 4 Initiator System to Target Mode FPGA(SCGCQ00791373) - Ventura: PCIe Discovery problems observed with device reset test.(SCGCQ00793909) - Intruder FPGA: Fault 0x4307 while running Block Move to drives and resetting random expander(SCGCQ00800919) - Intruder: Link event codes are not properly converted from hardware to MPI values(SCGCQ00806568) - Backend PCIe: FxCore error bit clearing(SCGCQ00813507) - pl: backend PCIe: read/write IOs with chain to native SGLs fail with IoFlags.FastPath set to 0(SCGCQ00813839) - Dauntless FPGA: Data Corruption reported on multiple tests(SCGCQ00813954) - 265D fault while running task managements(SCGCQ00817552) - Ventura: Sascore 1 links do not come up(SCGCQ00822145) - Dauntless FPGA: EFF1 fault on init(SCGCQ00822595) - Remove Aladin Reset Code in PL Start of Day(SCGCQ00823445) - Ventura: PCIe Device Manager DMD expiration handling(SCGCQ00824724) - Ventura: Phy register addressing is incorrect(SCGCQ00825050) - Ventura: Fault 430A during intitialization(SCGCQ00825789) - Dauntless FPGA: Fault D065 during CM init to AHCI drive in non-NCQ mode(SCGCQ00827582 ) - Ventura: Only 1 drive is discovered when 2 sas or 2 sata drives are directly attached(SCGCQ00828878) - Ventura: "iop arm table" crashes due to missing string(SCGCQ00829296) - Ventura: Fix PCIe discovery out-of-resource handling(SCGCQ00831671 ) - Use the address, not value of register to set base for the IOA shadow Register PIM(SCGCQ00832543) - Fault 0xD63C when trying to create/use an 8K PIM(SCGCQ00832557) - Fix code for handling FxCore Requester and Completer errors as per comments in review.(SCGCQ00834567) - Intruder A0: 0x4330 Fault When Multiple SATA Drives Are Attached Simultaneously(SCGCQ00834931) - PL: Update link layer register that should be programmed differently for intruder(SCGCQ00835524) - A device initialization call was being made for all end devices, that doesn't apply to SED(SCGCQ00836070 ) - Ventura: backend PCIe: host bringup fixes, part 1(SCGCQ00837192) - Intruder: Disable DMA Engine Overrun error for Intruder and beyond based on Hardware feedback(SCGCQ00839532 ) - PL: Assert was using compiled out code causing bad ring buffer(SCGCQ00839583) - Ventura: SAS_R31_HACK doesn't always compile correctly(SCGCQ00841016 ) - Ventura: backend PCIe: some bringup changes(SCGCQ00841065) - Fault 0x7C54 seen during I/T switching(SCGCQ00843298 ) - Unmap FIS Port Translation Hangs if No Range List Entries are Generated(SCGCQ00844030 ) - Intruder A0: Fault 0x5872 during I/T Switching(SCGCQ00844812) - Ventura: backend PCIe: fix some scattered bugs(SCGCQ00845780 ) - Intruder A0: Fault 670A while running target mode Jammer exception Test(SCGCQ00845803) - Intruder A0: 0x6C02 fault while running IO's and power glitching on every core(SCGCQ00846661) - Ventura: backend PCIe: command issued prior to first AHCI init success may fail to unpend(SCGCQ00848265) - Cleanup IOP Access to gplPtrPdbRegs(SCGCQ00849748) - PL: SATA Command getting stuck in PL after issuing Start Stop command with immediate bit set(SCGCQ00851287 ) - Ventura FPGA: Fault 6001 soon after initialization(SCGCQ00851724) - Ventura FPGA: backend PCIe: data corruption seen during write/read/compare test(SCGCQ00851725) - Ventura: Fault 265D when pl dbg dumps PtrHwDmaQFreePointer(SCGCQ00852104) - SAS3.5FW has tabs in source code(SCGCQ00852767 ) - Intruder A0: Fault 0x6111 during I/T Switching(SCGCQ00852833) - Ventura: backend PCIe: D363 fault during PL init when PCIe device structures are placed in DDR(SCGCQ00853886) - Intruder A0: 265D fault observed during link reset task management with IO(SCGCQ00853930) - PL: Fault 0x430B seen when connecting several enclosures(SCGCQ00854697) - PL: Incorrect SGPIO Index calculated for more than 2 SGPIOs(SCGCQ00855007 - Ventura: RxEEDP buffer init has wrong size(SCGCQ00855014) - TLB exception when showing PL ring buffer(SCGCQ00855026) - PL: IOs completed with good status when EEDP Check enabled and EEDP error injected with 4096 block size(SCGCQ00855669) - Firmware Controlled Spinup: Spinup group with multiple drives may never be allowed to spin(SCGCQ00855675 ) - Ventura: IFAULT_PL_HIGH_INT_SPURIOUS fault (0x6C02 asserted(SCGCQ00855711) - PL: Format command doesn't work on SATA drives when FMTDATA bit is 0(SCGCQ00856366) - Ventura: modify some debug info(SCGCQ00856678) - Ventrura: Accessing Mode Sense pages for NVME Results in alignment fault(SCGCQ00857247) - Ventrua FPGA: hit Fault 0x5801 running Data Integrity from RedEye(SCGCQ00857273) - Firmware Controlled Spinup: GroupSpinningCount May Not Be Adjusted Correctly for Legacy SAS Drives(SCGCQ00858694) - PL: Fault 0x7C54 seen when running IO with hard resets and config reads(SCGCQ00859243 ) - PL - Incorrect register settings for Ventura(SCGCQ00859820) - Disable FwSpinupAck print for periodic notify(SCGCQ00860244 ) - Intruder A0:WriteBuffer in 'Write Data' mode executes with good status when Bufferid=0 & Param List length != 512.(SCGCQ00860454 ) - Ventura: NVMe: Some SCSI-NVMe translations throw the same error for multiple error conditions(SCGCQ00860696) - Ventura FPGA: Faults observed when powering off/on populated PCIe switch(SCGCQ00861780) - Rearrange PDB RCC interrupt handlers to avoid spurious interrupts(SCGCQ00862058) - Handle FxCore Requestor Disabled Exception that follows Submission queue timeout exception for NVMe device(SCGCQ00864142) - PL: SFF-8485 Invert Activity Mode not properly turning the LED off for no-link state(SCGCQ00864613) - Intruder A0: MEDIUM ROTATION RATE is not updated in RIGID DISK GEOMETRY PAGE When MODE SENSE(10 is executed to(SCGCQ00864828) (SATA Drive) - PL: Minor modification for the 5872 workaround(SCGCQ00865238) - Ventura: backend PCIe: FxCore may generate invalid exception 0xFF(SCGCQ00865819) - Current Config of "pl status" command output is not clear.(SCGCQ00866270) - Ventura FPGA: NumberOfSATATargets does not decrement(SCGCQ00866287) - Ventura FPGA: Fault 0x6230 while running IOs and issuing target reset task managements(SCGCQ00866294) - Ventura: When processing SAS core interrupts, sometimes status register indicates no active interrupts(SCGCQ00866361) - Intruder A0: IDLE and STANDBY CONDITION TIMER's are not updated properly in POWER CONDITION MODE PAGE for NON EPC(SCGCQ00866637 ) Drive - Change the naming of library defines DEBUG and TARGET to avoid conflicts with customers(SCGCQ00866760) - PL: High latency on non-automated SATA IO with no other IO load(SCGCQ00867571) - Ventura FPGA: 6001 fault starting IO(SCGCQ00868569) - PL: SATA I/O times out right after a Start Stop Unit command with immediate bit set to 1(SCGCQ00868995) - Ventura: backend PCIe: PL translated PCIe read/write IOs may time out(SCGCQ00869263) - Ventura FPGA: Fault 0x61A6 while running IOs and issuing target reset task managements(SCGCQ00870402) - PL: Enclosure Management bounds checking(SCGCQ00870903) - PL: Fix Out of Bound Array Access in Diagnostic Command code(SCGCQ00871318) - Ventura: Fault 0xd102 observed during IO + TM testing on direct attached NVMe drive(SCGCQ00871397) - PL: Remove unused variable in when sending SATA SCT data(SCGCQ00871675) - PL: Resize PL_TRANSNUM_UNUSED Define to 8 bits(SCGCQ00871678 ) - Ventura: backend PCIe: target reset to AHCI device times out(SCGCQ00871680) - PL: Fix bad coding style in plGetSpinupGroup(SCGCQ00871683) - PL: Remove unused variable in a firmware function(SCGCQ00871686 ) - PL: Remove unused variable from the TRIM command handler(SCGCQ00871688) - Ventura: Avoid PCIe device initialization while PCI discovery is active.(SCGCQ00871804) - Root complex port mark enabled even if all the phys are disabled in nvdata(SCGCQ00871999) - Ventura FPGA: 0x1202 fault with IOs and Random TMs(SCGCQ00872717 ) - SATL: Get Rid of Unnecessary/Duplicate Assignment Statements in SATL Function(SCGCQ00872849 ) - Ventura FPGA: 0xEC9D during PCIe task management(SCGCQ00872879 ) - Intruder A0 : Fault 0x430b while Discovery in Target Mode setup(SCGCQ00873776 ) - Host Driver Detects Target Mode Event Errors Regarding Subsystem(SCGCQ00874585 ) - Ventura: Fault 0xd024 is seen sometimes during link glitch testing(SCGCQ00874912) - Ventura: backend PCIe: IOs to an AHCI device may halt after TM(SCGCQ00876257) - PL initializes IOA Local RAM with 0s without IOP FW knowing(SCGCQ00877473) - Ventura: backend PCIe: 1901 fault on AHCI command failure(SCGCQ00878246) - NO_FPE_HW compile option updates(SCGCQ00879534) - Ventura: backend PCIe: issues related to Axi2Shell error handling(SCGCQ00880773) - Timer Overflow errors for IOs sent using pliLightStartScsiIo(SCGCQ00880811) - Ventura: backend PCIe: (AHCI firmware hangs on translated SGL full of 0-length SGEs(SCGCQ00881278) - Ventura FPGA: Fault EC30 fault followed by fault EC70 on full port cable break against an NVMe drive(SCGCQ00882972) - Ventura FPGA: IO stopping during stress(SCGCQ00883428) - Ventura: port some FPE start path fixes to PL Light(SCGCQ00886430) - PL: Spinup control has incorrect error guard(SCGCQ00886966) - Ventura: unexpected behavior may occur during PL init with non-IT IOPs(SCGCQ00887074 ) - Ventura FPGA: 'pl status' doesn't reflect hot removal of a NVMe Drive connected to a switch.(SCGCQ00888012) - Ventura: RingBuffer Print Error of Device's IO Count(SCGCQ00888114) - Ventura: port some FPE start path fixes to PL Light(SCGCQ00888286) - Unable to issue Start Stop Unit to a sata device(SCGCQ00890804) - Tiger/Stryker: Fix tiger firmware build and build all issues(SCGCQ00894132) - Ventura: backend PCIe: FPE MaxPcieCoreNum is incorrect(SCGCQ00895285) - Some PL_ASSERT Cases Could Fail To Detect Out of Range Errors(SCGCQ00896629) - pl: IT: some debug prints go missing when a trace buffer is posted(SCGCQ00901424) - Remove Random number generator feature.(SCGCQ00904420) - PL: Unnecessary conditional statement in firmware source(SCGCQ00907209) - Ventura FPGA: Fault xEF09 during phy cable glitch on NVMe direct attached drive(SCGCQ00908689 ) - BL: Tiger bootloader is locking up and causing aborts(SCGCQ00910746) - PL: Update internal files to latest specifications(SCGCQ00913173) - Tiger: Remove usages in of SUCCESS (1 and FAILURE (0 defines(SCGCQ00913505) - Ventura: Invalid Q Entry for SAS->IOA Completion Q when firmware and fast path IO's are mixed with caching enabled.(SCGCQ00915170) - Ventura: backend PCIe: reformulate switch WWID(SCGCQ00915987 ) - Ventura: Additional settings for hw workaround in SCGCQ00915170 (SAS->IOA queue full error(SCGCQ00916873) - IOP & PL: Move certain PL structures to use OCM PLB Segment 2(SCGCQ00917625) - Ventura: Dauntless min build fails with GPIO wide port group mapping changes(SCGCQ00923022) - Ventura: backend PCIe: incorrect link rate may be reported in PCIe IO Unit Page 0(SCGCQ00925861) - PL: 265D fault when injecting errors into the data stream from a SATA drive(SCGCQ00928401) - PL: Optimize Start pending I/O function to gain a few % of IOPS increase(SCGCQ00929765) - TigerStryker: Fix pl library build for liger release(SCGCQ00930678) - PL: Fix arm compiler error.(SCGCQ00931355) - PL: Ventura incorrectly stores tail pointer in head pointer(SCGCQ00932450) - Ventura: Tip code faults with 0xECA6(SCGCQ00933078) - Ventura: separate reset of CSW core from PBD(SCGCQ00933765) - PL Ventura: MultipP bit not set in Inquiry(SCGCQ00933818) - Ventura: setting CSW protocol mode does handle setting HW Mode with PCIe devices(SCGCQ00934298) - PL: Unexpected Open Reject (Protocol Not supported is observed from target mode(SCGCQ00934341 ) - PL: PL code is not supposed to use division(SCGCQ00934930) - Tiger: Fix it_fpga_dnt build error to pass build all.(SCGCQ00935031) - Tiger: PSB PEX registers mapped to incorrect AXI addresses.(SCGCQ00937890) - Ventura: Misc initial bring-up work-arounds(SCGCQ00938539) - PL: MPI device driver state machine is confusing(SCGCQ00938627) - Ventura: PL should not be looking for Phy Interrupts in SASConfigRegs(SCGCQ00940270) - Tiger/PSB function parameters where not updated when Ventura/PDB functino was(SCGCQ00940318 ) - pl: SGL debug printer ignores SkipCount(SCGCQ00941786) - Tiger: CE and FxCore init issues(SCGCQ00943870) - Ventura: Fault d053 running SATA IO(SCGCQ00944751) - Dauntless Builds Not Completely Removed.(SCGCQ00944759) - Ventura: backend PCIe: IOs to an NVMe device fail if they are larger than the device's MDTS(SCGCQ00948252) - Ventura: SATA Init Always Fails(SCGCQ00948281 ) - Trace buffer has garbage at SOD(SCGCQ00948938) - Ventura FPGA: Hitting x430A fault during Hot Plug less than 3 seconds(SCGCQ00949143) - Ventura: Data abort when booting harpoon image(SCGCQ00950072) - Tiger: PCIe discovery and configuration fixes(SCGCQ00950664) - Ventura: Fault 4308 when firmware cycle mode enabled(SCGCQ00953736) - Ventura: Fix the PBAM Inframe core activity selection mapping(SCGCQ00954393) - Ventura: backend PCIe: fix some config page related bugs(SCGCQ00954691) - Ventura: backend PCIe: need to configure link width in the DM Core before bringing up the link(SCGCQ00954714) - Ventura: backend PCIe: fix a couple of NVMe related issues(SCGCQ00979716) - Ventura: PCI links get reset when in END POINT mode(SCGCQ00981060) - Ventura: backend PCIe: intermittent IO timeout with fast path plus firmware breakup path IOs(SCGCQ00981260 ) - Ventura: backend PCIe: PL NVMe read/write breakup IOs fail badly(SCGCQ00983674) - Ventura: Remove Tx phase slip setting workaround(SCGCQ00987742) - Ventura A0: Devices are intermittently showing up or not present at all(SCGCQ00987752) - Ventura: backend PCIe: NVMe devices or PCIe switches intermittently fail to link up(SCGCQ00987792) - Ventura: backend PCIe: need to reject an NVMe device with PI or metadata enabled(SCGCQ00991188) - Ventura: SAS devices are not discovered when hot plugged.(SCGCQ00991441) - SAS IO Unit Page 1 - Phy Re-enable not working. Controller Phy does not come back online.(SCGCQ00992048) - Ventura: backend PCIe: ED08 fault occurs with backend PCIe enabled and phys disabled(SCGCQ00993194) - Ventura: Invert PBAM GPIO LED data polarity(SCGCQ00993950) - Fault 0x5841 due to Check Condition on Atapi Device(SCGCQ00994935) - Ventura: backend PCIe: link always comes up with maximum width(SCGCQ00997661) - Ventura: recursive fault on fault with backend PCIe support disabled at runtime(SCGCQ00997681) - Ventura: backend PCIe: SAS IO Unit Page 1 write causes NVMe devices to go away(SCGCQ00998568) - Tiger: Data corruption reported for NVMe IOs 8KB and higher(SCGCQ00998637) - Devices not getting discovered with PL version 0.250.54.77(SCGCQ00999505) - Ventura A0: 265D fault when running Destructive Domain test(SCGCQ01000117) - PL: Fault 0x4300 when removing SATA devices from the topology(SCGCQ01000639) - Ventura A0: Fault 0x5828 while running Quarch Cable breaker Quarter phy glitch.(SCGCQ01000813) - Ventura A0: 7C55 fault when performing port_break between HBA and expander cable break with 4K IO size(SCGCQ01001139) - Ventura A0: Fault 0x6108 while running TMs & SMP commands(SCGCQ01001258) - Adapter fails to respond to diag reset while faulted(SCGCQ01001666) - Tiger FPGA: Fault 0x6230 during initialization(SCGCQ01001972) - Ventura: Fix typo in register definition name(SCGCQ01002334) - Tiger PL: Host port config space automatically sets BusMaster and MemSpaceEn(SCGCQ01002370) - Tiger: IO failure with two or more NVMe drives.(SCGCQ01002855) - 0x430b fault is seen while running IOs & link resets on Ventura HBA Phys(SCGCQ01004126) - Ventura: backend PCIe: fault occurs when link configuration is invalid(SCGCQ01004373) - PL: Firmware doesn't compile with MPI Device support enabled(SCGCQ01004853) - Firmware crashed with PL Fault d073 when running IO on multiple R1 VDs(SCGCQ01004990) - Ventura: backend PCIe: need to verify that the page size used by PL is supported by the device(SCGCQ01005076) - PL: Devices removed if PCIe Extended Capabilities are not implemented(SCGCQ01005270 ) - Ventura A0: Fault 0xD10D when running I/O's to Target mode controller(SCGCQ01005338) - Ventura: backend PCIe: need to take PDB testmux hardware out of reset at start of day(SCGCQ01005342) - Tiger: Workaround MPT Endpoint Captured BDF reg writing quirks(SCGCQ01007350) - PL (Ventura : Inquiry EVPD 0x83 is not unique for some devices(SCGCQ01007567) - Tiger FPGA: Firmware faults with 0xD20F when posting trace buffer(SCGCQ01007596) - Ventura A0: Fault 0x670A while running TM and SMP commands.(SCGCQ01008734) - Fault 0xD102 is observed when incorrectly composed SCSI Write Buffer command is issued to a SATA drive(SCGCQ01008776 ) - 0x6001 Fault while running port glitch cable break tests.(SCGCQ01010466) - PL: IO to MPI SED attached devices fail(SCGCQ01012207) - Tiger FPGA: 0x6815 fault when we should see 0x5821(SCGCQ01012466 ) - Ventura: Sequential Writes Performance Very Low -- Expander Attached -- Single SAS Core(SCGCQ01013913) - PL: SED DevHandle translation code incorrectly translates DevHandles(SCGCQ01013965) - PDB MEM BARs not updated properly when NVDATA settings are used as a fallback method to BAR-allocation faiilure(SCGCQ01014618 ) - Ventura: backend PCIe: couple of issues related to resource configuration(SCGCQ01014981) - Tiger: TLPs from NVMe drives have incorrect requester ID on egress at host port(SCGCQ01015401) - Ventura PL: Remove deprecated MPI SED Initialization step(SCGCQ01015440) - Ventura: Sas/IOA deadlock(SCGCQ01016130) - Ventura: backend PCIe: workaround for lane breakage on backend PCIe link down(SCGCQ01017060) - Tiger FPGA: Fault 0xEE13 while initializing an MPI device with a non-zero Device Serial Number(SCGCQ01017450) - (Sata Only WRITE AND VERIFY SCSI Command Not Failed With CC for LOGICAL BLOCK ADDRESS OUT OF RANGE Condition(SCGCQ01017807) - Ventura A0: Performance Counters not working as expected(SCGCQ01018523) - Tiger Ventura: hardcoded devhandle translation needed removed(SCGCQ01018537) - Ventura A0: 583D fault when running Port Glitch cable break between expanders(SCGCQ01018657) - Tiger Ventura - Fault 0x1902 seen when receiving address/descriptor replies via FW path on Ventura(SCGCQ01018738) - PL: SMP Pass Through to SED attached expanders fail(SCGCQ01018755) - Marlin: backend PCIe: various bringup issues(SCGCQ01018771) - Ventura: backend PCIe: allowed cascaded switch count should be 1(SCGCQ01019728) - Ventura: backend PCIe: issues related to PCIe link configuration(SCGCQ01019734 ) - Ventura: backend PCIe: EC0D fault on link drop during NVMe init(SCGCQ01019754) - Tiger FPGA: New Task File Interrupt being hit (0x6815 fault(SCGCQ01020348) - PL: PCIe Device Page 0 does not clear Reserved fields(SCGCQ01021410) - Tiger FPGA: Fault 0xED07 with tip while running PCIe link configuration at Start of Day(SCGCQ01021849) - Tiger FPGA: Link status change event causing 0x6230(SCGCQ01022790) - Tiger PL: Fault 265D when configuring the backend PCIe(SCGCQ01024192) - Ventura PL: Device handle pre-allocation for SEDs can get stuck in an infinite loop(SCGCQ01024765) - Fault 0xD101 observed during IO stress while sending a read command to a SATA drive with LBA out of range(SCGCQ01025055) - Ventura: NVMe: SGL translation fails if DDR flag is set in an IEEE chain element(SCGCQ01026956) - Ventura: NVMe: SGL translation may fail with unaligned first SGE(SCGCQ01026995) - Ventura PL: Invalid reply message and fault 0x1902 seen with SED attached IO(SCGCQ01027169) - Ventura: backend PCIe: EC30 fault on surprise link down(SCGCQ01027780) - (SATA Only Fault 0x4203 observed on running heavy IOs to SATA drives with IOs causing firmware exception.(SCGCQ01029537) - PL: Fault code 0xD091 is in multiple locations(SCGCQ01029667) - Ventura A0: Pl faults with fault code 0xd10f running SAS IO(SCGCQ01031904) - Ventura Tiger: 0x265d Fault while running Task Management Test to tiger attached SATA drive(SCGCQ01032769) - Fault 0xD025 is seen while running PCIe cable break test with IO test(SCGCQ01033270) - PL: Firmware faults with code 0x265D during PCIe enumeration(SCGCQ01033445) - Ventura: backend PCIe: several issues occur during link breaks behind a switch(SCGCQ01033463) - Ventura: backend PCIe: fix a few issues encountered upon surprise removal of a PCIe switch(SCGCQ01034082) - Ventura A0: EC60 Fault when Cables Moved on Ventura(SCGCQ01034096) - Tiger PL: Internal switch is not being properly hidden from the host(SCGCQ01034219) - Ventura A0: Fault 0x620E on NVMe drive pull when I/O stress is running against all drives(SCGCQ01034404 ) - Ventura: Total pendcount incorrect for NVMe(SCGCQ01035858) - PL: FORMAT UNIT command sent to NVMe drive fails when FMTDATA bit is set to 1(SCGCQ01036201) - Tiger FPGA: Fault 6001 is seen When run IO + TM on SAS/SATA behind expander(SCGCQ01036331) - Mismatch in WWID returned in PCIe Device Page0 and PCIe Device Status Change event.(SCGCQ01037372) - Fault 0x5881 due to not handling a new interrupt(SCGCQ01038536) - Tiger Ventura: Fault when running IO to multiple Tiger/SED attached drives(SCGCQ01038568) - Ventura: backend PCIe: 61A5 fault on frequent errors involving an NVMe device(SCGCQ01039087) - Ventura: PL Fault 0000d073(SCGCQ01039143) - Ventura Tiger: Fault 0x7008 while initializing firmware with an expander attached topology behind tiger(SCGCQ01039193) - Fault during Aladin CLI commands.(SCGCQ01040069) - Tiger FPGA: Fault 265D is seen during IO and TM on SAS/SATA behind expander and IO on direct attached NVMe(SCGCQ01040974) - Ventura Tiger: Fault 0x265d when forwarding Internal Abort Task for a MID to an SSP Target from a downstream Tiger to host(SCGCQ01040995) - Ventura Tiger: Unsupported/Failed Task Managements should also be forwarded to Tiger before failing back to host(SCGCQ01041510) - Tiger FPGA: Abortable IO timeout are seen during IO and TM on SAS/SATA behind expander and IO on direct attached NVMe(SCGCQ01043036) - PL returns incorrect PCI address returned for IOP mapped resource element.(SCGCQ01043532 ) - Tiger: New code using non standard function header style(SCGCQ01043926) - PL: Some unhandled IOA interrupts were falsely generating spurious interrupt fault code(SCGCQ01043930) - Ventura: backend PCIe: miscompare may occur after link glitch between HBA and PCIe switch(SCGCQ01046343) - Ventura: backend PCIe: EC30 or EC70 fault on direct attached link down(SCGCQ01046534 ) - Ventura A0: NVMe drives missing after few Port glitches between HBA and PCIe Switch(SCGCQ01046704) - Ventura A0: NVMe drive missing after few Lane/Phy glitches between PCIe switch downstream port and Endpoint(SCGCQ01046725 ) - Tiger: IO stops to devices after link reset, drives either get removed or IO times out.(SCGCQ01047475) - Tiger: IO timeout seen when running IO with Query Task TMs(SCGCQ01047487) - PL: Mid reuse may cause data miscompare(SCGCQ01047691) - IOP: Firmware faults with 0x265D when issuing a TM to a device behind a SED which is no longer connected(SCGCQ01049418) - Tiger FPGA: Abort Task to SATA can cancel out Fast Path State Machine Expecting Zero IoCount status(SCGCQ01051203) - PL fault 0xd0d0 is seen when IOA hardware interrupts for invalid completion entry(SCGCQ01052174) - Ventura: backend PCIe: issues related to backend PCIe link handling and NVMe TM(SCGCQ01052703) - Ventura with Tiger devices attached and Fast Path disabled in IOUnit 1 results in x7008 fault on initialization(SCGCQ01056872) - Persistent Connection Timeouts Occur With Some Drives(SCGCQ01057572) - Ventura: Single/Dual context mode not set correctly(SCGCQ01057740) - Fault 0x1D02 while running port break between HBA and PCIe Switch(SCGCQ01058662) - Ventura A0: NVMe device isn’t getting reconfigured even though discovery runs and appears to find it(SCGCQ01058974) - Ventura: FW events are sent in incorrect order when DA SATA drive is hot removed(SCGCQ01059293) - FW entered PL Fault 0000d0d1 while I/Oing across LDs(SCGCQ01059682) - Ventura: 8 LUN Target Using Linux Driver Performs 10% or more slower than previous SAS3 products(SCGCQ01060022) - Asynchronous External Abort during SOD. Found during COL cycles(SCGCQ01060269) - PL: Handle plSMPPhyControlSend( return status(SCGCQ01061458) - PL: Some error conditions not logged(SCGCQ01063603) - Ventura: backend PCIe: various faults occur after a short link glitch(SCGCQ01064269) - Ventura: backend PCIe: reading config space for debug may break other PL subsystems(SCGCQ01065697) - Tiger: Fault 0x430B when unregister is attempted for an Ventura DevH for a Tiger attached drive(SCGCQ01066917 ) - Ventura: Target stalls after many hours operating at 700K+ IOPs(SCGCQ01068910) - PL: SED attached devices not removed from IOC's device table(SCGCQ01068954) - Ventura: NVMe: ARRE Bit Not Set to 1b in Read-Write Error Recovery mode page for NVMe Drives.(SCGCQ01069374) - NVMe: Allocation Length field of SCSI commands is not handled properly for NVMe drives.(SCGCQ01069397) - Ventura: Aladin CLI causes system lock up when running on Crusader(SCGCQ01069804) - If SATA_FIS_PORTING feature complied out, FxCore exception Queue will be sized to 0(SCGCQ01070394) - Ventura: B0 requires check of enqueue register before disabling queue manager state machine(SCGCQ01070612) - SCSI Read Capacity - 16 processed successffully for incorrect service action field(SCGCQ01070692) - For NVMe drives mode sense command failed for PAGE CODE=0x3F and SUB PAGE CODE=0xFF(SCGCQ01070881) - PL: SMR: Enhance the error handling conditions of SMR ReportZones SATL(SCGCQ01077555) - Ventura: backend PCIe: PCIe link associated with root port 0 sometimes fails to come up(SCGCQ01082753 ) - Ventura Tiger: Do not configure completion time limit for MPI devices(SCGCQ01083308) - Ventura Tiger: Timeouts for Internal Task Managements not set correctly.(SCGCQ01083603) - Marlin A0: HBA goes to hung state while sending diag reset(SCGCQ01084604) - Ventura PL: 0x265D fault when initializing a SED(SCGCQ01086075) - PL Tiger: Fix plPciRcGetPexPortType(SCGCQ01088652) - Tiger: Periodic DPC check renders ringbuffer useless(SCGCQ01088685) - Tiger FPGA: NVMe drives go missing as soon as IO is started(SCGCQ01089519) - PL: Some configuration pages return non-zero data in reserved fields(SCGCQ01092041) - Initialization hangs on Harpoon controller(SCGCQ01092071) - Tiger PL: SGLs with DDR DLAS never complete(SCGCQ01092466) - A 7C41 Fault occurs when an Internal IO timeout occurs(SCGCQ01093487) - Fault 0x430B observed while running IO and port glitch test between Marlin A0 and attached expander.(SCGCQ01093757) - Tiger FPGA: Fix PCIe Io Unit Page 0 Read handler(SCGCQ01095060) - Ventura: NVMe: No INQUIRY Response Seen for NVMe Drive When Executed for Non-Zero LUN.(SCGCQ01095664) - Tiger FPGA: 5002 Fault with tip code(SCGCQ01099808) - Fault 0x1901 is observed when an internal IO to a SES device fails.(SCGCQ01100151) - PL: SAS3416 Fault 0xD071 & D015 during the heavy I/O(SCGCQ01107033 - Marlin A0: Fault 0xEC30 while running NAKIncomingTLP-ModDataFCUpdate.jas script or link breaking(SCGCQ01109436) - Attached expander goes missing while performing controller phy hard resets and config page reads(SCGCQ01110176 ) - pl: device missing delay timer may expire too soon(SCGCQ01112033) - PL: I/O could timeout if task management fails(SCGCQ01113324) - Ventura: backend PCIe: add workaround for link recovery issue(SCGCQ01114258) - Ventrua A0: PL fautl xD10F observed during SAS cable pull(SCGCQ01114603) - Ventura A0: Fault 0xC010 while unloading/loading the drivers in Target mode topology(SCGCQ01116345) - Ventura/Marlin: backend PCIe: recursive fault may occur on PDB SysDma error(SCGCQ01116710 ) - Fault 0x1900 hit when IOs and Task Abort Task management requests are run on the NVMe device(SCGCQ01122538 ) - Marlin A0: 0xC010 fault during EEDP Initiator --> Target test(SCGCQ01126480) - Ventura: backend PCIe: need to perform PCIe related workaround for reasons other than the original issue(SCGCQ01126828) - Ventura/Marlin: Fault 0xECD0 seen if switch goes away before all NVME drives attached registered with host.(SCGCQ01126840) - Ventura B0: FPE SAS completion queue should be in ILR(SCGCQ01127400) - Ventura/Marlin: backend PCIe: work around a link down issue(SCGCQ01134422) - Ventura: backend PCIe: IO timeouts may occur with NVMe devices under Linux(SCGCQ01134727) - Fault xD060 seen when doing NVME glitching(SCGCQ01134928) - PL: MidUsed not cleared when handling FPE Requestor Error(SCGCQ01134948) - Ventura/Marlin: backend PCIe: start of day mem allocation with backend PCIe disabled(SCGCQ01136170) - Ventura B0: Misc active cable management fixes(SCGCQ01137484) - Ventura A0: Not all slots are enumerated with SIO group ID for odd/even PHY connector lane routing(SCGCQ01138057) - Marlin A0: Switch attached NVMe drives are not discovered from Build 73.(SCGCQ01138330) - Ventura/Marlin: backend PCIe: reliability of link bandwidth change notification(SCGCQ01138343 ) - PL: Data abort exception while pulling JBOD(SCGCQ01138634) - SAS/SATA drives not discovered(SCGCQ01140463) - PL: Hard/Link reset on HBA phy failing with IOCStatus = 0008 (Invalid State(SCGCQ01146367) - pl: 265D fault if PDBs are unmapped with backend PCIe support disabled(SCGCQ01147668) - Ventura/Marlin: backend PCIe: need modification to hot reset/link down workaround(SCGCQ01149992) - Ventura B0: Task Management errors with no exception while running IO's on I/T setup(SCGCQ01152173) - Added new PL fault code and also set default 60 secs for SATA hinting timer in PL(SCGCQ01152796) - FW fault 0x265d when unplugging active cable(SCGCQ01154156) - pl: 265D fault when host booting firmware on a board with a blank flash(SCGCQ01154569) - Fault 0x670B seen while sending SCSI Read Buffer commands to bunch of SATA drives(SCGCQ01163838 ) - PL: Incorrect LogInfo may be returned during handling FPE Exception IO(SCGCQ01165427) - Ventura: Implement hardware workaround for SAS Training failure(SCGCQ01168045) - PL: Possible null pointer access in a non-automated SATA Response Frame(SCGCQ01168086) - PL: Unchecked function return value in sata code(SCGCQ01169267) - Ventura/Marlin: NVMe: completion queue head doorbell may not be written in a couple of error cases(SCGCQ01170592) - Virtual SES support can cause Fault 0x7200(SCGCQ01171097) - Host trace buffer does not contain expected data(SCGCQ01174473) - Starting Task Managements take a long time in certain conditions(SCGCQ01176191) - PL Fault 0xd073 is seen during certain IO load conditions(SCGCQ01180058) - Ventura: PL fault 5811(SCGCQ01184674) - pl: 4311 fault may occur when both SAS and NVMe are enabled(SCGCQ01186198) - PL: 0x7C71 Fault During Repeated Phy Resets with Mixed SAS/SATA(SCGCQ01187303) - Ventura: backend PCIe: link recovery issues(SCGCQ01188928) - pl: delay loop may have twice the expected duration(SCGCQ01192571) - Ventura: backend PCIe: NVMe devices may not show up in Windows(SCGCQ01192659) - PL: Fault 5814 while multipath SAS pull/push of 2 enclosures(SCGCQ01193764) - Ventura B0: Observed fault 0x4A00 during Phy glitch between HBA and Expander(SCGCQ01194893) - Ventura: PL – PCIe Topology Polling incorrectly enabled(SCGCQ01194941) - Ventura B0: PL Fault 0x6001 for NVMe drives running Ios and random Task Managements(SCGCQ01196113) - Virtual SES Target Not Reported to the Host(SCGCQ01197507) - pl: Unexpected SAS link operation with protocol cycling enabled(SCGCQ01198352) - Ventura: RxCtxMgr debug print is printing an un-initialized variable(SCGCQ01198393) - Ventura: backend PCIe: compatibility tweaks for NVMe devices(SCGCQ01201787) - Ventura: backend PCIe: device add event is generated for a backend PCIe switch(SCGCQ01201813) - Ventura: backend PCIe: various issues may occur if multiple switches have the same Device Serial Number(SCGCQ01202401) - Ventura: backend PCIe: various faults may occur after a link disturbance(SCGCQ01206536) - Ventura: backend PCIe: NVMe IOs may halt when a backend PCIe link recovery occurs(SCGCQ01206643) - Ventura (Sata Only : Internal Device Resets observed on SATA Drives during I/O.(SCGCQ01207972) - IOs failed to host with generic open fail log info(SCGCQ01208362) - Ventura: backend PCIe: unable to print switch registers for debug(SCGCQ01209215) - Fault 0xEC3D seen during switch initialization(SCGCQ01210423) - Ventura B0: MR FW is hitting a data abort crash during boot up and discovery(SCGCQ01210439) - Ventura B0: BTL is not assigned to expander(SCGCQ01211588) - Ventura: PCIe Device unregister failure(SCGCQ01214268) - Ventura B0: vSES target not getting exposed in Linux Host(SCGCQ01214419) - Validate mid in Tx openfail cleanup(SCGCQ01215592) - 0xEC84 Fault observed when PCIe switch is Powered OFF and Powered ON(SCGCQ01216678) - PL Fault 0xEC07 found while Push/Pull of JBOD with IO's(SCGCQ01217170) - Intruder compile error in plVirtualSes.c(SCGCQ01219448) - PL: Passthrough I/O could timeout if DST is placed in OCM(SCGCQ01219643) - Handle FPE IOP start queue full condition(SCGCQ01222231) - PL Fault 0xd077 is seen while drives are pulled with IOs outstanding(SCGCQ01222435) - Ventura: backend PCIe: link recovery testing issues(SCGCQ01222761) - Diag Reset observed while sending TM to NVMe drives(SCGCQ01223373 ) - Fault seen when handling Task Managment with IOs to NVME drives when drive reports media errors.(SCGCQ01226478) - Ventura/Marlin: backend PCIe: EC84 fault(SCGCQ01229418) - Ventura B0: vSES firmware sending incorrect SCSI state while completing INQUIRY with UNDERRUN(SCGCQ01230819) - GPIO HD Cable management function does not support active high level.(SCGCQ01231609) - Ventura B0: backend PCIe: link gets stuck down after a link break(SCGCQ01231751) - Ventura/Marlin: backend PCIe: build fails if a specific workaround is disabled(SCGCQ01232334) - FPGA Compile Error(SCGCQ01233994) - Ventura/Marlin: backend PCIe: switch resources may remain allocated after it is removed(SCGCQ01235267) - Ventura/Marlin: backend PCIe: target reset may time out if device is partially initialized(SCGCQ01235889 ) - pl: NVMe: Abort Task may abort an IO when it is still outstanding at the device(SCGCQ01235948) - Fault 0x6001 while running IOs and TMs to NVME drives with media errors.(SCGCQ01238263) - PCIe device page 0 field may not report devices link number(SCGCQ01239126) - Fault 0xe989 is seen if media errors are seen while running IOs to NVMe drives(SCGCQ01239353 ) - Data Protect Sense Key received on power up of NVME drive(SCGCQ01239795) - Memory allocation of 5 NVME drives is required to discover 4 drives when VPP LED management support is enabled.(SCGCQ01240626 ) - PL Fault 0000430b(SCGCQ01240774) - SAS Topology gets hung because of a firmware fault in sas3516 controller(SCGCQ01241342) - pl: NVMe: fix a couple of issues exposed by a malfunctioning device(SCGCQ01243546) - SSC Profile and PLL BW Selection(SCGCQ01243603) - Ventura B0: vSES Target: Incorrect Sense Data for REQUEST SENSE SCSI Command(SCGCQ01247631) - Ventura: Auto backplane detection - Disable PCIe RefClk for non-NVMe configurations(SCGCQ01247682 ) - pl: FPE timer may be activated for an IO that is being aborted(SCGCQ01249183) - PL fault 0xe989 hit with cable push/pull(SCGCQ01249805) - Fault 0xD073 with IOs to NVME drives with media errors.(SCGCQ01249813) - Add option to enable support for OEM specific NVMe Enclosures testing(SCGCQ01250846) - Fault 0x265D while powering on/off the attached PCIe switch devices.(SCGCQ01251456) - Marlin: Add additional support for cold boot fix(SCGCQ01251641) - NVDATA config option to disable PL Virtual SES support(SCGCQ01251655) - Ventura B0: Fault 0x430B while running IOs & Hard resets of HBA Phys(SCGCQ01254319 ) - pl: NVMe: D015 fault during Abort Task(SCGCQ01255908 ) - Ventura MR 7.1, RHEL 7.2: SAS/SATA HDD R0/10/5, OLTP, Q >= 16, Up to -50% IOPs Regression (L13, W33(SCGCQ01255912 ) - IO Timeout while sending Task Managements to PCIe devices(SCGCQ01256214) - pl: task management may not complete with heavy IO load(SCGCQ01258861) - 4K SATA block read error(SCGCQ01258955 ) - Ventura/Marlin: extra barrier in FPE firmware IO start path(SCGCQ01259570 ) - Ventura/Marlin: backend PCIe: link not reinitialized after certain errors(SCGCQ01259639) - VSES diag page 0A mapping not enabled for NVMe devices(SCGCQ01261033) - Ventura B0: OS boot fails with latest HBA FW (02.250.02.00(SCGCQ01261816) - Fault 0xECA0 is hit while running IOs on NVMe drives behind Ventura(SCGCQ01266097) - Ventura: Slot status LED updates fails with mixed backplane types (VPP and SGPIO in the same server config(SCGCQ01266429 ) - Ventura/Marlin: backend PCIe: completion timeout disable support failure(SCGCQ01269306) - Fault 0xD372 is seen during NVMe IO run and drive push pull test(SCGCQ01271759) - Ventura/Marlin: backend PCIe: NVMe devices aren't discovered with VSES disabled(SCGCQ01274107) - Checks for reconstruction in place.(SCGCQ01276354) - IOMMU fault at address 0x80360000(SCGCQ01279547) - Make platformtype function available to test utility(SCGCQ01282492 ) - Data loss during cache offload power cycle test(SCGCQ01286491) - pl: NVMe: Task Set Full handling flag not respected for NVMe(SCGCQ01289543 ) - pl: excessive exception generation during SATA IOs with Task Set Full handling disabled(SCGCQ01291127) - Ventura/Marlin: backend PCIe: EC0E fault may occur on link down(SCGCQ01292448) - FW goes to data abort when power cycle the enclosure.(SCGCQ01294834) - Enclosure ID changes when a cable pull and insert occurs.(SCGCQ01295290) - MR-7.2: iMR 9440-8i:Hit MonTask line 662 in file ../../raid/mficmd.c rst=0 After Upgrade The Driver & Reboot The System(SCGCQ01299168) - Ventura: backend PCIe: EF53 fault on link down(SCGCQ01301079) - (NVME Only Port enable completes before drive is detected by discovery.(SCGCQ01301777) - pl: NVMe: port enable times out if an NVMe device fails with CFS during NVMe init(SCGCQ01303837) - pl: NVMe: EC0F fault occurs during task management(SCGCQ01303943) - MR7.1: Unexpected event for lun not ready Sense: 2/04/02(SCGCQ01304550) - Ventura/Marlin: backend PCIe: potential unexpected EF50-EF54 faults(SCGCQ01304678) - Disable SATA FIS poritng on a SATA drive connected to a Broadcom expander with EDFB enabled.(SCGCQ01307008) - 14G:SWPT: Enclosure hotremoved and insert it back,one physical disk is missing in storage inventory.(SCGCQ01309090) - Incorrect DmDevSMPReady array size(SCGCQ01310496) - Due to a timing issue a hang condition may occur on cold power up(SCGCQ01311156) - Assertion failure in ../../dm/mpt2/mptframe.c at line 788: id!=MPT_FRAME_ALLOC while enclosure powercycle.(SCGCQ01311481) - Readjusted profile LD count to produce 240 VDs correctly(SCGCQ01315995) - Due to a timing issue a hang condition may occur on cold power up(SCGCQ01316806) - Marlin B0: 0x4310 fault on fwHostBoot post clean flash on FW: 03.250.01.00(SCGCQ01318643 ) - CSET Aggregator: SCGCQ01297325, SCGCQ01289572(SCGCQ01318920) - Consolidating CSETs from OEM stream to 7.1 Channel(SCGCQ01318925 ) - Consolidating a subset of CSETs from OEM stream to 7.1 stream(SCGCQ01318990) - Consolidating CSETs from OEM stream to 7.1 stream(SCGCQ01319003) - Consolidating CSETs from OEM stream to 7.1 stream(SCGCQ01319859 ) - Disable fw messages "cmdId:5e has different completion status for sub commands" when convert 240Pds to Jbod and reboot(SCGCQ01320953) -(SCGCQ01324136) - Controller montask after data abort exception handler was called(SCGCQ01324312) - Fix Static Code analysis issues(SCGCQ01325320) - SCons: Doxygen Builder fails to keep track of dependencies(SCGCQ01326891) - MR-7.1: FW exception when power off/power one last cascaded drives enclosure on SLES 12 SP1 x64(SCGCQ01326930) - Mode page access to same devId needs to be serialized(SCGCQ01329539) - PKG 465\ When a Migration starts fw eventually breaks(SCGCQ01329544) - Expander FW update fails with "The expander firmware update failed while downloading the firmware to controller" error(SCGCQ01330666) - Ventura: Task Management to NVMe drives may not complete(SCGCQ01330747) - 7.3: Need to adjust ProfileMaxDevices for Profiles other than 240 VD Profile(SCGCQ01330851) - iMR-7.1-FW: DmRecoverIoError(retr 1 messages printed out every 5 minutes while system is iddle and without VDs(SCGCQ01331455) - Fixed SAS cleanup code to skip the PCI device instances.(SCGCQ01332893) - PA1: fw hit PL D10D while format partition(SCGCQ01333872) - 8G offload changes ONFI offsets - causing incompatibility across 7.x stream(SCGCQ01336017 ) - Need interrupt to fire when OCM flush is complete(SCGCQ01336830) - Crusader: fw Assertion failure in ../../raid/ld.c at when insert pd(SCGCQ01337840) - PCIe SSD Fails to blink Bad Phy after 5 minutes, on Passive BP with internal adapter(SCGCQ01339684) - Assertion failure in ../../dm/src/FindDev.c at line 261 while connecting 10 enclosures to the system(SCGCQ01342054) - Ventura MR 7.3 - SW R10 8x Direct attach HDD WB 8K 256QD 30% regressions(SCGCQ01342174) - MR7.1 : MemsetECache prints fill important termlog space(SCGCQ01342196) - After send command to PD to clear LED, don't poll for completion(SCGCQ01342947) - 7.3 pk484 unxpctd c_ptr 19804640 tgtId ef while migrate from 2DR1 -> 4DR6(SCGCQ01343118) - DEV Defect to address Code Collab defects/comments for CQ# 1304715 & 1320083(SCGCQ01343240) - mix mode: NVMe pd turn to foreign config after couple of OCR.(SCGCQ01344064) - 7.3: FW hit KA when insert SAS for multipath with 48JBODs in controller(SCGCQ01347504) - FW changes to make NVRAM baselines between 7.3 and 7.1 in sync(SCGCQ01348744 - Dev Defect: Don't refer LMID before dism start in the case of device hot plug(SCGCQ01350309) - Second Reconstruction starting but no progress(SCGCQ01351330) - MR7.3 Controller is not detected after running overnight cable pull(SCGCQ01352931) - MR7.3 NVME drives in Fast Path iops drop to 0 while in megamon(SCGCQ01353696) - NVME profile B was not shown to user(SCGCQ01354313) - MR 7.3_FW_PA4: MonTask: line 332 in file ../../raid/taskman.c rst=0 during Patrol read with IO's on 240 VD with media errors.(SCGCQ01356270) - WA for specific enclosure SES Command 0x1D(SCGCQ01356733) - System hangs at "Initializing FW Interfaces" with pinned cache present.(SCGCQ01361595) - Join Mirror functionality not working(SCGCQ01368560) - dereferencing uninitialized pointer(SCGCQ01373232 ) - 7.3 pk564 Crusader taskman when remove sas cable in multipath(SCGCQ01376326) - Restore nvram flag allowOnlineCtrlReset after set factory default completes(SCGCQ01378753) - lastDmaChannel is updated by both cores without a semlock(SCGCQ01378860) - Bad drive causes system to hang on boot.(SCGCQ01381151) - Initiate ocr when FW enters MonTask(SCGCQ01381615) - FW hangs when running a negative test case adding a 5th enclosre to one of the ports(SCGCQ01385667) - StorCLI show profile 13 with 8 NVMe drives support(SCGCQ01392900) - In NVMe only profile not able to see the profile in profile get list.(SCGCQ01393547) - MR7.3: 4k PD Configuration can't be imported from iMR to MR Controller. However, it can be imported from MR to iMR(SCGCQ01395842) - Offload descriptors are 64 bit in size, resulting in offload errors.(SCGCQ01397850) - Virtual Address overlap results in skipping DDR ECC error checks when cache is dirty(SCGCQ01400126) - Data flush to drives after cache offload taking ~250 seconds.(SCGCQ01401796) - Update nvram.h with correct size for curAdpPersonality(SCGCQ01404432) - MR FW: Enable RMC logging for OEM(SCGCQ01405061) - BusReadWriteSW( is not reading back the data that was written to make sure data is flushed through PCI buffers(SCGCQ01405191 ) - The Auto Config feature not present in HII(SCGCQ01406286) - Certain boards failed manufacturing screening due to Micron M83C-R NAND flash manufacturer ID being 0(SCGCQ01407825) - Reduce number of block-pairs used for 8GB offload(SCGCQ01408312) -(SCGCQ01411542) - Raid Map and Pd sync are updated for every OCR(SCGCQ01415120) - OEM controller shows random slot number inside HII after hotplugging enclosure(SCGCQ01415422) - NVDATA: Change Default SGPIO electrical driving strength from 50 to 66 Ohm per HW team recommendation(SCGCQ01418180 ) - Revert SCGCQ01418180 for 3616 and 3508 XSD, 3408 and 3416 remains the same.(SCGCQ01424266 ) - Disable OOB FW download.(SCGCQ01424907) - Prepare ONFI Memlist to offload 8GB DDR region such that DDR size is uniformly distributed across ONFI devices(SCGCQ01428498) - OEM controller has incorrect drive enumeration with single IOM(SCGCQ01431119) - Bugzila 112779 - [SAMSUNG PM863A SSD can not show the "Part Number"/ "FRU Number" information under XCC web w(SCGCQ01435624) - Constant print "phy 8 disabled" in tty log(SCGCQ01438991) - Incorrect grammar in post message(SCGCQ01444273 ) - 9460-8i card connect drive through direct-attached backplane: error LED not on when drop out a drive.(SCGCQ01445040 ) - Single Thread MSI-X and MCTP accesses(SCGCQ01446273) - Change CACHE_HEADER_VERSION from 13 to 11(SCGCQ01465054) - 930-16i Cannot Spinup HDD During System Power On(SCGCQ01470741) - When update Toshiba SAS 2.5" 10K 12Gbps 300GB HHD (PN:SH20J34185 controller hangs(SCGCQ01515259) - SPV: Fault 0x0501 when drive is pulled.(SCGCQ00135004) - 1901 Fault due to a Port open fail interrupt without a matching transport error.(SCGCQ00136195 ) - Thunderbolt B0: Implement workaround from BT1682(SCGCQ00138062) - Status FIS filelds are zero SATA Passthrough reply for PIO-in cmds(SCGCQ00141209 ) - Correction to Diagnostic Code to Show PL Memory Details(SCGCQ00145990 ) - BT1680: 6001 fault(SCGCQ00146564) - Fix 6202 fault when sending I/Os to a SATA drive(SCGCQ00146780) - PL Lib build fails(SCGCQ00146819) - ON_TASK_MANAGEMENT_INACTIVE Notification Not Being Sent To CudaMgr(SCGCQ00146956) - Possible 0xD093 fault(SCGCQ00147128) -(SCGCQ00148155) - Fault xD091 seen while running IO(SCGCQ00150094) - Device add/remove testing results in a fault 0x6202.(SCGCQ00151026) - (Sata Only : Fault 0x265D on sending Read(16 with LBA greater than 48 bit(SCGCQ00151324 ) Version 50.2.1-1026 - Moderate Impact/Low Probability of Occurrence ------------------- BIOS: 07.02.03.1_4.17.08.00_0x07020401 UEFI Driver: 0x07020401 HII: 07.02.05.01 MR FW: 5.020.01-1219 PACKAGE=50.2.1-1026 Fixes: - Purley Cosmo/Cable/Cyborg/Ventura Raid card 530-8i loss during MQT2 Test (Bug 123240) Version 50.2.1-0925(Only for Proton System) - Moderate Impact/Low Probability of Occurrence ------------------- BIOS: 7.02.03.1_4.17.08.00_0x07020401 UEFI Driver: 0x07020401 HII: 07.02.05.01 MR FW: 5.020.01-1130 PACKAGE=50.2.1-0925 Fixes: - Purley Proton Raid card 530-8i loss during MQT2 Test Version 50.2.1-0601 - Moderate Impact/Low Probability of Occurrence ------------------- BIOS: 7.02.03.1_4.17.08.00_0x07020401 UEFI Driver: 0x07020401 HII: 07.02.05.01 MR FW: 5.020.01-1045 PACKAGE=50.2.1-0601 Fixes: - R0 HDD WB-Switching between cases of IO going to cache and bypassing cache happens frequently on certain profiles (SCGCQ01138581) - Multipath SAL script failed (SCGCQ01177445) - manufacturing info for enclosure is showing zeros under SMP passthru menu in Storelib. (SCGCQ01188954) - ESXi 6.0 U2 or ESXi 6.5 hangs during reboot (SCGCQ01214236) - Progress time for CC/BGI is inconsistent with Rebuild/Copyback (SCGCQ01220611) - Controller hangs during OCR (SCGCQ0122920)5 - controller hangs (cannot get into debugger) after running i/o for a few hours (SCGCQ01229276) - MR7.1 UEFI BIOS Is Not Shown for OEM controller (SCGCQ01229284) - CLI reports "Support LargeIOSupport" as No (SCGCQ01229311) - Critical Message = " Error restoring offload cache " during MedusaIO running to R50 with power loss (SCGCQ01229975) - Change OEM_MERCURY Check to IoPathFlagOemMercury (SCGCQ01230006) - The QDChanged flag is never reverted back to 0 (SCGCQ01230078) - Next LD is not set while PD rebuild is in progress and the current LD is deleted. (SCGCQ01231043) - Fix to fail back pre read call back graciously when there are unrecoverable errors are hit (SCGCQ01231653) - During learn cycle, the battery does not discharge. (SCGCQ01232276) - NVMe: DC found when running Chaos on R5-WT-DIO-NORA with IO/Buffer size of 16kb or less (SCGCQ01232376) - Drive Firmware Upgrade fails while running IO's on a JBOD drive. (SCGCQ01232733) - Unable to see any option for Crypto erase in HII for any HDD/SSD ISE drive (SCGCQ01233384) - Assertion failure in ../../mros/mem.c at line 617: mb->tag==tag after update to new ROP 270 and reboot (SCGCQ01235357) - Performance Reduction seen in BST (SCGCQ01235742) - Defect port from mainline (SCGCQ01235761) - Max NVMe drive support shows as 8 for MR 7.1 for NVMe profile (SCGCQ01236604) - some SATA ISE drives are not displaying as ISE capable (SCGCQ01237004) - NVMe 9440-8i Rebuild does not start on 2 drive R1-Win7 (SCGCQ01237009) - Locate PD does not work with SGPIO backplane (no blinking LED) (SCGCQ01237036) - Loss of access to PI VD causes crash (SCGCQ01237965) - OOB discovery fails (SCGCQ01238858) - PL rejecting cmds due to invalid values in structure members (SCGCQ01240309) - Multiple VDs created over idrac with racadm fails (SCGCQ01241098) - Print DirtyCache status (GPIOA6 )during controller Initialization (SCGCQ01241691) - Set mdts value to 128KB in case any drives has higher mdts value (SCGCQ01242011) - DC observed on R10 VD, post importing the foreign configuration after Megamon triggered OCR (SCGCQ01242067) - Redundant path broken for PD 00(e0x40/s0) message for OS Disk when removing a known bad SATA SSD from a different slot. (SCGCQ01242091) - Excess prints slows controllers response to host commands. (SCGCQ01242470) - C10 - FW crashing at "Assertion failure in ../../hw/main.c at line 606: 0" during looped cache offload test (SCGCQ01244311) - Set mdts value to 128KB in case any drives has higher mdts value (SCGCQ01245535) - Drives not getting discovered after OCR/Reboot in iMR controller with 295 Fw package. (SCGCQ01247494) - OOB Storage Configuration - Unable to create 3 x 14PD, 42 drive simple RAID10 VD. (SCGCQ01247647) - PRequest message shows numerous times in log (SCGCQ01249133) - Fatal firmware error: Line 934 in ../../cpu/arm/exceptions.c while importing foreign config with pinned cache (SCGCQ01249809) - Kill adapter found while running CC on VD's with media errors (SCGCQ01249815) - Continuous Prints observed during Reconstruction operation. (SCGCQ01249820) - Inconsistencies in foreign configuration import when cache is pinned. (SCGCQ01249966) - Initiatlize partition map during PD Replace within LD (SCGCQ01250193) - GetAllLDAllowedOperation call in Storelib is not returning Allowed operations when some LDs are deleted (SCGCQ01250559) - iMR cable pull IO Drop on VDs (SCGCQ01250688) - Hibernate Feature in Windows 7 doesn't work properly, if IO's are running in background (SCGCQ01251505) - Issue - OLTP performance is less than Intruder by 10-20%. (SCGCQ01252558) - Hitting Kill adapter for importing Foreign configuration and query controller information( IO was not running ). (SCGCQ01253096) - FW Kill Adapter observed while performing the RLM operation on OS VD from R1 to R0 (SCGCQ01253798) - Life Cycle 3.00.00 Build 24: Redundant VD shows as FAILED State, when its actually Degraded. SCGCQ01253921 - Controller enters MonTask during Rebuild on PI enabled VD (SCGCQ01255170) - Profile ID update Event doesn't reflect prior profile ID (SCGCQ01255917) - CC is not correcting DIFF errors after reporting them as corrected. (SCGCQ01256210) - WG: In case of preview, FW should not return "MFI_STAT_CTRL_RESET_REQUIRED" status code : MR Ventura (SCGCQ01256323) - FW breaks into montask with fusion MU error - data descriptor overflow error.. (SCGCQ01256286) - FW hit "C0:MptIssueCmd: ERROR!!! Unknown command x0 in Rdm=x7fb95780" upon booting up (SCGCQ01259277) - SBL bus init leads to system hang and BST failure (SCGCQ01259726) - RSOD been observed after disabling Data protection on PI enabled VD (SCGCQ01260419) -: ddf while remove 2nd pd in 2DR1,4DR10 for pinned cache (SCGCQ01261386) - Improvements for offload/restore reliability (SCGCQ01262608) - There is mprintf error (printing a message) that is causing this TLB error during error recovery for sanitize. (SCGCQ01263180) - Create slot id to pd mapping for NVMe drives (SCGCQ01263802) - Storcclif start diag DMA Test failed (SCGCQ01264038) - Disable BIOS flag in Megamon ( dbgflag biosDisable 1 ) successfully set but it is not actually working (SCGCQ01264139) - After performing Clear/PD erase on SATA SSDs system hangs (PL Fault) (SCGCQ01264210) Version 50.0.1-0381-1 - High Impact/High Probability of Occurrence ------------------- BIOS: 7.00.09.0_4.17.08.00_0x07001600 UEFI Driver: 0x07001600 HII: E7.00.38.01 iMR FW: 5.001.01-1025 PACKAGE: 50.0.1-0381 - Fixed a package issue that would attempt to update unsupported devices. Version 50.0.1-0381 - High Impact/High Probability of Occurrence ------------------- BIOS: 7.00.09.0_4.17.08.00_0x07001600 UEFI Driver: 0x07001600 HII: E7.00.38.01 iMR FW: 5.001.01-1025 PACKAGE: 50.0.1-0381 - Fixed an issue where the controller could hang while importing a commissioned hot spare drive. (SCGCQ01393703) Enhancement(s) - Implemented a workaround for a device attached between the root complex and the controller; in order to addresses the issue of the controller going to Gen 1 speed during D3 Hot state transition due to an issue with IDT timer. (SCGCQ01401585) Version 50.0.1-0378-1 - Moderate Impact/Low Probability of Occurrence ------------------- BIOS: 7.00.09.0_4.17.08.00_0x07001600 UEFI Driver: 0x07001600 HII: E7.00.38.01 iMR FW: 5.001.01-0888 Package: 50.0.1-0378 Version 50.0.1-0374 - New Function Only/No fixes ------------------- BIOS: 7.00.09.0_4.17.08.00_0x07001600 UEFI Driver: 0x07001600 HII: 07.00.38.01 MR FW: 5.001.01-0805
Lenovo Data Center Group Linux OS Support Home Page |
| linux.lenovo.com |
© 2018-2019 Lenovo. All rights reserved |
ThinkSystem RAID and ServeRAID M Series SAS/SATA Controllers Driver for Linux This product supports [RHEL 7.3, 7.2, & 7.1] Adapters Supported: - ThinkSystem RAID 930-8i 2GB Flash PCIe 12Gb Adapter - ThinkSystem RAID 930-16i 4GB Flash PCIe 12Gb Adapter - ThinkSystem RAID 930-24i 4GB Flash PCIe 12Gb Adapter - ThinkSystem RAID 930-8e 4GB Flash PCIe 12Gb Adapter - ThinkSystem RAID 930-4i 2GB Flash Flex Adapter - ThinkSystem RAID 730-8i 1GB Cache PCIe 12Gb Adapter - ThinkSystem RAID 530-8i PCIe 12Gb Adapter - ThinkSystem RAID 530-8i Dense Adapter - ThinkSystem RAID 530-4i 4GB Flex Adapter - ServeRAID M1215 SAS/SATA Controller for Lenovo System x (46C9114) - ServeRAID M1210e SAS/SATA Controller for Lenovo System x - ServeRAID M5225 SAS/SATA Controller for Lenovo System x (00AE938) - ServeRAID M5210 SAS/SATA Controller for Lenovo System X (46C9110) - ServeRAID M5110 SAS/SATA Controller for Lenovo System x (81Y4481) - ServeRAID M1115 SAS/SATA Controller for Lenovo System X (81Y4448) NOTE TO SERVICE - Reference RETAIN #N/A Version 7.703.07.00- Moderate Impact/Low Probability of Occurrence --------------------- fixes: - Send sense buffer upper 32bits inside IOC INIT frame.(SCGCQ01315987) - MR: On OEL 6.x/7.x with UEK kernels - megaraid_sas.conf file from the kmod rpm does not match kernel version.(SCGCQ01319368) - pass upper 32 bits of version buffer and system information buffer to FW inside IOC INIT frame.(SCGCQ01326366) - Workaround changes for FW MFA frame pull issue.(SCGCQ01338087) - Log dmesg if IOC INIT fails in IOMMU and RDPQ enabled enviornment for user information only.(SCGCQ01338097) - Validated if any of DMA buffers pool which should be in same 4GB region does not cross 4GB boundary.(SCGCQ01338372) - Memset to zero for MFI command frame for IOC INIT and use lower_32_bits() macro to get lower 32bits of DMA address passed to FW.(SCGCQ01341287) - Removed Crusader ID(device ID- 0x0015) from supported PCI IDs of MR7.2 linux driver.(SCGCQ01350963) - MR7.3: Code review defect - ioc_init_frame not freed during kernel module unload.(SCGCQ01384694) - MR7.2: In megasas_issue_tm() SMID needs to be used for Task abort case only.(SCGCQ01315252) - Incorrect processing of IOCTL frames for SMP/STP commands.(SCGCQ01383823) - Set cmd_status inside DCMD/IO/header frame to MFI_STAT_OK to wake up all pended IOCTLs.(SCGCQ01298582) - Removed print "Failed from megasas_complete_cmd" from PD CFQ sequence DCMD completion path.(SCGCQ01321565) - Do not switch DMA mask to meet same 4gb requirement. IOMMU does not work well with such DMA mask switch.(SCGCQ01342578) - Allocated MFI frame size and the size of MPT chain frame(Where MFI frame resides for MFI MPT passthru commands) should match.(SCGCQ01342650) - Minimum possible value for module parameter- resetwaittime should be 1 secs instead of 0 secs.(SCGCQ01344137) - Set DMA mask after FW is in READY state in PCI resume path of megaraid_sas driver.(SCGCQ01389431) - MR7.3: Data miscompare found with WB secure VD RAID 1 with LSA sending IOCTLs in parallel.(SCGCQ01378684) EnhancementRequests: - Added support for 64bit DMA mask for invader.(SCGCQ01294199) - MR7.3: add support for Citrix XenServer 7.1 OS.(SCGCQ01257971) - Send current time to FW during IOC init.(SCGCQ01307072) - Added support for RHEL7.4.(SCGCQ01455156) - MR7.3: add support for OEL 6.9.(SCGCQ01289005) - Added support for threaded interrupts.(SCGCQ01498747) - Added support for 64bit DMA.(SCGCQ01301940) - Added support for SLES12 SP3.(SCGCQ01455167) CSETActivities: - Set cmd_status inside DCMD/IO/header frame to MFI_STAT_OK to wake up all pended IOCTLs.(SCGCQ01381770 port of SCGCQ01298582) - MR: On OEL 6.x/7.x with UEK kernels - megaraid_sas.conf file from the kmod rpm does not match kernel version.(SCGCQ01320324 port of SCGCQ01319368) - Use IOC_INIT frame once driver has verified IOC_INIT frame allocation was successful.(SCGCQ01455132 port of SCGCQ01430747) - Updated correct supported kernel version of Ubuntu16.04 in driver's document- OS_support_list_mr7.5.txt.(SCGCQ01455206 port of SCGCQ01454090) - Added NVME passthru support in MR linux driver.(SCGCQ01455135 port of SCGCQ01407028) - Updated OEL6_UEK and OEL7_UEK buildkit.(SCGCQ01443433 port of SCGCQ01439776) - Minimum possible value for module parameter- resetwaittime should be 1 secs instead of 0 secs.(SCGCQ01344142 port of SCGCQ01344137) Version 7.702.06.00- Moderate Impact/Low Probability of Occurrence --------------------- Defects (47) - Reset MPT frame field cmd_completed while retrurning it back to free pool.(SCGCQ01176530) - Optimized R1 FP write code.(SCGCQ01191077) - Before populating driver RAID map copy memset drv_map to zero and ldTgtIdtoLd array to 0xff(SCGCQ01204087) - Initialize stream detection array properly.(SCGCQ01204096) - On SPARC/Big endian host, need to convert peerSMID to little endian to CPU before accessing(SCGCQ01216698) - Fixed coverity reported issues and changed name of few functions.(SCGCQ01219231) - Don't set tm_capable for JBDO when PD CFG SEQ map is not available(SCGCQ01226222) - Remove local defination FALSE/TRUE and use OS provided false/true.(SCGCQ01256130) - Used vmalloc for crash dump buffers and driver's local RAID maps(SCGCQ01270059) - Reduce size of fusion_context allocation during driver load by moving load_balance_info array out, and try vmalloc if kmalloc fails.(SCGCQ01183280) - Flooding of messages- "BRCM: IO does not end on page boundary; sge_len" while running RAW IOs.(SCGCQ01189815) - Fixed data corruption by asking OS not to do merging of IOs to avoid SGE holes(SCGCQ01231229) - Code review defect: create separate function for allocating RAID maps(SCGCQ01282924) - Removed Crusader ID(device ID- 0x0015) from supported PCI IDs of MR7.2 linux driver(SCGCQ01350963) - Updated OS to send page aligned SGEs by calling blk_queue_virt_boundary(SCGCQ01206279) - Use vmalloc followed by memset to zero instead of vzalloc in driver code.(SCGCQ01206316) - MR_ValidateMapInfo issue on bigendian platform (In some case Detect Ghost VDs)(SCGCQ01213952) - Fixed code review defects(SCGCQ01254323) - Removed code inside macros VD_EXT_DEBUG, SPAN_DEBUG and enahnce prints in OCR path(SCGCQ01270056) - FW fault happens as driver wrongly fill numSGE=0.(SCGCQ01274103) - Code optimization and enhanced prints for debugging(SCGCQ01224881) - Remove unsupported PCI Device IDs from the driver code(SCGCQ01234256) - Resolved conflict of PCI device ID-0x0015(SCGCQ01254317) - MR7.2: In megasas_issue_tm() SMID needs to be used for Task abort case only(SCGCQ01315252) - Save interfaceType for each sysPDs inside SCSI device's private data field which will persists until sysPD is removed/deleted.(SCGCQ01216464) - Code Optimization and enhanced prints(SCGCQ01223300) - MR 7.1: Linux OS crash when powering off enclosure during I/O(SCGCQ01229442) - Return pending IOs with status DID_REQUEUE instead of DID_RESET to SCSU layer before doing OCR(SCGCQ01231846) - MR7.2: Port changes from upstream to make in-house MR 7.2 code to be consistent with upstream code(SCGCQ01282321) - Add print for partially copied SCSI IO and fix few endianness issues(SCGCQ01224305) - Linux Driver 07.700.23.00/Getting megaraid_sas prints during startup of OS(SCGCQ01255074) - aen class range check to avoid kernel panic(SCGCQ01256126) - Corrected bitmap macros inside struct RAID_CONTEXT35(SCGCQ01269453) - Set cmd_status inside DCMD/IO/header frame to MFI_STAT_OK to wake up all pended IOCTLs.(SCGCQ01298582) - Fix few dev found issues(SCGCQ01226224) - On OEL SPARC (Big Endian), Linux MR 7.1 driver loading fails to initialize Ventura which has RDPQ support enabled(SCGCQ01229897) - Fixed few code collab defects/comments(SCGCQ01202237) - Remove throttle IOs prints in IO path and add sysfs parameter to reflect number of R1 FP writes(SCGCQ01204099) - Ventura MR-7.0.1 RHEL 7.2 driver: ERR messages when installing driver 7.700.20.00(SCGCQ01222990) - Use do_div() kernel API to do modulo operation of 64 bit dividend and 32bit divisor .(SCGCQ01243263) - megasas_complete_cmd_dpc_fusion() will be called with 1 sec delay inside function megasas_wait_for_outstanding_fusion(SCGCQ01256116) - Allocated MFI frame size and the size of MPT chain frame(Where MFI frame resides for MFI MPT passthru commands) should match(SCGCQ01342650) EnhancementRequests (17) - Big endian architecture is now support for Ventura generation of MR HBA.(SCGCQ01256016) - Fixed the problem of sync_irq not being called when MSI-x are disabled.(SCGCQ01206307) - Port changes from MR7.0 and MR6.13 critical fixes to MR7.1(SCGCQ01167939) - In megasas_build_ldio_fusion, code to set controller CPU affinity can be optimized(SCGCQ01216486) - Set device queue depth same as controller's can_queue for SCSI MQ mode(SCGCQ01271569) - Add SLES 11 32-bit build kit support to Ventura MR.(SCGCQ01214721) - Ported fixes from MR 6.13 to MR 7.1(SCGCQ01222522) - Added support for RHEL7.3(SCGCQ01224300) - Support SPARC/PPC/ARM (Big/Little Endian). Fix Endianess issue in MR Ventura driver.(SCGCQ01183275) - Added DCMD interface to read target properties for SCSI device(VDs and JBODs both)(SCGCQ01220142) - Added KMOD RPM support for OEL7.3 UEK.(SCGCQ01227476) - R1 Write IOPs improvement(SCGCQ01213232) - Extra code for bug in A0 ventura is removed. Optimized Descriptor write as Ventura required 32 bit in major IO Path operation.(SCGCQ01215347) - Remove Crusader device support from driver(SCGCQ01259175) - Don't re-issue Reset on the way back OCR(SCGCQ01215089) - Rework start_vm_build script used for VBAS build and new build infrastructure for DKMS RPMs(SCGCQ01261800) - Version 7.700.26.00- Moderate Impact/Low Probability of Occurrence --------------------- Enhancement: - Added support for ThinkSystem HBA and RAID. Version 6.812.08.00 - Moderate Impact/Low Probability of Occurrence --------------------- Fixes: - Modified not to send outstanding IOs back to SML with DID_RESET host_byte but return IOs back with host_byte DID_REQUEUE before doing OCR. (SCGCQ01278656 Port Of Defect SCGCQ01231846) Enhancement - Added support for SLES 12.2 Version 6.812.07.00 - Moderate Impact/Low Probability of Occurrence --------------------- Fixes - Changed timeout value for DCMDs get_bios_data and get_pd_info 180 seconds to keep it aligned with other DCMDs' timeout value. (SCGCQ00884247) - Do not allow MFI frame to be freed from DCMD fire context when already an OCR is in progress. (SCGCQ00879190) - Fixed an issue where driver always worked in non RDPQ mode even the running firmware did not support RDPQ. (SCGCQ00872542) - Moved SCSI layer interaction code out of reset_mutex in AEN thread to prevent deadlock around reset_mutex. (SCGCQ00868731) - Convert supported JBOD count value returned by firmware in CPU format and then use the same value for further validation (SCGCQ00837088) - Fixed an issue where unevenSpan configuration of R1 would not have proper load balancing for FP READ. SCGCQ00646224 - Added timeout value for wait_event. (SCGCQ00249742) - Enabled hostlockless flag of SCSI host for RHEL6 and clones for async IO submission from SCSI mid layer. (SCGCQ00884242) - Fixed an issue where double freeing of MFI frame in case of MFI IO timeout in polled mode could occur. (SCGCQ00837932) - Added synchronization between OCR thread and AEN thread, so that there should not be any PCI write from AEN thread during OCR (SCGCQ00836410) - Added IO timeout value for SCSI management commands for JBOD. (SCGCQ00750452) - Fixed a JBOD performance issue due to incorrect MSI-x index set in request desc. (SCGCQ00619694) - Changed state machine of firmware crash dump collection to prevent file system on VD being set to Read-only mode after ECC error injection. (SCGCQ00608705) - Fixed an issue where incorrect messages such as LSI SAS2.0 were printed for MR driver. (SCGCQ00298201_ - Fixed an issue where the driver sent an incorrect region type "REGION_LOCK_EXCLUSIVE" set to FW for RAID level >=5 - Changed error handling for DCMD failure cases to allow graceful exit for not fatal errors. (SCGCQ00868661) - Free task management frame after dumping the task management reply frame data to ensure that TM reply frame will have valid data returned by firmware. (SCGCQ00860038) - Release reset_mutex inside OCR function, if adapter is already killed to prevent a kernel panic. (SCGCQ00857740) - Increased timeout to 180 seconds for flush cache and shutdown controller DCMDs to prevent kernel panic when DCMDs fired during driver's shutdown. (SCGCQ00841491) - Fixed an issue where traversed LDs at multiple places up to maximum 256 were limited to 64. (SCGCQ00652795) - Fixed an issue where the driver crashed when msix_disable=1 was passed to the boot time parameter. (SCGCQ00383508) - Fixed an issue where kernel panic seen while deleting VD and background IOs running. (SCGCQ00803468) - Fixed an issue where the driver was not sending DCMD- MR_DCMD_CTRL_SET_CRASH_DUMP_PARAMS after OCR. (SCGCQ00601138) - Fixed an issue where the kernel panicked inside PCI subsystem because of IRQs not freed before disabling MSI-X interrupts (SCGCQ00827403) - Disabled SED drive JBOD support. (SCGCQ00751296) - Fixed multiple OCRs triggering hits Exception Core issue (SCGCQ00707592) - Fixed an issue where the firmware faulted due to invalid regionlock Flags set by Driver. (SCGCQ00796461) - Fixed an issue where subsequent reads of state value from hardware resulted different values and could lead to a timeout in and a non working adapter. (SCGCQ00709216) - Fixed an issue where Offline VD caused boot hangs in SLES 11 (SCGCQ00284564) - Disabled SPAN_DEBUG and set get_arm_from_strip to print if firmware supports UnevenSpan. (SCGCQ00365846) - Added check to validate ldcount exposed in firmware RAID map for legacy firmware. If ldcount is more than 64, fail RAID map validation. (SCGCQ00820349) - Fixed an issue where the Linux kernel crashed when AEN and LD Sync commands were issued frequently. (SCGCQ00712031) - Fixed an issue where duplicate disk(s) were seen on controller after loading Linux driver during OS installation, (SCGCQ00568992) - Fixed an issue where kernel panic could occur at driver load time on 3.0 kernels (i.e. SLES11 SP2, SLES11SP3). (SCGCQ00561505) - Changed driver to return SCSI command back to mid layer if the controller has any critical hardware errors. SCGCQ00362023 - Fixed an issue where the driver did not do Load balance for R1 READ due to wrong stats counters. (SCGCQ00677516 Port of Defect - SCGCQ00674872) - Fixed potential duplicate IOCinit frames being fired by VMware5 VF driver during OCR. (SCGCQ00571967 PORT OF SCGCQ00571679) - Fixed OS crash issue on SCSI IO timeout (SCGCQ00631210 PORT OF SCGCQ00625137) -Fixed an issue where the kernel panicked due to MFI/MPT pass-through command timeout and later finished from Interrupt context. (SCGCQ00307867 PORT OF - SCGCQ00302080) - Fixed an issue where megasas_poll_wait_aen was cleared before poll syscall returns causing to lose events (SCGCQ00575192 PORT OF SCGCQ00574787) -Fixed an issue where data corruption observed on JBODs while running IOs with 32k block size. (SCGCQ00530992 PORT OF SCGCQ00523780) - Fixed MPC kernel panic during chassis power cycle if AEN completes and detach is called before event workqueue runs. (SCGCQ00647390 PORT OF SCGCQ00645836) - Fixed an issue where kernel crashed in some cases, where megaraid_sas driver is loaded but controller is not present. (SCGCQ00282968 PORT OF SCGCQ00282067) Enhancements: - Set queue depth for syspD based on interface type (SCGCQ00879700) - Updated module Meta data (module description and module author) with Avago replacing LSI. (SCGCQ00801961) - Set OS provided timeout value for sysPD non read-write IOs (SCGCQ00764795) - Performance tuning for SMP affinity is implemented for distros's which support irq_set_affinity_hint API. (SCGCQ00623697) - Optimized OCR path to enable interrupt and make HBA OPERATIONAL after driver has fired LD_MAP_GET_INFO DCMD. (SCGCQ00768402) - Added module parameter to turn on/off SMP affinity code. (SCGCQ00666706) - Driver will do load balance for N Drive Raid 1 volumes. (SCGCQ00634064) -Functionality in driver is added to differentiate between iMR and MR at firmware initialization time. (SCGCQ00361244) - Uneven Span support added in Driver. (SCGCQ00319104) - Driver code is updated such way that it can work for any block size drive, if the rest of the system has proper support for the same. (SCGCQ00259244) - Implemented online controller reset if controller is not responding at driver load time. (SCGCQ00820389) - Added SCSI residual bytes support to the megaraid_sas Linux driver (SCGCQ00347089) - Use sequence number for JBOD FastPath I/Os to eliminate command block after drive replacement (SCGCQ00806534) - Big endian architecture support added for MR Linux driver (SCGCQ00526911) - Driver support is added for 3108 C0 chip combine reply queue ON (SCGCQ00354586) - Added support 240 VD feature (SCGCQ00622703) - Added Firmware crash dump collection support (SCGCQ00550369) - Added support for large I/O 1MB transfer size (SCGCQ00816313) - Changed the max sg table size to 64. Old setting was 70 (SCGCQ00653992) - Added driver support for task management for Jbod or VD (tmCapable) (SCGCQ00854635) - Added support for SED JBOD in MR Linux driver (SCGCQ00711555) - Changed code to complete IOCtls posted just before a kill adapter so user space applications do not hang. (SCGCQ00759916) Version 6.810.09.00 - Moderate Impact/Low Probability of Occurrence --------------------- Fixes: - Fixed an issue where deadlock may occur when the Automatic Event Notification thread runs in parallel with error handler thread (SCGCQ00911332, Port of SCGCQ00868731) - Fixed an issue where driver will operated in RDPQ mode regardless of whether firmware has advertised support or not (SCGCQ00872542) - Fixed an issue where system may reset with error "BUG: unable to handle kernel NULL pointer dereference at 00000000000000d0" preceded by error "megasas: target reset FAILED!!" (SCGCQ00875223) - Fixed an issue where driver MFI frames could be freed twice (SCGCQ00879190) - Fixed an issue where some out-of-band commands had different timeouts than others (SCGCQ00884247) - Fixed an issue where performance was lower on async IO submissions from the SCSI mid layer (SCGCQ00884242) - Fixed an issue where a kernel panic may occur if the system is reset or fail to reboot (SCGCQ00859634, Port of SCGCQ00857740) - Fixed an issue where Task Management frames were not being dumped after the Tast Management Reply frame data (SCGCQ00860038) - Fixed an issue where a fatal error may occur when an out-of-band command times out during an Online Controller Reset (SCGCQ00882011, Port of SCGCQ00868661) - Fixed an issue where kernel may hang when many commands are timing out or many Automatic Event Notifications are being processed (SCGCQ00857245) - Fixed an issue where megaraid_sas module was not being included inside initrd/initramfs (SCGCQ00880965) - Fixed an issue where kernel may panic if driver does not setup IRQs for non-MSI-x interrupt mode (SCGCQ00870263, Port of SCGCQ00867873) - Fixed an issue where driver return code is based on command completion rather than command return code (SCGCQ00856103, Port of SCGCQ00856089) - Fixed an issue where Tape drives may not be detected by the Operating System (SCGCQ00914385, Port of SCGCQ00911702) - Fixed an issue where max_sectors per IO request may be set to more than firmware can handle (SCGCQ00917992, Port of SCGCQ00917399) - Fixed an issue where an IERR may occurr on heavy IO with Failover (SCGCQ00864111, Port of SCGCQ00736612) Enhancements: - Enhanced queue depths in driver for physical disks based on interface type (SCGCQ00879700) - Improved naming of internal functions (SCGCQ00866064) - Updated module parameter "rdpq_enable" default to "1" (enable RQPQ mode) (SCGCQ00871565) - Enhanced reply queue to support queue depth greater than 1K (SCGCQ00853521) - Added feature for driver to support Task Management for JBOD and Virtual Drives (SCGCQ00854635) - Added module parameter to disable 1M IO support and set default to enable 1M IO support (SCGCQ00911362) - Enhanced tasklet initialization so it would occur before setting up IRQs (SCGCQ00914393, Port of SCGCQ00911709) - Simplified HB handling for SR-IOV (SCGCQ00864113, Port of SCGCQ00700580) - Enhanced driver to update Online Controller Reset capability when it changes (SCGCQ00914389, Port of SCGCQ00908352) - Added feature to print Critical, Fatal and Dead firmware events into system logs (SCGCQ00868723, SCGCQ00882010, Port of SCGCQ00866176) - Enhanced HB handling to align with behavior on other Operating Systems (SCGCQ00864117, Port of SCGCQ00707323) - Removed excess dead code (SCGCQ00850012) Version 6.808.16.00 - Moderate Impact/Low Probability of Occurrence --------------------- Fixes: - Fixed an issue where a deadlock may occur around reset_mutex when Automatic Event Notification threads run in parallel with error handlers - (SCGCQ00911332, Port of SCGCQ00868731) - Fixed an issue where scanning of Tape drives does not occur depending on whether the drive state is set to systemPD or not - (SCGCQ00914385, Port of SCGCQ00911702) - Fixed an issue where max_sectors may be set larger than what firmware can support - (SCGCQ00917992, Port of SCGCQ00917399) - Fixed an issue where kernel may panic due to driver not setting up IRQs for non MSI-x interrupt mode - (SCGCQ00870263, Port of SCGCQ00867873) - Fixed an issue where driver may halt firmware due to improper error handling for DCMD failure cases - (SCGCQ00882011, Port of SCGCQ00868661) - Fixed an issue where driver may hang kernel due to deadlock - (SCGCQ00857245) - Fixed an issue where system may crash due to timeout for flushing cache and shutting down controller DCMDs was not long enough - (SCGCQ00841491) - Fixed an issue where deadlock may occur between Online Controller Reset and Automatic Event Notification processing function - (SCGCQ00846933) - Fixed an issue where PCI writes from Automatic Event Notification thread were occurring during Online Controller Reset - (SCGCQ00836410) - Fixed an issue where MFI frames linked list may corrupt due to double-freeing of frame in the case of an MFI IO timeout - (SCGCQ00837932) - Fixed an issue where kernel may panic inside PCI subsystem due to IRQs not freed before disabling MSI-X interrupts - (SCGCQ00827403) - Fixed an issue where ldcount was not validated for non-240VD firmware - (SCGCQ00820349) - Fixed an issue where a command block would occur for JBODs with FastPath IOs after a drive is replaced - (SCGCQ00806534) - Fixed an issue where 1MB IO support was not supported controller-wide - (SCGCQ00816313) Enhancements: - Set DMA alignment to 8 bytes for PI-enabled VDs - (SCGCQ00928796, Port of SCGCQ00928176) - Added a parameter to support disabling 1MB IO support - (SCGCQ00911362) - Added support for printing Critical, Fatal and Dead Firmware events into system logs - (SCGCQ00882010, Port of SCGCQ00866176) - Added support for driver to perform an Online Controller Reset at driver load time if the controller is not responding - (SCGCQ00820389) Version 6.808.14.00 - Moderate Impact/Low Probability of Occurrence --------------------- Fixes - Fixed an issue where controller may reset or "MonTask: line 1276" error will occur with JBOD present (SCGCQ00837088) - Fixed a performance issue on RAID1 with 256k IO size (SCGCQ00674872) - Fixed a performance issue on RAID1 reads with FastPath enabled (SCGCQ00646224) - Fixed an issue where an Online Controller Reset may take an unusually lon time (SCGCQ00420374) - Fixed an issue where a controller firmware crash may not be recognized by driver (SCGCQ00249742) - Fixed an issue where an MFI frame may be freed twice on MFI command timeout (SCGCQ00837932) - Fixed an issue where the firmware may fault in an Automatic Event Notification fires during an Online Controller Reset before the chip is in READY state (SCGCQ00836410) - Fixed an issue where there was no IO timeout value for SCSI management commands for Secure JBOD (SCGCQ00750452) - Fixed a performance issue on SSDs in JBOD mode (SCGCQ00619694) - Fixed an issue where file system on a VD can go to read-only on ECC error detection (SCGCQ00608705) - Fixed an issue where disks may not be found during installation after loading the driver (SCGCQ00299643) - Fixed an issue where a kernel panic may occur when cable pulled during system reboot (SCGCQ00841491) - Fixed an issue where 240VD support was not fully implemented (SCGCQ00652795) - Fixed an issue where the driver may crash if msix_disable=1 is passed to kernel as boot parameter (SCGCQ00383508) - Fixed an issue where IO errors may occur when connected to a Tape drive (SCGCQ00399947) - Fixed an issue where kernel may hang due to megaraid_sas driver deadlock (SCGCQ00857245) - Fixed an issue where kernel may panic when deleting VD and background IO is occurring (SCGCQ00803468) - Fixed an issue where crash dump may be disabled after an Online Controller Reset (SCGCQ00601138) - Fixed an issue in 32bit OSs where driver may not load on boot (SCGCQ00362423) - Fixed an issue where deadlock may occur (SCGCQ00846933) - Fixed an issue where a kernel panic may occur because IRQs are not freed before disabling MSI-X interrupts (SCGCQ00827403) - Fixed an issue where multiple Online Controller Resets can trigger a Core Exception (SCGCQ00707592) - Fixed an issue where crash dump may not be performed properly (SCGCQ00593374) - Fixed an issue where firmware may fault with CacheCade (SCGCQ00796461) - Fixed an issue where adapter may hang (SCGCQ00709216) - Fixed an issue where an offline VD may cause boot hangs (SCGCQ00284564) - Fixed an issue where kernel may panic (SCGCQ00820349) - Fixed an issue where kernel may crash in megaraid_sas driver with CacheCade if there are many Automatic Event Notifications and LD sync operations occurring (SCGCQ00712031) - Fixed an issue where system may hang with CacheCade (SCGCQ00687881) - Fixed an issue where the same disk may show multiple times in OS (SCGCQ00568992) - Fixed an issue where kernel may panic on Linux kernels version 3.0 or greater (SCGCQ00561505) - Fixed an issue where invalid IO statistics may be provided if driver supports more than just 512b sector drives (SCGCQ00282615) - Fixed an issue where driver fails to reboot system due to outstanding IOs in SCSI mid-layer when controller is in error state (SCGCQ00362023) Enhancements - Added ability for JBOD IOs going via firmware path to use timeout value provided by OS (SCGCQ00764795) - Added a retry of IO commands as LDIO if raid map sync is failed with MFI_STAT_CONFIG_SEQ_MISMATCH (SCGCQ00712510) - Added support for 4k sector drives if the system supports it (SCGCQ00259244) - Added support for driver to perform an Online Controller Reset if the controller is not responding (SCGCQ00820389) - Fixed an issue where system may hang on S3 resume (SCGCQ00758933) - Added a feature to prevent command block with FastPath after JBOD drive replacement (SCGCQ00806534) - Enhanced 1MB IO support (SCGCQ00816313) - Added support for "megaraid_sas.disable_ext_io=1" boot parameter to disable 1M IO support (SCGCQ00911362) - Added support for Secure JBOD (SCGCQ00711555, SCGCQ00753765) - Fixed an issue where user space applications may hang if IOCtl is sent prior a kill adapter issued (SCGCQ00759916) - Fixed an issue where OS may crash on a SCSI IO timeout (SCGCQ00631210) - Fixed an issue where system may fail to reboot or will kernel panic on init 6 if controller has faulted (SCGCQ00859634) - Fixed an issue where firmware may fault (SCGCQ00702536) - Fixed an issue where controller may crash during system power cycle (SCGCQ00647390) - Fixed an issue where kernel may crash when megaraid_sas driver is loaded but no MegaRAID controllers are present (SCGCQ00282968) Version 6.806.08.00 - Moderate Impact/Low Probability of Occurrence ------------------- Fixes: - Incorporated MegaRAID 6.6 x86/x86_64 Linux driver stream - Fixed an issue where performance may drop in sequential read 256kb IO (SCGCQ00677516) - Fixed an issue which may lead to firmware crash and "MonTask: line 1257 in file ../../raid/2108vI2o.c" error in firmware log (SCGCQ00702536) Features/enhancements: - Added a retry of IO commands as LDIO if raid map sync is failed with MFI_STAT_CONFIG_SEQ_MISMATCH (SCGCQ00651680) - Added support for 1MB IO if the firmware supports it as well (SCGCQ00671670) - Added ability to take a VD offline / bring a VD online, similar to the equivalent actions for PDs (SCGCQ00521610) - Added support for Self-Encrypting Drives in JBOD mode (SCGCQ00399739) Version 6.704.15.00 - Initial release -------------------
Lenovo Data Center Group Linux OS Support Home Page |
| linux.lenovo.com |
© 2018-2019 Lenovo. All rights reserved |