CO ID:	LSID100101474
Headline:	CR_Ref# LSID100101126: Add ICH7 PnP ID to SWR driver._SWR_Driver_R5_Univ
Description:	CR_Ref# LSID100101126: Add ICH7 PnP ID to SWR driver.
State:	Development_Completed
Associated Task:	LSID100101470

CO ID:	LSID100101226
Headline:	CR_Ref# LSID100101023: Ensure current SSID's are in Columbus release plan_SWR_Driver_R5_Univ
Description:	CR_Ref# LSID100101023: Ensure current SSID's are in Columbus release plan
State:	Development_Completed
Associated Task:	LSID100101477

DFCT ID:	LSID100095927
Customer DFCT No:	HSA0183
Headline:	SWR Linux Driver makes OS Hang-up when one no-response drive in RAID1 in OS running.
Description:	Please modify RAID driver to make the no-response drive fail by command timeout when the above condition is occurred.
Version of Bug Reported:	10.19.0411.2008
Version of Bug Fixed:	12.07.1021.2008
Steps to Reproduce:	Steps to duplication: 1) Inject 10minutes no respond error to the one of RAID1 drive. 2) Boot up the OS. 2) It became OS Hang-up when during read/ write.
Resolution:	Fixed
Resolution Description:	Root Cause          : The timeout for retry commands is exeeding the OS timeout. Fix               : Decrease the retry timeout so that HAL can fail the command to OS
Customer Defect Track No:	HSA0183
Customer List:	OEM -- OEM
Fix Impact:	Low
Suggested Testing:	Verify               : Follow the steps in the defect to reproduce and with this fix the issue shouldn't occur
Child Tasks:	LSID100101435

Task ID:	LSID100100805
Headline:	Fixing compiler error
Description:	Fixing compiler error
State:	Open
Change Set Files:	0
References:

Task ID:	LSID100101115
Headline:	pciid's automation
Description:	pciid's automation
State:	Open
Change Set Files:	0
References:

Task ID:	LSID100100401
Headline:	Task to update Linux package
Description:	Task to update Linux package
State:	Open
Change Set Files:	0
References:

Task ID:	LSID100101426
Headline:	reverting eval pci-id changes
Description:	reverting evals pci_ids' change
State:	Open
Change Set Files:	0
References:

Task ID:	LSID100101477
Headline:	adding ibex peek
Description:	adding ibex peek
State:	Completed
Change Set Files:	0
References:	LSID100101226(CO)

Task ID:	LSID100101470
Headline:	LSID100101126: Add ICH7 PnP ID to SWR driver.
Description:	LSID100101126: Add ICH7 PnP ID to SWR driver.
State:	Completed
Change Set Files:	0
References:	LSID100101474(CO)

Task ID:	LSID100101435
Headline:	LSID100095927: non-responsive drive
Description:	LSID100095927: non-responsive drive
State:	Completed
Change Set Files:	0
References:	LSID100095927(DFCT)

Task ID:	LSID100101319
Headline:	pciid's eval version
Description:	pciid's eval version
State:	Open
Change Set Files:	0
References:

Task ID:	LSID100101114
Headline:	pci id's addition automation
Description:	pci id's addition automation
State:	Open
Change Set Files:	0
References:

Task ID:	LSID100101307
Headline:	pciid's automation
Description:	pciid's automation
State:	Open
Change Set Files:	0
References:

Task ID:	LSID100101273
Headline:	adding folders
Description:	adding folders
State:	Open
Change Set Files:	0
References:

Task ID:	LSID100101306
Headline:	Fixing incosistencies btw OEM and lsi packages
Description:	Fixing incosistencies btw OEM and lsi packages
State:	Open
Change Set Files:	0
References:

Heading:

Known Restrictions

Contents:

• Type "brokenmodules=ahci" line at kernel parameter line during SLES 9 & 10 installations • RHEL 3.0 64-bit versions are not supported on AMD systems. Only Intel systems are supported. • RAID 5 is not supported on VMWARE ESX Servers. • 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. • RHEL5 installation does not automatically prefer the driver in DUD to native driver. Run replace_ahci script inside the DUD before rebooting during the last stage of installation. Refer to readme.txt under in the DUD for more details • 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.