|
|
Engineering Release Notice |
| Release Date: | 03/30/2012 |
| OEM: | ALL_OEM |
| SWR_Driver_R5_Univ | 15.00.0329.2012 |
| Component: | SWR_Driver_R5_Univ |
| Stream: | SWR_DRIVER_R5_UNIV_MACON_Dev_Main |
| Version: | 15.00.0329.2012 |
| Baseline From: | SWR_DRIVER_R5_UNIV_MACON_3_16_2012_LenovoIntel_pnPID.8788@\DAS_Projects |
| Baseline To: | SWR_DRIVER_R5_UNIV_MACON_3_29_2012_PushPullPanic_Linux.6842@\DAS_Projects |
| LSIP200234523 | (TASK) | 234523 LSIP200229473: Lenovo - Macon SGPIO LED |
| LSIP200234684 | (TASK) | 234684 FTS Kernel panic during Drive pull-push |
| LSIP200234692 | (TASK) | 234692 Adding missed Intel PnPID |
| LSIP200229473 | (DFCT) | Macon SGPIO LED |
| LSIP200231024 | (DFCT) | SWR_Macon_Pahses1.1_Patch1 : Kernal pacnic is observed in RHEL 5.8_32 Bit OS on drive push/pull. |
| LSIP200230794 | (DFCT) | (CSCty64551) C22-SWRAID: RHEL5.7 Install hangs during megasr driver load |
| DFCT ID: | LSIP200229473 |
| Headline: | Macon SGPIO LED |
| Description: | Lenovo found drive LED didn't work with some status, please see attachment for the details, and advise the possible solution. |
| Version of Bug Reported: | SCU.11.01191623R |
| Steps to Reproduce: | check LED status with different disk status. |
| Resolution: | Locate LED will blink during a REBUILD operation. |
| Fix Impact: | Medium |
| External Behavior Change: | Yes |
| Suggested Testing: | Do REBUILD & check locate LED behaviour |
| Child Tasks: | LSIP200234523 |
| DFCT ID: | LSIP200231024 |
| Headline: | SWR_Macon_Pahses1.1_Patch1 : Kernal pacnic is observed in RHEL 5.8_32 Bit OS on drive push/pull. |
| Description: | On push/pull drive from a backplane connected to SCU controller results in kernal panic.
Server will hang and kernal panic observed Details. OS Details OS name: RHEL 5.8_GA_32Bit Linux OS Version: 2.6.18-308.el5PAE OS Architecture: i686 Driver Name: LSI MegaSR RAID5 Application Version: MegaRAID Storage Manager - v11.08.03-03 HARDWARE--- Controller: LSI Embedded MegaRAID (Bus 6,Dev 0) Drive(s): 4 Driver Version: 15.00.0316.2012 Virtual Drive(s): 0 Drives-- PRODUCT ID VENDOR ID DISK TYPE CAPACITY MBE2147RC FUJITSU SAS 135.973 GB ST9146852SS SEAGATE SAS 135.973 GB MBD2147RC FUJITSU SAS 135.973 GB MBD2147RC FUJITSU SAS 135.973 GB Serever Details FTS server RX_300_S7 BIOS : R1.2.0 SCU : SCU.11.03.0201000P Revision : C1 |
| Version of Bug Reported: | SCU.11.03.0201000P |
| Steps to Reproduce: | Steps
1. Install RHEL5.8_32 Bit OS in SATA Controller (IDE Mode) 2. Connect few SAS PD to backplane 3. Supply RPM file for driver (version 15.00.0316.2012) 4. Install MSM and launch it 5. Make sure all the drives are detected. 6. Do a push/Pull of drive from any one slot. Please see the attched logs |
| Resolution: | Replaced msleep with udelay inside spinlock |
| Fix Impact: | Medium |
| External Behavior Change: | No |
| Suggested Testing: | Same as repro. |
| Child Tasks: | LSIP200234684 |
| DFCT ID: | LSIP200230794 |
| Customer DFCT No: | CSCty64551 |
| Headline: | (CSCty64551) C22-SWRAID: RHEL5.7 Install hangs during megasr driver load |
| Description: | When Installing RHEL5.7 and when the megasr driver is loading, the system shows "Disabling IRQ #177" and hangs in this screen for 10 minutes and fails to load the Driver. This prevent us from Installing RHEL5.7 OS and showstopper for testing this OS.
|
| Version of Bug Reported: | 15.00.0120.2012-1 |
| Steps to Reproduce: | SWRAID config with Patsburg-A with SKUROM#5 and LSIRAID5 TSOC.
Alameda Server with LSI SWRAID BIOS version: "LSI MegaRAID Software RAID BIOS Version SCU.11.01191623R" LSI Driver: megasr-15.00.0120.2012-1-rhel50-U7-64.img Install RHEL5.7 |
| Resolution: | Removed Enabling of Interrupts in Drive Discovery Path |
| Customer Defect Track No: | CSCty64551 |
| Fix Impact: | Medium |
| External Behavior Change: | No |
| Suggested Testing: | Same as repro. |
| Child Tasks: | LSIP200234684 |
| Task ID: | LSIP200234523 |
| Headline: | 234523 LSIP200229473: Lenovo - Macon SGPIO LED |
| Description: | LSIP200229473: Lenovo - Macon SGPIO LED |
| State: | Delivered |
| Change Set Files: | |
| References: | LSIP200229473(DFCT) |
| Task ID: | LSIP200234684 |
| Headline: | 234684 FTS Kernel panic during Drive pull-push |
| Description: | FTS Kernel panic during Drive pull-push |
| State: | Delivered |
| Change Set Files: | |
| References: | LSIP200230794(DFCT) LSIP200231024(DFCT) |
| Task ID: | LSIP200234692 |
| Headline: | 234692 Adding missed Intel PnPID |
| Description: | Adding missed Intel PnPID
8086 1D04 357F 8086 |
| State: | Delivered |
| Change Set Files: | |
| References: |
| Heading: | Known Restrictions |
| Contents: |
• In SWR5 driver, RAID 5 feature is enabled only if iButton is present in the system. BIOS communicates the presence/absence of iButton using configuration data on disk (DDF) and through device registers from BIOS version 06.10111923. So if IButton is present then any driver version later than 10.02.1001.2007 with BIOS version later than 06.10111923 should be able to create a R5 logical drive using an operating system application. The following limitation is applicable for any driver (version less than 10.02.1001.2007) and BIOS (version less than 06.10111923) combination:- If driver does not read a valid DDF, it will disable R5 creation. Driver may not see valid DDF if (A) user does not configure using BIOS Ctrl+M; or (B) if no drives were present at the boot time and all the drives were hot-inserted after OS is booted. In both cases, user must create initial configuration using BIOS Ctrl+M utility. • A RAID 5 logical drive withstands single drive failure by reconstructing missing data from the data and parity from the remaining drives. The assumption underlying this ability is that the data in the remaining drives is consistent. This assumption becomes invalid if there is a power loss during write operation(s). If there is a loss of power during a write operation, data inconsistencies may occur because data and parity writes may have completed only partially. After subsequent reboot the logical drive has inconsistent data on that particular stripe. If a drive were to fail at this point, missing data (for the inconsistent stripe alone) cannot be reconstructed from remaining drives. To correct inconsistency, drivers starts back ground initialization (BGI) at reboot. While BGI is in progress, the inconsistent stripe(s) are vulnerable to drive failure. One way to avoid this window of vulnerability is to run check consistency on the logical drive using BIOS utility. Another way is to prevent an unplanned shutdown (e.g. using UPS). • The LITE-ON SH S752K model CD/DVD ROM device does not respond to 0x55 & 0x51 MMC commands properly. The device hangs when these commands are issued multiple times. The driver resets the device when it hangs; but reset adversely affects DVD burning. This behavior can be consistently observed using K3B DVD burning software. K3B aborts DVD writes when 0x55 is failed and device is reset. • RAID 5, by its very nature, cannot tolerate double failures. The double failure can be a combination of a single drive failure and either; more drive(s) failure or an unplanned power failure, in the RAID system. Unplanned power failure can be including but not limited to, loss of power source or an unusual system shutdown. Unplanned power failures while there are medium errors on the drives is also considered as a double failure condition. • Multiple drive failure would result in a data loss condition. A single drive failure combined with any additional unplanned failure can cause loss of data integrity. To avoid loss of data integrity for the power failure case, it is highly recommended to provide an uninterrupted power supply to the server to protect the RAID 5 subsystem during the event of a degraded or rebuilding state. Medium errors on the disks, combined with an unplanned power failure can also cause loss of data integrity, but this occurrence would be very unlikely. • Hotplug limitation in runtime If the user pulls out or plugs in a drive when the LSI OpROM has completed its execution, and before the OS driver is loaded (like DOS shell, or AHCI‚s Ctrl-M screen etc), the OpROM‚s runtime code displays a message and force reboot the system to avoid configuration losses or data corruption. • Maximum two storage controllers supported If the used try to enable SCU and AHCI in RAID mode and insert any external storage controller (for example MegaRAID Hardware RAID), the last controller in the boot sequence might not be able to POST. • Windows installation limitation in RAID Mode: If Windows installation is done on a drive connected through AHCI controller, make sure SCU controller is disabled in BIOS. After completion of installation, SCU can be enabled in BIOS. If both controllers are enabled in RAID mode, installation may fail. |