Red Hat Bugzilla – Bug 475620
[LTC 5.4 FEAT] Update spufs for Cell in the kernel of RHEL5.4 to the upstream version 
Last modified: 2009-09-02 04:15:52 EDT
Emily J. Ratliff <firstname.lastname@example.org> -
1. Feature Overview:
Feature Id: 
a. Name of Feature: Update spufs for Cell in the kernel of RHEL5.4 to the upstream version
b. Feature Description
The spufs for Cell was updated upstream after the code cutoff for RHEL5.3. Now we would like to
update the spufs in RHEL5.4 to the most current level to incorporate bug fixes, etc. from upstream.
2. Feature Details:
Arch Specificity: Purely Arch Specific Code
Affects Core Kernel: Yes
Delivery Mechanism: Backport
Request Type: Kernel - Enhancement from Upstream
d. Upstream Acceptance: Accepted
Sponsor Priority 1
f. Severity: High
IBM Confidential: no
Code Contribution: IBM code
g. Component Version Target: kernel 2.6.28
3. Business Case
Applying maintenance fixes to the Cell/B.E. kernel specifically for the spufs improves the
reliability of the Cell support in RHEL5.4
4. Primary contact at Red Hat:
5. Primary contacts at Partner:
Project Management Contact:
Hanns-Joachim Uhl, email@example.com, 49-7031-16-4198
Hanns-Joachim Uhl, firstname.lastname@example.org
IBM is signed up to test and provide feedback.
Created attachment 329853 [details]
selected spufs updates
This patch updates spufs by some selected patches.
It applies cleanly on top of 128.el5 and builds just fine.
The kernel boots and passes the spufs-testsuite (except one testcase that also fails on upstream kernels).
Updating PM score.
Created attachment 332526 [details]
This is an update to the original patch and includes the recommendations from Dave. The upstream patch which addresses those comments is 926dc3d76ec7561c72d466d2a0e26cc1a69fc372
You can download this test kernel from http://people.redhat.com/dzickus/el5
Please do NOT transition this bugzilla state to VERIFIED until our QE team
has sent specific instructions indicating when to do so. However feel free
to provide a comment indicating that this fix has been verified.
I verified on 2.6.18-134.el5 that 4 more tests from the spufs-testsuite pass now (compared to 2.6.18-133.el5).
~~ Attention Partners RHEL 5.4 Partner Alpha Released! ~~
RHEL 5.4 Partner Alpha has been released on partners.redhat.com. There should
be a fix present that addresses this particular request. Please test and report back your results here, at your earliest convenience. Our Public Beta release is just around the corner!
If you encounter any issues, please set the bug back to the ASSIGNED state and
describe the issues you encountered. If you have verified the request functions as expected, please set your Partner ID in the Partner field above to indicate successful test results. Do not flip the bug status to VERIFIED. Further questions can be directed to your Red Hat Partner Manager. Thanks!
~~ Attention - RHEL 5.4 Beta Released! ~~
RHEL 5.4 Beta has been released! There should be a fix present in the Beta release that addresses this particular request. Please test and report back results here, at your earliest convenience. RHEL 5.4 General Availability release is just around the corner!
If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity.
Please do not flip the bug status to VERIFIED. Only post your verification results, and if available, update Verified field with the appropriate value.
Questions can be posted to this bug or your customer or partner representative.
------- Comment From email@example.com 2009-07-09 04:37 EDT-------
Verified in RHEL 5.4 Beta .. closing Bugzilla
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.