CO ID:	LSID100094885
Headline:	CR_Ref# LSID100094068: CC should never start automatically by default (OEM Specific)
Description:	CR_Ref# LSID100094068: CC should never start automatically by default
State:	Development_Completed
Associated Task:	LSID100082067

CO ID:	LSID100093758
Headline:	CR_Ref# LSID100079626: Add SSID for new SAS platform_FW_SAS_LSI
Description:	CR_Ref# LSID100079626: Add SSID for new SAS platform
State:	Development_Completed
Associated Task:	LSID100094437

CO ID:	LSID100094931
Headline:	CR_Ref# LSID100094418: Customize LED blink pattern for Hot Spare_FW_SAS_LSI
Description:	CR_Ref# LSID100094418: Customize LED blink pattern for Hot Spare
State:	Development_Completed
Associated Task:	LSID100082104

DFCT ID:	LSID100092025
Customer DFCT No:	1078_PR5001
Headline:	Panic occurs on HWR Linux driver(megaraid_sas) while the kdump is running with I/O to the drive.
Description:	[Supplementation] 1. Panic does not occur when there is no I/O. 2. Panic does not occur when Write Policy of a VD is Write Through. 3. With SATA HDD, the duplication ratio is 100%. (With SAS HDD, the duplicationl ratio is low.) 4. See the Notes section for the console screen when the panic occured.
Version of Bug Reported:	ver 00.00.03.18
Steps to Reproduce:	[Procedure] 1. Set kdump and sysrq. 2. System rebooting. 3. Endlessly do I/O. # dd if=/dev/urandom of=data bs=1M count=2048 # while [ -l ] ; do /bin/cp data data2 ; done 4. Do system panic. (On another screen) # echo c > /proc/sysrq-trigger 5. Panic is generated while starting the kdump kernel, and kdump fails.
Resolution:	Fixed
Resolution Description:	FW now waits for host commands to complete before transitioning to READY.
Customer Defect Track No:	1078_PR5001
Customer List:	OEM -- OEM
Fix Impact:	Medium
Suggested Testing:	Same as in Repro steps.
Child Tasks:	LSID100094953

DFCT ID:	LSID100094780
Headline:	Block IR to MR migration
Description:	FW should not allow migration from IR to MR. I have attached the slides for this defect.
Version of Bug Reported:	420
Steps to Reproduce:	On an adapter that supports both IR and MR Create an IR volume with CFGgen, then migrate it to MR. If the coerrcion size is not large enugh then the Metadata will over write ld data.
Resolution:	Fixed Indirectly
Resolution Description:	MR imports the IR configuration with the DDF size of 64MB, then MR resize it to 512MB lead to a data loss.
Fix Impact:	Low
Suggested Testing:	1) Create RAID 1 using cfggen.exe (Old Version 2.00.23) in IR and migrate MR. - should fail to import 2) Create RAID 1 using cfggen.exe (New Version 2.00.24) in IR and migrate MR. - should import Finally, once you have this test config working, with 73Gig drives, please try with 146 Gig drives, and both FW should work above both cases.
Child Tasks:	LSID100094914

Task ID:	LSID100094437
Headline:	same as LSID100093956
Description:	for adding new SSID/VID
State:	Completed
Change Set Files:	0
References:	LSID100093758(CO)

Task ID:	LSID100094914
Headline:	data loss IR to MR migration
Description:	Root cause: MR imports the IR configuration with the DDF size of 64MB, then MR resize it to 512MB lead to a data loss. Fix: Read the Configured_Size from the ddf_PD_Entry and check against the (PD size - DDF_RESERVED_SIZE (512 MB)) if the Configured_Size is grater, then reject the configuration.
State:	Completed
Change Set Files:	0
References:	LSID100094780(DFCT)

Task ID:	LSID100082118
Headline:	FW_SAS Release Version: 1.12.130-0426
Description:	FW_SAS Release Version: 1.12.130-0426
State:	Open
Change Set Files:	0
References:

Task ID:	LSID100082122
Headline:	FW_SAS Release Version: 1.12.131-0427
Description:	FW_SAS Release Version: 1.12.131-0427
State:	Open
Change Set Files:	0
References:

Task ID:	LSID100094953
Headline:	Panic occurs on HWR Linux driver(megaraid_sas)
Description:	1. Set kdump and sysrq. 2. System rebooting. 3. Endlessly do I/O. # dd if=/dev/urandom of=data bs=1M count=2048 # while [ -l ] ; do /bin/cp data data2 ; done 4. Do system panic. (On another screen) # echo c > /proc/sysrq-trigger 5. Panic is generated while starting the kdump kernel, and kdump fails.
State:	Completed
Change Set Files:	0
References:	LSID100092025(DFCT)

Task ID:	LSID100082128
Headline:	Increment Maintenance Version from 13 to 14
Description:	Increment Maintenance Version from 13 to 14
State:	Open
Change Set Files:	0
References:

Task ID:	LSID100082067
Headline:	CC automatic scheduling is made oem specific
Description:	CC scAutomatic Scheduling of CC should be enabled only for ACHILLES,ZEUS and CATERA. For the rest it should be disabled. We aslo found the following issue while testing: After BGI is completed, the generated AEN indicates, CC is completed 100%. In LdCCIssue function, LD_CONS_STATUS_BGI & LD_CONS_STATUS_ACTIVE status bits are cleared once the CC/BGI gets completed and then LdCCProgressSet function is called with progress MR_PROGRESS_DONE. LdCCProgressSet function checks the above status bits, and assumes the default CC operation as those have been already cleared. Hence now in LdCCIssue function, LdCCProgressSet function is called before LD_CONS_STATUS_BGI & LD_CONS_STATUS_ACTIVE status bits are cleared.
State:	Completed
Change Set Files:	0
References:	LSID100094885(CO)

Task ID:	LSID100094997
Headline:	Refine the fix done for LSID100093240
Description:	Use 1.03 implementation of the xor isr for handling the ASR_ACTIVE bit of the XOR engine.
State:	Completed
Change Set Files:	0
References:

Task ID:	LSID100082130
Headline:	FW_SAS Release Version: 1.12.142-0428
Description:	FW_SAS Release Version: 1.12.142-0428
State:	Open
Change Set Files:	0
References:

Task ID:	LSID100082133
Headline:	FW_SAS Release Version: 1.12.142-0428
Description:	FW_SAS Release Version: 1.12.142-0428
State:	Open
Change Set Files:	0
References:

Task ID:	LSID100082139
Headline:	FW_SAS Release Version: 1.12.142-0428
Description:	FW_SAS Release Version: 1.12.142-0428
State:	Open
Change Set Files:	0
References:

Task ID:	LSID100082102
Headline:	Sata drives are offlined when more than 32 drives
Description:	Problem: --------- When more than 32 sata drives are connected, they become offline on reboot. Root Cause: -------------- During SATA drive discovery PL layer need two frames per SATA Drive discovery. There are 128 frames reserved for discovery (non-critical frames). When there are 144 SATA drives number of frames are not enough to discover. Fix: ----- During discovery phase if there are not enough frames available for discovery, then firmware will allow to allocate discovery frames from IO Pool frames. In this phase there will be no active IOs, so there will be no performance drop if discover frames are allocated from IO pool frames.
State:	Completed
Change Set Files:	0
References:

Task ID:	LSID100082107
Headline:	Cannot fully program SAS address in newer iButtons
Description:	Problem Description New batch of I-Buttons have different electrical (AC and DC) characteristics compared to the earlier ones. Also 1-wire pull up resistor (RPUP) mounted on the said 1078 controller had high value of 4K7 instead of recommended value of 2K2. Combination of these 2 factors leads to failure in updating these I-Button devices. Analysis Based upon APP126 and PCN-354 following deviations were observed in FW implementation in MegaRAID code (Oconee-2 Patch 12) Timing Recommended and currently implemented SHA-1 Computation Time           tSCHA          2000uS           tSCHA                1500uS Write_0_low                     Tw0L          60uS                tLOW1+tSLOT           121uS Write_1_low                     Tw1L          6uS               tLOW1               1uS Read                          TRL          9uS               tRDV-tSU (*3)          14 (12) uS Reset low time (tRSTL) is correctly implemented as 480uS however original specification called out for the value of 720uS and PCN-354 clearly states that this value should be modified. (This is not required since new value is already in place.) Implementation 1.     Delay period of SHA-1 engine (tSCHA ) increased from 1500 to 2000 uS 2.     MegaRAID FW modified to support operations that demand high amount of current viz. programming (programming current ILPROG 800uA) and SHA1 authentication / update (computation current ILCSHA 1000uA). While invoking these functions, 1-wire interface changed from open drain to drive logic state. 3.     All the other timing parameters kept the same for now. Justification for using high drive mode Minimum high input voltage defined for I-Button devices (VHmin) is 2.8V (including programming and SHA-1 computation modes). The maximum current the device can consume during high current mode is 800uA for programming and 1000uA for SHA computation. At 3.3V with 10% regulation, calculated value of Rpup is in the range of [(3.3 * 0.9) – 2.8]V / 1000uA = 170 ohm. During normal operation (read / write), for 1078 maximum low input voltage (VLmax) is 0.8V. At 3.3V with 10% regulation, Iload value can be calculated as: [(3.3 * 1.1) – 0.8]V / 170 ohm = 16.6 mA. However I-Button devices can sink maximum 4mA current while maintaining voltage level low (at 0.4V). So minimum value of Rpup is [(3.3 * 1.1) – 0.8]V / 4mA = 700 ohm. For value of Rpup lower than 770ohm (assuming 10% tolerance), normal read operation can not be guaranteed. As a solution, GPIO pin used as 1-wire interface for I-Button is changed from open drain to totem-pole only during high current operations SHA computations and programming. Rpup is maintained at the current recommended value of 2K2. Result With this code modification, failure seen on the said controller is eliminated.
State:	Completed
Change Set Files:	0
References:

Task ID:	LSID100082136
Headline:	FW_SAS Release Version: 1.12.142-0428
Description:	FW_SAS Release Version: 1.12.142-0428
State:	Open
Change Set Files:	0
References:

Task ID:	LSID100082104
Headline:	Red LED blink pattern customized
Description:	For rebuild: Fault LED will be blinked with following pattern: On 1040ms, Off 960 ms That's the closest we can do to one second on, and one second off. For Hotspare: Blink pattern should be: On 160ms, Off 160ms. This shall cycle 8 times – 1280ms. Followd by Off – 720ms. That's the closest we can do to customer expectation of On:Off cycling for 1 second and off for 1 second
State:	Completed
Change Set Files:	0
References:	LSID100094931(CO)

Task ID:	LSID100082113
Headline:	FW_SAS Release Version: 1.12.132-0425-TEST
Description:	FW_SAS Release Version: 1.12.132-0425-TEST
State:	Open
Change Set Files:	0
References:

Task ID:	LSID100082114
Headline:	FW_SAS Release Version: 1.12.132-0425
Description:	FW_SAS Release Version: 1.12.132-0425
State:	Open
Change Set Files:	0
References: