For everyone's reference, I fixed this problem on my machine by using the
"noathlon" kernel parameter. On the boot diskette, type "linux noathlon", so that
you can boot the system. Use the pico editor (or other) to edit /etc/grub.conf
and add "athlon" to the end of the kernel line so that it looks something like:
kernel /vmlinuz-2.4.7-10 ro root=/dev/hda7 hdc=ide-scsi noathlon
If you used Lilo instead of Grub, there is probably a similar change to /etc/lilo.conf
The release notes mention this problem:
"Some Athlon-class machines are out-of-spec or have overly aggressive
chipset configurations set by their BIOS. On these systems, you
may see random "Oops" messages at boot time (after successfully
completing the install process) and will be unable to boot successfully.
On these systems, boot with the "noathlon" option to turn off the
athlon optimizations; install the 686 kernel instead of the athlon
kernel to avoid this for the future."
My motherboard is an IWILL KK266Plus. I think the ABIT KG7 might have the same
problem.
- Viktors
christopher j bottaro wrote:
>
> i'll try memtest86, but for now, how do i boot with the noathlon option (i
> just read about that in the release notes)? i use grub to boot.
>
> thanks,
> christopher
>
> ----- Original Message -----
> From: "Trond Eivind Glomsrød" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, October 30, 2001 11:53 AM
> Subject: Re: clean 7.2 install kernel panics (among other things)
>
> > "christopher j bottaro" <[EMAIL PROTECTED]> writes:
> >
> > > turning off PnP OS worked for my 1.1ghz athlon abit kt7 system, and now
> > > redhat 7.2 is running great on it. my other system is still kernel
> panics
> > > though. it is a 1.4ghz athlon abit kt7a. they are both practically the
> > > same system! here is the most common error message when i boot up (i
> get
> > > other messages sometimes, but this one is the most common):
> > >
> > > Kernel panic: Aiee, killing interrupt handler!
> > > In interrupt handler - not syncing
> > >
> > > to answer someone elses question, yes i have a USB mouse on the
> offending
> > > system and a regular PS/2 mouse on the working system. i unplugged the
> USB
> > > mouse but still get the kernel panics. i actually got far enough in the
> > > booting process once to remove the USB mouse config in kuduz (or
> whatever it
> > > is called), but it didn't help anything.
> >
> > 1) Do you overclock your system?
> > 2) Can you try memtest86? http://www.memtest86.com/
> >
> > The times I've had this problem, removing bad memory has helped
> >
> > --
> > Trond Eivind Glomsrød
> > Red Hat, Inc.
> >
> >
> >
> > _______________________________________________
> > Redhat-list mailing list
> > [EMAIL PROTECTED]
> > https://listman.redhat.com/mailman/listinfo/redhat-list
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
