Red Hat Bugzilla – Bug 135318
Hangs after Enabling Swap Space: OK
Last modified: 2014-03-16 22:49:21 EDT
Description of problem: Booting from VMWare it hangs after it says Enabling Swap Space OK Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Boot 2.Wait for Enabling Swap Space OK message 3.Freeze Actual results: does not continue after that Expected results: should continue after that Additional info:
What evidence do you have that acls are related to the problem? What is hanging, exactly? It would really help to get an "alt-sysrq-t" system trace during the hang (serial console can help to capture the data.)
Okay well i just got this and never really used it yet so just telling me what to do without how to do it wont help..
The bug is against "acl" so I assumed there was some evidence that acls are involved. If not, we need to isolate things to see where things are really stuck. Do you have a null modem cable that you can use to send debugging output from one system to another one? Swap is enabled really early during boot, so if we're hanging there then the normal logging mechanisms have not yet started. And a full trace of running processes will be far too long to capture manually. Has this system ever booted? Did it only recently start failing?
I just installed FC2 and this is the first boot so its never been succesffullly booted yet...and what is acl??
"acl" is the component of FC2 which you filed the bug against. It concerns Access Control Lists. Sounds like it's not really an acl problem, then. :) I'll refile against initscripts, as the hang is occurring somewhere during their execution. We'll still have to narrow it down.
Using VMWare wouldn't affect it right? Because i am running it with that...
If you boot with 'linux single', does it hang?
well now it goes to bash mode after Enabling swap space
OK, boot with 'linux confirm'; answering 'y' to each choice, at which script does it hang?
Um..where exactly do i type that?
The bootloader; the same place you entered 'single'. Note you may need to remove the 'rhgb' option for this.
so in that GRUB booloader screen i edit one of them and just add 'confirm' ? ....i'm completely new to this stuff
Correct, add it to the end of the 'kernel' line.
Nothing different happened....
It didn't give you a choice such as: "Start service foo (Y/N/C)?" OK, boot again with 'single'. When you get to the shell prompt, edit /etc/sysctl.conf. Change the line that says: kernel.sysrq = 0 to: kernel.sysrq = 1 Save, and reboot. When it hangs, hit <Alt>-<SysRq>-<P>, and write down the output there.
Uh it booted and i'm using right now...
Fedora Core 2 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC3 updates or in the FC4 test release, reopen and change the version to match.
Closing for now. Please reopen if it happens again.