From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
After an indeterminate period (from hours to days) the machine enters
a state whereby a number of things fail to operate as they should.
- Console logins (root or otherwise) hang and timeout
- Console ctrl-alt-del fails to reboot machine
- ssh with or without stop at "Entering interactive session"
Most processes that were already running continue unaffected.
Sometimes the gnome menu bars will also freeze.
The only cure is to reboot.
Version-Release number of selected component (if applicable):
kernel-2.6.9-1.681_FC3 (and earlier)
Steps to Reproduce:
2. Try to login as root
Actual Results: login timeout or ssh session hangs
Expected Results: Clean login
Are there any messages in the logs?
I was actually working on this very question all afternoon. I can now
say that I can see no pattern. There is certainly nothing directly
related, no oopses or anything.
There may be a link with BIND failures leading to NFS automount
freezes on mounts that are defined by hostnames in DNS that aren't
/etc/hosts .. maybe. I mention this as a "thought in progress" only.
It is more likely that the problem is the other way round. ie The
failure causes BIND and NFS problems.
Are you using network-based auth and/or homedirs?
All the user auth is "files" based. The ordinary users are autofs'ed
off /home, but the directories are on this box.
However, the root user cannot log in and the home dir is /root on the
root filesystem, with the passwd entry being on /etc/passwd line 1.
Can you enable sysrq and get sysrq-t (or -p or -m) to see what it's
doing when it's hung?
I also get very long latency on ctrl-alt-del. also the FC3 kernels
hang instead of rebooting... when i want to reboot, it's the reset
button (after everything's been unmounted).
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
This hasn't happened for a while now.
Sorry, not sure what fixed it.