Description of problem: When booting an Intel system with hyperthreading disabled, the following messages appear: "ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x5 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x6 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x7 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707" Version-Release number of selected component (if applicable): 2.6.18-8.el5 How reproducible: always Steps to Reproduce: 1. disable HT in BIOS 2. Boot RHEL5 kernel 3. Actual results: Error messages appear Expected results: Error messages should not appear Additional info: The processors are marked as disabled in the APIC table. This error message can also appear if the _STA method does not exist. Error message is from: drivers/acpi/processor_core.c: is_processor_present()
This message also appears on newer multi-core Intel CPUs that do not have all dies enabled (Tigerton-DC).
See also Private Bug 228851 "CPI Exception (acpi_processor-0681): AE_NOT_FOUND" May be DUP.
Is there a newer BIOS available for this system? I have seen this error on several different systems, and each time it was resolved by updating the BIOS.
I can't see 228851. All Dell system BIOS will have ACPI Processor entry even if hyperthreading is disabled. This message started appearing with the hotplug CPU changes.
So this is a regression? Any chance you can test and determine in which release the regression appeared? Should be easy to fix. Also, there shouldnt be any lack of functionality, as far as I can tell its only the debug message getting printed.
Before I forget (again), after I was asked about this by Dell and I came across the following thread http://bugzilla.kernel.org/show_bug.cgi?id=8570. It would appear as though a patch has just become available but it needs to be accepted upstream.
This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?".
Things are looking very promising upstream. I asked Brian if I can steal this and he said yes. Re-assigning to me.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
in kernel-2.6.18-99.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5
Partners, this bug should be fixed in the latest RHEL 5.3 Snapshot. We believe that you have some interest in its correct functionality, so we're making a friendly request to send us some testing feedback. If you have a chance to test it, please share with us your findings. If you have successfully VERIFIED the fix, please add PartnerVerified to the Bugzilla keywords, along with a description of the results. Thanks!
Fixed in RHEL5.3-Snapshot4 (kernel-2.6.18-124.el5).
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