CO ID:	LSID100107665
Headline:	CR_Ref# LSID100092613: CTO Enable / Disable In MegaRAID Utilites_HWR_SAS_Bios
Description:	CR_Ref# LSID100092613: CTO Enable / Disable In MegaRAID Utilites
State:	Development_Completed
Associated Task:	LSID100107753

CO ID:	LSID100108730
Headline:	HDD Passthru support in EFI driver_HWR_SAS_Driver_EFI
Description:	Add support of HDD passthru to EFI driver
State:	Development_Completed
Associated Task:	LSID100109351
Suggested Testing:	1) Testing the BlockIO After driver is loaded, verify that a new BlockIO protocl is created by using "map -r" command 2) Using diskpart.efi and efifmt.efi utilities to check the READ/WRITE for the new BlockIO protocol works Use DiskPart to create a partition on the system PD Use EfiFmt to format the partition Copy files from a USB key to that newly create EFI FS and verify the content of the files are intact.

CO ID:	LSID100101910
Headline:	CR_Ref# LSID100098174: MegaRAID Skinny to support: HDD Pass-thru_HWR_SAS_Bios
Description:	CR_Ref# LSID100098174: MegaRAID Skinny to support: HDD Pass-thru
State:	Development_Completed
Associated Task:	LSID100108667
Suggested Testing:	Test case 1: Connect two system PD to Wasat A0 board Verify BIOS POST Make the second system PD as a boot device Either install OS or DOS and make sure you are able to boot to OS (or DOS) Test case 2: Connect two or more system PD to Wasat A0 board Make some of them un-configured good and create more than one RAID volume Verify BIOS POST Make the second system PD as a boot device Either install OS or DOS and make sure you are able to boot to OS (or DOS) Note: Repeat above steps by making one of the VD as a boot device (you can try making first VD as a boot device in other instance you can make other than first VD as a boot device) Test case 3: Connect two or more system PD to Wasat A0 board Make some of them un-configured good and create more than one RAID volume Verify BIOS POST Create DOS partition on each system PD and VD and format them Install OS or DOS on one of them and make sure you are able to boot to OS (or DOS) Run IO on other VDs and system PDs If you could create a situation where system PD and VD has same IDs (for example, system PDs at deviceID 9 and 10 and you create VDs and give number for that 9 and 10) this will help to validate BIOS thoroughly as it would need to index to correct INT13 table etc. Test case 4 (to make sure previously existing functionality works): 1.     Have only un-configured PDs and create RAID configuration 2.     Choose one of the VD as a boot device 3.     Install OS (or DOS) and make sure you could boot to this OS (or DOS partition)

CO ID:	LSID100101910
Headline:	CR_Ref# LSID100098174: MegaRAID Skinny to support: HDD Pass-thru_HWR_SAS_Bios
Description:	CR_Ref# LSID100098174: MegaRAID Skinny to support: HDD Pass-thru
State:	Development_Completed
Associated Task:	LSID100109524
Suggested Testing:	Test case 1: Connect two system PD to Wasat A0 board Verify BIOS POST Make the second system PD as a boot device Either install OS or DOS and make sure you are able to boot to OS (or DOS) Test case 2: Connect two or more system PD to Wasat A0 board Make some of them un-configured good and create more than one RAID volume Verify BIOS POST Make the second system PD as a boot device Either install OS or DOS and make sure you are able to boot to OS (or DOS) Note: Repeat above steps by making one of the VD as a boot device (you can try making first VD as a boot device in other instance you can make other than first VD as a boot device) Test case 3: Connect two or more system PD to Wasat A0 board Make some of them un-configured good and create more than one RAID volume Verify BIOS POST Create DOS partition on each system PD and VD and format them Install OS or DOS on one of them and make sure you are able to boot to OS (or DOS) Run IO on other VDs and system PDs If you could create a situation where system PD and VD has same IDs (for example, system PDs at deviceID 9 and 10 and you create VDs and give number for that 9 and 10) this will help to validate BIOS thoroughly as it would need to index to correct INT13 table etc. Test case 4 (to make sure previously existing functionality works): 1.     Have only un-configured PDs and create RAID configuration 2.     Choose one of the VD as a boot device 3.     Install OS (or DOS) and make sure you could boot to this OS (or DOS partition)

DFCT ID:	LSID100109319
Headline:	SS When installing to a VD that is your boot device, it asks you to put system files onto the 1st system PD
Description:	Having a mix of System PDs and 1 VD r1, if you try and install the OS to VD0/R1 the OS will ask you to partition the system drive in order to put some system files on it. You cannot just install to the VD0 even though it is selected as the boot device. This is also seen with SYSTEM Pds. If you have a system PD selected to boot to, it will ask you to install some files to the VD before installing to the system PD. Using test firmware:2.0.03-0536-TEST-VASUM-0FC3 Win2k3 - 32bit Castor MileHigh Similar issue: Sub: OS installation on the 2nd RAID VD while Unconfig-Good and System PDs are present in the enclosure using test BIOS T2004.08 Created 2 R1 VD (VD0,VD1) while some PDs are Unconfig-Good and some are System PDs in the Shea enclosure. Made VD1 as boot drive in WebBIOS. Started installing Sles10-SP2-x64 on the VD1. On 1st phase of OS installation completion and reboot noticing following: 19990301 Hard Disk Drive Boot Sector Error 1962 Operating System not found So, Sles10-SP2-x64 installation can‚t complete. Test Component: FW Package: 20.1.1.-0006 FW: 2.0.03-0578 Test BIOS: T2004.08
Version of Bug Reported:	T2008.07
Version of Bug Fixed:	4.02.00_x64EFI_0x03040000
Steps to Reproduce:	Have a mix of system PDs and at least 1 VD (R1) Set VD0 to boot to Start installation with Win2l3 32 bit Install driver with F6 Once at the partition Screen, select VD0 to install to at the bottom of the PD list. It will ask you to install files to the 1st system drive in the drive list in order to install to the VD0. You cannot install directly to VD0 even though it's selected as a boot device.
Resolution:	Fixed
Resolution Description:	Fix: Use a byte from EBDA to store INT13 drive type (this will have read/write permission at post as well as at runtime) Root cause: Using the variable defined in code segment to store INT13h drive type which becomes READ only at runtime. Details: During POST few INT13 call comes. We were keeping the drive type for which the last int13 call come during POST. Though we were trying to change the type at runtime as call comes but it is not sticky hence BIOS uses the lastly stored (at POST) int13 drive type to choose command op-code.
Fix Impact:	Low
Suggested Testing:	Have system PD and VDs. Please test this BIOS by trying to install W2k3, Linux flavor OS on VD, try several other combination (that is installing OS on system PD by only having system PD, installing OS on VD by only having VD, install OS on sys PD by having sys PD and VD combination and install OS on VD by having sys PD and VD combination) if possible.
Child Tasks:	LSID100109342

DFCT ID:	LSID100109246
Headline:	The Connected tape drive is not getting listed in the Bios post screen.
Description:	The connected tape drive is not getting listed in the bios post screen but the same is getting listed in the Webbios and also in the debug log. Config:- System:- TX300S3. Cntrlr:-Castor 9260-8i Bios:-3.04.00 Fw Ver:-2.0.03-0572 Os:- Win XP SP2 X64 Drv Ver:-4.4.0.64 MSM:-3.1.04 I/O:- Chaos. tape:- Quantum Ultrium 3 Drive.
Version of Bug Reported:	3.04.00
Steps to Reproduce:	Connect A tape drive. verify that the tape drive is getting listed in the Post or not.
Resolution:	Fixed
Resolution Description:	Root cause: Per CR 51228, so far BIOS displays only disk devices and ignore displaying info about other devices including Tape Change: Display Info of disk, Tape and CD-ROM (though we dont support CDROM today we added this proactively)
Fix Impact:	Cosmetic
Suggested Testing:	Connect Tape to the MegaRAID controller which supports Tape device and make sure BIOS shows Tape info at BIOS POST
Child Tasks:	LSID100109482

DFCT ID:	LSID100109609
Headline:	With FW. package.11.0.1-0007, unable to receive EFI boot messages during post by EFI driver
Description:	After flashing 11.0.1-0006 or 11.0.1-0007, unable to see EFI boot messages during post. Also when boot from USB and go to EFI shell, after giving "drivers" command we see "?" in front of EFI SAS driver line.
Version of Bug Reported:	2.05
Version of Bug Fixed:	2.06.00_x64EFI_0x03050000
Steps to Reproduce:	Flash FW pkg:11.0.1-0007 and reboot the machine. You will notice that EFI driver is not posting any message during boot. Also when you boot from USB stick and go to EFI shell, upon giving "drivers" command user will see "?" in front of LSI Sas EFI driver line.
Resolution:	Fixed
Resolution Description:	Root cause: When delayPOST is set to 60 seconds or more FW stays in undefined sate; HSW treats undefined as an error state and exits with Device Error. Fix: Dont treat undefined as an error state as FW can get out of this state after sometime.
Fix Impact:	Low
Suggested Testing:	Set delay POST to 60 or more seconds
Child Tasks:	LSID100109495

DFCT ID:	LSID100108803
Headline:	BIOS is unable to find boot partition when installing to a VD
Description:	BIOS is unable to find boot partition when installing to a VD
Version of Bug Reported:	T2004.07
Version of Bug Fixed:	4.02.00_x64EFI_0x03040000
Steps to Reproduce:	Create a R1 (Only) on Skinny controller in WebBIOS and set the VD as the boot device Reboot and install W2K3 on the R1 (Install Skinny driver) After the first part of the installation, and system reboots, the BIOS does not find the boot partition again. When going back and using BIOS T2108.06, this issue is not seen.
Resolution:	Fixed
Resolution Description:	Root cause: Originally (before adding system PD support), BIOS was using INT13 drive type 0x2 to refer VD. When we added support for system PD we assigned drive type 0 for VD, 2 for system PD. In Ext Int13 Read Write path of BIOS code this int13 drive type was passed on to stack and BIOS was checking the drive type with hard coded value 0x2; if match not found it falls through CD-ROM path and uses 2k block size, that caused disk error issue while installing OS. Fix: Use the defined macro where the check is made with stack and divert the code to right path for system PD and VD
Customer List:	LSI -- LSI
Fix Impact:	Low
Suggested Testing:	Have a VD and install OS
Child Tasks:	LSID100109030

Task ID:	LSID100107753
Headline:	disableCTO for OEM Catera for 1078
Description:	If OEM is Catera and if the 1078 controller is plugged in to specific Catera system (this system will have specific signature).. then BIOS needs to check disableCTO flag and set it if it is not already set. Please see CO note section for more details.
State:	Completed
Change Set Files:	0
References:	LSID100107665(CO)

Task ID:	LSID100109351
Headline:	Checkin EFI Drv which has Cfg2/Diag2 and skinny
Description:	Check in EFI Driver binary in SAS bIOS stream which has the following two changes: 1. LSID100098174: MegaRAID Skinny to support HDD Pass-Thru 2. LSID100100174/ LSIP200008378: Support DCP2 and Diag2 in UEFI Driver
State:	Completed
Change Set Files:	0
References:	LSID100108730(CO)

Task ID:	LSID100107362
Headline:	Update UEFI Driver v. 0303 Release note under 1078
Description:	Update EFI Driver ver 0x03030000 release note under 1078 release folder and re-release BIOS
State:	Completed
Change Set Files:	0
References:

Task ID:	LSID100109495
Headline:	BIOS: Dont treat Undefined as an error state
Description:	Current BIOS treats undefined as an error state as it exits from Init MFI when FW goes into undefined state thus will not support the controller. If FW needs to delay the POST for 60 or more seconds then FW might stay in undefined swtate for a while hence BIOS should give FW a chance to get out of undefined state.
State:	Completed
Change Set Files:	0
References:	LSID100109609(DFCT)

Task ID:	LSID100109030
Headline:	Fix ExtInt13 Rd/Wr issue when drive type is VD
Description:	Origianlly (before adding system PD support), BIOS was using INT13 drive type 0x2 to refer VD. When we added support for system PD we assigned drive type 0 for VD, 2 for system PD. In Ext Int13 Read Write path of BIOS code this int13 drive type was passed on stack and BIOS was checking the drive type with hard coded value 0x2 if match doesnt found it falls through CD-ROM path and uses 2k block size, that caused disk error issue while installing os. Use the defined macro (0 for VD, 1 for CD and 2 for PD), check the type and divert the flow to right direction based on the drive type (internal ).
State:	Completed
Change Set Files:	0
References:	LSID100108803(DFCT)

Task ID:	LSID100109482
Headline:	Display Tape info during BIOS POST
Description:	Current BIOS displays only disk devices and ignores all other devices per CR 51228. Display SCSI Devices which type is 0 (this is already there), 1 or 5 using this task
State:	Completed
Change Set Files:	0
References:	LSID100109246(DFCT)

Task ID:	LSID100109342
Headline:	Use a byte from EBDA to store INT13 drive type
Description:	Basically, the variables which are defined in code segment are READ only at Runtime. Due to this the value that we update at runtime didnt get store and caused the problem of not being able to install OS on VD when system PD is present (Please read note for more details) Per our requirement, we need to sotre INT13 drive type at global varaible when INT13 call comes from upper layer and use PD_SCSI or LD_SCSI based on the INT13 drive type.
State:	Completed
Change Set Files:	0
References:	LSID100109319(DFCT)

Task ID:	LSID100109524
Headline:	Sys PD:Fire PD LIST Query w/ type 1 and value 0x40
Description:	Originally FW was failing the DCMD (0x0c) if HSW fills type with 1 and value with 0x40 (refer defect: LSID100108797 but FW was giving only sys PD (no SEP or SES) when HSW fires pd list query with type 5. This task is to use DCMD with type 1 and value 0x40 to get the list of system PD...
State:	Open
Change Set Files:	0
References:	LSID100101910(CO)

Task ID:	LSID100108667
Headline:	Support system PD in HWR SAS BIOS
Description:	BIOS should provide int13 support for system PD. BIOS would need to build INT13 table in following manner: Boot device first (if any), followed by VD (if any) and then system PD (if any). If expose all is set to false then BIOS could provide int13 support for max of eight devices (including value at 40:75) BIOS should also detect system PDs and present the numbers to the user during BIOS POST. Based on OEM type BIOS should continue to dispaly PD details to user during BIOS POST.
State:	Completed
Change Set Files:	0
References:	LSID100101910(CO)