Bug 60710 - Kernel Panics after install
Summary: Kernel Panics after install
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.2
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-03-05 06:15 UTC by David
Modified: 2007-04-18 16:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-06-08 01:57:05 UTC
Embargoed:


Attachments (Terms of Use)

Description David 2002-03-05 06:15:30 UTC
Description of Problem:
After I install redhat 7.2, there will be kernel panics every time I try to 
boot into linux.  These kernel panics will happen at random times during the 
boot process

Version-Release number of selected component (if applicable):
2.4.9

How Reproducible:
Every time after install

Steps to Reproduce:
1. Install redhat 7.2
2. Boot into linux after install
3. 

Actual Results:
Kernel Panic

Expected Results:
Normal boot into linux

Additional Information:

Comment 1 Arjan van de Ven 2002-03-05 10:49:27 UTC
Is this an athlon machine ?

Comment 2 David 2002-03-05 16:11:56 UTC
Yes, this is an Athlon XP processor.

Comment 3 Arjan van de Ven 2002-03-05 16:15:03 UTC
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 ?

Comment 4 David 2002-03-05 21:54:11 UTC
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?

Comment 5 Arjan van de Ven 2002-03-05 22:00:53 UTC
Yes.
If that works I recommend upgrading to the 2.4.9-31 erratum kernel which has a
workaround for the bios bug included.

Comment 6 David 2002-03-06 21:25:12 UTC
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?

Comment 7 Arjan van de Ven 2002-03-06 21:27:14 UTC
2.4.18 should have the same workaround;
if not add
append = "noathlon"
in lilo.conf

Comment 8 David 2002-03-13 13:52:06 UTC
Thanks, everything seems to be working now.  What exactly is the athlon bug?

Comment 9 Arjan van de Ven 2002-03-13 14:09:24 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.