Bug 55496

From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.14-pre6 i686)

Description of problem:
We have been unable to boot PC133 AMD Athlon systems using AMD-compiled
kernel (i.e. using CONFIG_MK7=y) with 2.4.7 through about 2.4.9.   It
appears this is what one gets when installing on an Athlon system, for we
had kernel 2.4.7 that completely barfs right after offered the option to
choose "I" for "interactive mode" (Aiees, loss of interrupts, and many
humorous kernel panic errors that I have never seen, other than in this
situation).  First system we tried was in a Tyan KT-A S2390B motherboard,
with an AMD Tbird 1.4 GHz.  Swapped motherboards and removed all hardware
but essentials and same thing happened, which reminded me of the problem we
used to see with 2.4.7 kernel and AMD PC133 systems.  Problem does *not*
appear on AMD DDR systems.

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


How reproducible:
Always

Steps to Reproduce:
1. Build an AMD (Tbird or better, I think) system using a PC133 memory bus
motherboard.
2. Install Red Hat 7.2.
3. Accept "Congratulations" and press Enter to reboot your machine.
	

Actual Results:  See description.

Expected Results:  Well, this is what PC133 based AMD systems frequently do
with 2.4.7 kernel using CONFIG_MK7=y; in a sense, what should have
happened, happened.

Additional info:

We fix by rebooting into installer, changing to shell (Alt-F2), mknod
/dev/hda b 3 0 and /dev/hda1 b 3 1
(this is / for us ), mkdir /tmp/mnt, mount /dev/hda1 /tmp/mnt, chroot
/tmp/mnt, make sure /boot is mounted, copy kernel (we built that will boot)
from floppy and modules if necessary into /boot and /lib/modules, edit
/etc/lilo.conf to boot new kernel, /sbin/lilo, umount whatever you mounted
after chroot'ing, exit, umount /mnt/hda1, reset, and boot new system.