Bug 60710
Summary: | Kernel Panics after install | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | David <dsp2> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-06-08 01:57: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
David
2002-03-05 06:15:30 UTC
Is this an athlon machine ? Yes, this is an Athlon XP processor. This looks like the athlon bios bug from 55040 then... could you look at that bug and see if the workaround ("noathlon") fixes your problem ? Do I just type linux noathlon at lilo prompt? Also, I need to boot into console mode (runlevel 3), so should I just type linux 3 noathlon? Yes. If that works I recommend upgrading to the 2.4.9-31 erratum kernel which has a workaround for the bios bug included. Thanks a lot... the noathlon option seemed to work perfectly. I am going to upgrade to kernel 2.4.18. Do I still need the noathlon option, and if so what should I put in the lilo.conf file to make it permanent? 2.4.18 should have the same workaround; if not add append = "noathlon" in lilo.conf Thanks, everything seems to be working now. What exactly is the athlon bug? Some bioses leave the chipset in debug mode, and the chipset then "crashes" if there's too much load on the memory bus. "noathlon" disables the kernel's fast memcpy() implementation and therefore reducing the load the kernel puts on the memory bus. |