Hide Forgot
Description of problem: Similar bug reported in bz #701947 SAS2 Controller Firmware issuing 0x620f fault while IOs and TM are running. This bug needs to be fixed in RHEL5.7 too. Version-Release number of selected component (if applicable): How reproducible: Almost easy to reproducible Steps to Reproduce: 1. Booted RHEL 6 - 32 bit ( Onboard) OS with SAS2 Controller with latest firmware and BIOS. 2. enclosure with SAS drives is connected to LSI SAS2 controller 3. Created RAID0 volume with 10 SAS drives. 4. Created RAID10 volume with 4 SAS drives. 5. Initiated IO's on drives available. 6. Issued Task Management (Port, Target and Lun reset) with 20 sec delay after each reset. 7. After sometime its issuing "mpt2sas0: fault_state(0x620f)!" Actual results: "mpt2sas0: fault_state(0x620f)!" Expected results: There should not firmware fault and IOs should be running smoothly. Additional info: Solution for this patch has been tested by LSI test group. so it is safe patch to include in RHEL6.1 release. There are Tier-1/2 customer intersted to see this patch in RHEL6.1
Please find the patch for this issue at below link. http://marc.info/?l=linux-scsi&m=130450868630805&w=2 I will post rhel5.7 equavalent patch for this issue. Tomas, to make things faster, can you attach current mpt2sas code available in rhel5.7 ~ Kashyap
(In reply to comment #1) > Tomas, to make things faster, can you attach current mpt2sas code available in > rhel5.7 For the RHEL5 code look here - http://people.redhat.com/jwilson/el5/
(In reply to comment #1) > Tomas, to make things faster, can you attach current mpt2sas code available in > rhel5.7 Kashyap, it's not clear to me - are you going to post a patch?
(In reply to comment #3) > (In reply to comment #1) > > Tomas, to make things faster, can you attach current mpt2sas code available in > > rhel5.7 > > Kashyap, it's not clear to me - are you going to post a patch? Sorry I messed up for RHEL5.7 bug submission. RHEL5.7 wants back porting of below RHEL6.1 bug fix. https://bugzilla.redhat.com/show_bug.cgi?id=701951 We should close this bug as "Invalid" I will open new bug Sorry for all. ~ Kashyap
Closing, based on comment#4