Bug 141984
Summary: | setting kernel parameters at bootup give soft hang with ati firegl x1 installed | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Stephen Adler <adler> |
Component: | procps | Assignee: | Karel Zak <kzak> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | adler |
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: | 2005-10-20 12:42:22 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
Stephen Adler
2004-12-06 16:19:25 UTC
sysctl is called more times in rc.sysinit, when it hang up? During "Configuring kernel parameters: ..."? What do you have in the file /etc/sysctl.conf? Can you try after complete boot do as root: # sysctl -e -p /etc/sysctl.conf yes, its during the "Configuring kernel parameters: ...". The problem is that I can't boot into an operational state since the system hangs at the "Configuring kernel parameters:..." state. Do you know how I can boot up without it configuring the kernel? Is there a way to disable this step during boot up? You have to boot to "emergency" mode, see: http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/s1-rescuemode-booting-emergency.html and edit the file /etc/rc.d/rc.sysinit. At line cca 234 you can found code: action $"Configuring kernel parameters: " sysctl -e -p /etc/sysctl.conf please, disable this line by '#' Now you can try boot to standard mode. Any progess with FC4? Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received the feedback we requested, we will assume the problem was not reproduceable or has been fixed in a later update for this product. Users who have experienced this problem are encouraged to upgrade to the latest update release, and if this issue is still reproduceable, please REOPEN this big report. |