From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Description of problem: After last up2date, the system hung for hours. I had no choice but to reboot. When it came back up it gave me "init: Id "x" respawning too fast: disabled for 5 minutes" I've seen numerous post on this on google, but need a easy to follow recipe to check and repair the problem. Joe Version-Release number of selected component (if applicable): kernel 2.6.10 How reproducible: Always Steps to Reproduce: 1.Reboot 2. 3. Actual Results: init: Id "x" respawning too fast: disabled for 5 minutes Additional info:
Boot into runlevel 3, try running startx, or prefdm by hand, to see where it's failing.
When I boot to runlevel 3 it asks for login but doesn't accept "root" with my root password or my user name and password.
One other think I noticed. I booted to runlevel 3 on another machine (fedorabox) and it comes up saying (fedorabox) login: and it accepts my password. This one that I'm haveing the problem with says (none) login: and won't accept my login.
It sounds like something is screwed up at a farily low level. Does it boot to single user mode successfully?
If you are referring to runlevel 1, it says: INIT: Entering runlevel: 1 INIT: no more processes left in this runlevel
Fedora Core 3 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 FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you!
The information we've requested above is required in order to review this problem report further and diagnose/fix the issue if it is still present. Since there haven't been any updates to the report in quite a long time now after we've requested additional information, we're assuming the problem is either no longer present in our current OS release, or that there is no longer any interest in tracking the problem. Setting status to CANTFIX, however if you still experience this problem after updating to our latest Fedora Core release and are still interested in Red Hat tracking the issue, and assisting in troubleshooting the problem, please feel free to provide the information requested above, and reopen the report. Thank you in advance. (this message is mass message)