From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461) Description of problem: When booting from the floppy boot disk, the machine gets past the "Loading initrd..." and the kernel starts running. Some text briefly flickers on the screen (looks like memory probing) and then the machine reboots. The time between the kernel starting and the spontaneous reboot is so fast I can't tell how far the kernel got during the boot. When the machine comes back up (from the reboot) it fails many self tests during boot (memory, cache memory, CPU, floppy). The machine has been running RH 7.3 for about a year without problems. Memtest86 reports no problems over a 24 hour run. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create boot disk from /images/bootdisk.img on CD #1. 2. Boot machine. 3. Actual Results: Machine reboots immediately after loading kernel. Expected Results: Expect kernel to start. Additional info: I tried passing mem=24M, mem=32M and noapic to the kernel without success. The machine has 32M memory (Vectra XU 5/90).
Tried various combinations of "apm=off" and "nomce" with "mem=" and "noapic" without luck. Will try to get serial console working to pin down how far the kernel gets before rebooting.
Created attachment 94773 [details] Boot log from serial console Boot log captured from serial console. Machine reboots after printing the last line - no delay.
I have recently discovered that adding "pci=conf1" or "pci=conf2" to the kernel command line will allow the machine to boot normally. Maybe some driver is not honoring the PCI detection method? This is strange as the boot data shows the kernel is using type 1 configuration.
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/