Bug 554664
| Summary: | MRG current has a very old megaraid_sas driver | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | IBM Bug Proxy <bugproxy> |
| Component: | realtime-kernel | Assignee: | Luis Claudio R. Goncalves <lgoncalv> |
| Status: | CLOSED ERRATA | QA Contact: | David Sommerseth <davids> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 1.2 | CC: | bhu, lgoncalv, ovasik |
| Target Milestone: | 1.2.5 | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-03-23 15:43:22 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
*** Bug 554681 has been marked as a duplicate of this bug. *** Patch bz554664-scsi-megaraid_sas-add-new-controllers-0x78-0x79.patch, backport of upstream commit 6610a6b354d6c3377a1e79cd1d760ffe4358245c, has been added to kernel 2.6.24.7-247.el5rt patch queue. ------- Comment From johnstul.com 2010-01-18 16:11 EDT------- Rob has tested the -147 kernel with the system in question and it did boot up. I think we can mark this resolved. (In reply to comment #3) > ------- Comment From johnstul.com 2010-01-18 16:11 EDT------- > Rob has tested the -147 kernel with the system in question and it did boot up. > I think we can mark this resolved. This sounds indeed like wonderful news! I don't mean to be a party killer, but have you done any stress tests with this driver? I would just like to be sure that we don't regress on both performance and reliability. After all it's a new controller card which now is supported, which probably means a different firmware and so on. Verified by code review. Found patch mentioned in comment #2 applied to kernel-rt-2.6.24.7-149.src.rpm. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2010-0161.html The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |
=Comment: #0================================================= John G. Stultz <johnstul.com> - So we were trying to bring up MRG on a new box, and ran into trouble when the megaraid sas driver wasn't seeming to find the controller. All we got with kernel-rt-2.6.24.7-146.el5rt.x86_64.rpm was: ----------------------------------------------------------- megasas: 00.00.03.16-rc1 Thu. Nov. 07 10:09:32 PDT 2007 <no driver messages> ... <panic, no root device> Where as with RHEL5.4: ---------------------- SCSI subsystem initialized megasas: 00.00.04.08-RH2 Tues. May 5, 11:41:51 PST 2009 megasas: 0x1000:0x0079:0x1014:0x03b2: bus 9:slot 0:func 0 ACPI: PCI Interrupt 0000:09:00.0[A] -> GSI 24 (level, low) -> IRQ 177 PCI: Setting latency timer of device 0000:09:00.0 to 64 megasas: FW now in Ready state scsi0 : LSI SAS based MegaRAID driver Vendor: IBM-ESXS Model: ST9146803SS Rev: B536 Type: Direct-Access ANSI SCSI revision: 05 Vendor: IBM-ESXS Model: ST9146803SS Rev: B536 Type: Direct-Access ANSI SCSI revision: 05 Vendor: IBM Model: ServeRAID M5015 Rev: 2.0. Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 570310656 512-byte hdwr sectors (291999 MB) sda: Write Protect is off sda: Mode Sense: 1f 00 00 08 SCSI device sda: drive cache: write back, no read (daft) SCSI device sda: 570310656 512-byte hdwr sectors (291999 MB) sda: Write Protect is off sda: Mode Sense: 1f 00 00 08 SCSI device sda: drive cache: write back, no read (daft) sda: sda1 sda2 I suspect the MRG driver stating that its from Nov 07 might mean its a bit old. Talked w/ Chris McDermott and he magically knew what commit *should* fix this: git show 6610a6b354d6c3377a1e79cd1d760ffe4358245c Any chance that this commit could be added?