From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041220 Firefox/1.0 Fedora/1.0-6.centos4.2
Description of problem:
The process cpuspeed causes the boot process to halt at this step on
the x86_64 version. Forcing a hard boot is the only way to end the
boot process. Boot process will not advance beyond this point. This
also appears in Fedora Core, Version 3 for x86_64 also. Hare is
DFI LanParty UT 250GB
nForce 3 chipset
AMD 64 3200+
80 GB Maxtor IDE drive
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install either RHEL 4.0 Beta2 or FC3 for x86_64
2. Attempt to boot either OS
3. OS will lock on cpuspeed and will not proceed.
Actual Results: Boot process hung and would not advance on step
Expected Results: It should have booted completely in the OS,
providing a stable OS for use.
Have you checked if this still happens with the rhel4 release candidate?
Where do I acquire the RC? All I've been able to get a hold of is RHEL 4
Just determined that we are not able to reproduce this in-house on one of our
own beta2 x86_64 boxes, so I'm suspecting something specific to your hardware.
Did this machine work with previous releases?
I have not been able to boot FC3 x86_64 SMP kernels (none of the available,
2.6.9 and higher) until I disabled 'cpuspeed' services. Contrary to the original
post, there was no proble to boot the system into uP kernel. That is how I was
able to disable cpuspeed. The hangs were at random places after 'cpuspeed' but I
have never got to the end of the boot process.
Also, the machine was resetting right after GRUB initial screen when trying to
boot SMP kernel after a reboot from uP session (w/o hard reset or power off/on).
The reason seems to be that the machine's CPU(s) were left in low-frequency
(1GHz instead of nominal 2.4GHz). The BIOS screen shows 1.0GHz until a hard reset.
My machine is dual-Opteron 250, Tyan K8W S2875 MoBo. Fedora Core 3 x86_64.
Michal - as your comment is specific to FC, and does not appear to relate to
RHEL at all, would you please open a new bug for Fedora Core for your problem?
I have just opened it for FC3, bug #158523
Can this issue be reproduced with the latest RHEL4 bits?
No activity on this bug in 2 years, works fine on a ton of hardware we have
in-house. Closing WORKSFORME.