Bug 477236
| Summary: | CPU stuck: soft lockup | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dimitri Maziuk <dmaziuk> | ||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | 9 | CC: | alastemp-amd2009, kernel-maint, quintela | ||||||||
| 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-07-14 15:53:53 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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Dimitri Maziuk
2008-12-19 19:19:07 UTC
Created attachment 327488 [details]
dmesg
Created attachment 327489 [details]
log
You may have run into the TLB bug. I have just been having trouble with that myself, I believe. If you are happy to try it at your own risk, the following attachment may help. You might need to add a line to the switch statement for your cpuid: stepping "03" (from your log) isn't listed in AMD's K10 Revision Guide. Created attachment 343243 [details]
C++ program to enable workarounds for the TLB Bug and other AMD K10 errata - use at your own risk!
Interesting. Thing is, we "upgraded" machines that did lock up (not all did -- from about 20 bough at the same time) from Fedora 9 to CentOS 5 and they've been up for a couple of months now. So I'm filing this for future refence, but at this moment they're not broken anymore. Thanks. Update: I have just finished testing the same CPU (B3 stepping) on a Foxconn A6VMX motherboard (without enabling the erratum 298 workarounds) and it passed just fine. So I need to use the previously attached code to prevent lockups on one manufacturer's motherboard, but not on another's. Presumably a BIOS or hardware bug somewhere in the first system. Glad your systems are working too. This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. 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 '9'. 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 9'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 9 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 Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |