Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 527421

Summary: HS21xm i5000_edac kernel topology fix
Product: Red Hat Enterprise MRG Reporter: IBM Bug Proxy <bugproxy>
Component: realtime-kernelAssignee: John Kacur <jkacur>
Status: CLOSED ERRATA QA Contact: David Sommerseth <davids>
Severity: medium Docs Contact:
Priority: low    
Version: 1.2CC: bhu, jkacur, lbrindle, lgoncalv, mmcallis, ovasik
Target Milestone: 1.2   
Target Release: ---   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Not in relnote RT bug fix A problem existed with the i5000_edac driver under some topologies. In some cases, this driver failed to export memory devices via sysfs, preventing the ibm-prtm service from starting. With this update, the memory devices are accessible, allowing the ibm-prtm service to start, and therefore perform SMI remediation as expected.
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-03 11:28:11 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 Depends On:    
Bug Blocks: 527551    
Attachments:
Description Flags
i5000_edac kernel patch fix none

Description IBM Bug Proxy 2009-10-06 11:00:35 UTC
=Comment: #0=================================================
KEITH MANNTHEY <kmannth.com> - 
As part of validing 2.6.31 kernel I fixed a know problem with the i5000_edac driver.   In some
topolgies the driver would fail to expose memory devices via sysfs and the ibm-prtmd service would
not start.  

It is a pretty simple fix and it has one Ack so far on the edac mainling list.  I don't see why it
will not go upstream. 

Without this patch smi remediation  is not enable on about 1/2 of the possible memory topologies.
=Comment: #1=================================================
KEITH MANNTHEY <kmannth.com> - 

i5000_edac kernel patch fix

Comment 1 IBM Bug Proxy 2009-10-06 11:00:39 UTC
Created attachment 363811 [details]
i5000_edac kernel patch fix

Comment 4 IBM Bug Proxy 2009-10-30 01:30:45 UTC
------- Comment From kmannth.com 2009-10-29 21:24 EDT-------
This tested good with 2.6.31.4-rt14.27.el5rt. Thanks for pickup up the fix.

Comment 5 Luis Claudio R. Goncalves 2009-11-09 23:36:56 UTC
This change was also added to our V1 kernel and will be available on kernel -138.

Comment 7 David Sommerseth 2009-11-18 16:07:15 UTC
Verified by code review.  Found attached patch implemented in 2.6.24.7-139.

CVS: bz527421-smi-remediation-simple-fix.patch
mrg-rt-v1.git: b1665c93e2f0fadaafb45b1ab1201450f397bfcf


Tried to boot both -137 and -139 kernel on an HM21xm blade, without noticing any immediate difference in behaviour.  Might be HW configuration dependent?

Comment 9 Lana Brindley 2009-11-30 22:14:11 UTC
Release note added. If any revisions are required, please set the 
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

New Contents:
RT bug fix

C: A problem existed with the i5000_edac driver under some hardware topologies.
C: Occasionally, the driver would fail to expose memory devices via sysfs and the ibm-prtmd service would not start.  
F: The memory devices are now accessible.
R: ibm-prtm can now perform SMI remediation as expected.

Comment 10 Lana Brindley 2009-11-30 22:17:47 UTC
Release note updated. If any revisions are required, please set the 
"requires_release_notes"  flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

Diffed Contents:
@@ -3,4 +3,6 @@
 C: A problem existed with the i5000_edac driver under some hardware topologies.
 C: Occasionally, the driver would fail to expose memory devices via sysfs and the ibm-prtmd service would not start.  
 F: The memory devices are now accessible.
-R: ibm-prtm can now perform SMI remediation as expected.+R: ibm-prtm can now perform SMI remediation as expected.
+
+A problem existed with the i5000_edac driver under some hardware topologies. Occasionally, the driver would fail to expose memory devices via sysfs, and the ibm-prtmd service would not start. The memory devices are now accessible and ibm-prtm can perform SMI remediation as expected.

Comment 11 Lana Brindley 2009-12-02 01:18:04 UTC
Release note updated. If any revisions are required, please set the 
"requires_release_notes"  flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

Diffed Contents:
@@ -1,3 +1,5 @@
+Not in relnote
+
 RT bug fix
 
 C: A problem existed with the i5000_edac driver under some hardware topologies.

Comment 12 Murray McAllister 2009-12-03 05:42:33 UTC
Release note updated. If any revisions are required, please set the 
"requires_release_notes"  flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

Diffed Contents:
@@ -2,9 +2,8 @@
 
 RT bug fix
 
-C: A problem existed with the i5000_edac driver under some hardware topologies.
+A problem existed with the i5000_edac driver under some topologies. In
-C: Occasionally, the driver would fail to expose memory devices via sysfs and the ibm-prtmd service would not start.  
+some cases, this driver failed to export memory devices via sysfs,
-F: The memory devices are now accessible.
+preventing the ibm-prtm service from starting. With this update, the memory
-R: ibm-prtm can now perform SMI remediation as expected.
+devices are accessible, allowing the ibm-prtm service to start, and
-
+therefore perform SMI remediation as expected.-A problem existed with the i5000_edac driver under some hardware topologies. Occasionally, the driver would fail to expose memory devices via sysfs, and the ibm-prtmd service would not start. The memory devices are now accessible and ibm-prtm can perform SMI remediation as expected.

Comment 14 errata-xmlrpc 2009-12-03 11:28:11 UTC
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-2009-1635.html