Bug 146251
Summary: | Boot process hangs at CPUSPEED step on x86_64 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Ryan <galyenrc> |
Component: | kernel | Assignee: | Jarod Wilson <jarod> |
Status: | CLOSED WORKSFORME | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | davej, jbaron, msz, shillman |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-06-15 21:13:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ryan
2005-01-26 14:23:25 UTC
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 beta2. Thanks 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. 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. |