Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 451591 - Handle invalid ACPI SLIT table
Summary: Handle invalid ACPI SLIT table
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.3
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Luming Yu
QA Contact: Martin Jenner
Depends On:
TreeView+ depends on / blocked
Reported: 2008-06-16 02:21 UTC by Luming Yu
Modified: 2013-08-06 01:43 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2009-01-20 19:58:24 UTC
Target Upstream Version:

Attachments (Terms of Use)
a back port (deleted)
2008-06-18 14:23 UTC, Luming Yu
no flags Details | Diff

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2009:0225 normal SHIPPED_LIVE Important: Red Hat Enterprise Linux 5.3 kernel security and bug fix update 2009-01-20 16:06:24 UTC

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
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

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 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 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.

Note You need to log in before you can comment on or make changes to this bug.