Description of problem: kernel panics when attempting a default options boot on AMD-K6 CPU's Version-Release number of selected component (if applicable): Kernel 2.6.9-67 and above. How reproducible: Always Steps to Reproduce: 1. Attempt to boot kernel on stated CPU type 2. 3. Actual results: Kernel Panic Expected results: Successful boot Additional info: appending nomce to the kernel option line is a workaround.
Created attachment 328933 [details] patch that 'Clears MCE flag on AMD K6' As detailed in the referenced CentOS bug tracker, a patch that fixes the issue is available (thanks to mlyda) which originally appeared on the LKML: http://lkml.org/lkml/2007/5/17/122 At least 3 people have reported that the patch indeed fixed the boot problem.
Patch looks good. P.
Created attachment 330392 [details] RHEL4 fix for this issue
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.
Set exception flag to "?". Did this work in earlier versions of RHEL 4? If so, this is a regression.
Committed in 82.EL . RPMS are available at http://people.redhat.com/vgoyal/rhel4/
~~ Attention Partners! Snap 1 Released ~~ RHEL 4.8 Snapshot 1 has been released on partners.redhat.com. There should be a fix present, which addresses this bug. NOTE: there is only a short time left to test, please test and report back results on this bug at your earliest convenience. If you encounter any issues, please set the bug back to the ASSIGNED state and describe the issues you encountered. If you have found a NEW bug, clone this bug and describe the issues you encountered. Further questions can be directed to your Red Hat Partner Manager. If you have VERIFIED the bug fix. Please select your PartnerID from the Verified field above. Please leave a comment with your test results details. Include which arches tested, package version and any applicable logs. - Red Hat QE Partner Management
~~ Attention! Snap 4 Released ~~ RHEL 4.8 Snapshot 4 has been released on partners.redhat.com. There should be a fix present that addresses this bug. NOTE: there is only a short time left to test, please test and report back results on this bug ASAP. The latest kernel build can be obtained here: http://people.redhat.com/vgoyal/rhel4/ If you encounter any issues, please set the bug back to the ASSIGNED state and describe the issues you encountered. If you have found a NEW bug, clone this bug and describe the issues you encountered. Further questions can be directed to your Red Hat Partner Manager. If you have VERIFIED the bug fix. Please select your PartnerID from the Verified field above. Please leave a comment with your test results details. Include which arches tested, package version and any applicable logs.
Patch is in -88.EL kernel.
AMD, can you verify that this fixes the K6 panic?
Testing and verifying on the AMD K6 hardware requires the i586 kernel. Because this is not available from Red Hat, I built it using kernel-2.6.9-89.EL.src.rpm in the vgoyal/rhel4/ directory and made it available from: http://centos.toracat.org/kernel/centos4/586amdpatch/ Please test if you can and report back here.
Thanks Akemi!
Akemi Yagi's kernel build appears to fix the issue and I can once again boot without the nomce flag appended.
Just a quick note to add there was one other success report, this time by the person (mlyda) who provided the original patch in the CentOS bug tracker. It looks certain that kernel kernel-2.6.9-89.EL has fixed the problem.
Thanks everyone! Glad we were able to resolve this issue for you.
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-1024.html