Bug 243172
| Summary: | APIC-Error "timer not connected to IO-APIC | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tobias Vogel <tobias.vogel> |
| Component: | kernel | Assignee: | Peter Martuccelli <peterm> |
| Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 9 | CC: | achrisjo, kernel-maint, peterm, p.van.egdom, quintela, triage |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-05-21 13:32:05 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: | |||
|
Description
Tobias Vogel
2007-06-07 17:42:13 UTC
Same problem with Fedora8 x86_64
My believe is that it appears earlier on screen:
ACPI Error (tbfadt-0453): 32/64X address mismatch in "Pm2ControlBlock":
[00008800] [0000000000008100], using 64X [20070126]
On Fedora-test-list:
Alan Cox wrote:
>If you've found an APCI spec bug send a note to Len Brown anyway (you
> can file a bug but Len at the end of the day is the Mr ACPI)
> <len.brown>.
>
I sent dmesg files, screen copy, to "len", and the bug may be more serious
as at times the error goes undetected ( APIC error on CPU1 doesn't show in
log log files, etc. )
//ARNE
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists. Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs: http://docs.fedoraproject.org/release-notes/ The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Personal opinion: the bug-report shows history which may be of value. The bug is present in Fedora 8, and I suspect it will be in Fedora 9. Changing version from "7" to "8". This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Moving to proper component and changing version from 8 to 9 to make sure it doesn't get autoclosed. Regards, Phil The most common cause of this problem is a misconfigured APIC and most often the APIC is misconfigured before boot (by the BIOS). Can we verify the BIOS is not the culprit? Please verify the BIOS with Linux Firmware Kit. Download the latest ISO and boot off CD. Download from -> http://linuxfirmwarekit.org/download.php Also, can you attach a /var/log/dmesg from the affected hardware? Closing out due to inactivity. If the reporter is still having a problem in F11 Beta please update the report with the required information from comment #7. The error is present in Fedora-10, just not announced in the same way. Here is from Fedora-10: ACPI Error (tbfadt-0453): 32/64X address mismatch in "Pm2ControlBlock": [0000880 0] [0000000000008100], using 64X [20080609] ( compare it to Comment #1 ) |