Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 451591

Summary: Handle invalid ACPI SLIT table
Product: Red Hat Enterprise Linux 5 Reporter: Luming Yu <luyu>
Component: kernelAssignee: Luming Yu <luyu>
Status: CLOSED ERRATA QA Contact: Martin Jenner <mjenner>
Severity: high Docs Contact:
Priority: high    
Version: 5.3CC: cward, dzickus, fenghua.yu, jane.lv, jvillalo, peterm, youquan.song
Target Milestone: ---Keywords: FutureFeature, OtherQA
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-20 19:58:24 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: 428015    
Attachments:
Description Flags
a back port none

Description Luming Yu 2008-06-16 02:21:38 UTC
Description of problem:
It detects the firmware issue and falls back to a reasonable Numa configuration.
We had asked BIOS team to fix the issue on CL. But in the future OEM's BIOS, the
issue could happen again. Without the patch, people even don't notice the issue
and kernel boot with wrong Numa configuration

Version-Release number of selected component (if applicable):


How reproducible:
If the kernel doesn't report "ACPI: SLIT table looks invalid. Not used.", that
means SLIT is valid.

Steps to Reproduce:
1. boot kernel
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Luming Yu 2008-06-18 14:23:26 UTC
Created attachment 309736 [details]
a back port

Comment 3 Don Zickus 2008-07-25 20:26:51 UTC
in kernel-2.6.18-100.el5
You can download this test kernel from http://people.redhat.com/dzickus/el5

Comment 6 Chris Ward 2008-11-14 14:04:53 UTC
~~~ Attention Partners! ~~~

Please test this URGENT / HIGH priority bug at your earliest convenience to ensure it makes it into the upcoming RHEL 5.3 release. The fix should be present in the Partner Snapshot #2 (kernel*-122), available NOW at ftp://partners.redhat.com. As we are approaching the end of the RHEL 5.3 test cycle, it is critical that you report back testing results as soon as possible. 

If you have VERIFIED the fix, please add PartnerVerified to the Bugzilla Keywords field to indicate this. If you find that this issue has not been properly fixed, set the bug status to ASSIGNED with a comment describing the issues you encountered.

All NEW issues encountered (not part of this bug fix) should have a new bug created with the proper keywords and flags set to trigger a review for their inclusion in the upcoming RHEL 5.3 or other future release. Post a link in this bugzilla pointing to the new issue to ensure it is not overlooked.

For any additional questions, speak with your Partner Manager.

Comment 7 Chris Ward 2008-11-18 18:13:18 UTC
~~ Snapshot 3 is now available ~~ 

Snapshot 3 is now available for Partner Testing, which should contain a fix that resolves this bug. ISO's available as usual at ftp://partners.redhat.com. Your testing feedback is vital! Please let us know if you encounter any NEW issues (file a new bug) or if you have VERIFIED the fix is present and functioning as expected (add PartnerVerified Keyword).

Ping your Partner Manager with any additional questions. Thanks!

Comment 8 Luming Yu 2008-11-24 07:22:08 UTC
Confirmed patch is in the -123 kernel.

Comment 10 errata-xmlrpc 2009-01-20 19:58:24 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-0225.html