I've been having continual unexplained lockup problems since converting one
of my outgoing qmail servers to 2.4.x. This has been discussed before on
this list, where the symptoms are that anything typed on console takes
forever to actually come up, and after a few minutes the machine is so
unresponsive it requires a powercycle.
Noticed that when this box is in its state of unresponsiveness, the process
start times in ps gradually move backwards. The following listings were
taken over about a 1.5 hour timespan.
First
root 1 0 0 11:04 ? 00:00:09 init
root 2 1 0 11:04 ? 00:00:00 [keventd]
root 3 1 0 11:04 ? 00:00:00 [kswapd]
root 4 1 0 11:04 ? 00:00:00 [kreclaimd]
root 5 1 0 11:04 ? 00:00:00 [bdflush]
root 6 1 0 11:04 ? 00:00:02 [kupdated]
root 96 1 0 11:06 ? 00:00:00 [kreiserfsd]
root 356 1 0 11:06 ? 00:00:02 syslogd -m 0
root 366 1 0 11:06 ? 00:00:00 klogd
Second
root 1 0 0 10:54 ? 00:00:09 init
root 2 1 0 10:54 ? 00:00:00 [keventd]
root 3 1 0 10:54 ? 00:00:00 [kswapd]
root 4 1 0 10:54 ? 00:00:00 [kreclaimd]
root 5 1 0 10:54 ? 00:00:00 [bdflush]
root 6 1 0 10:54 ? 00:00:02 [kupdated]
root 96 1 0 10:56 ? 00:00:00 [kreiserfsd]
root 356 1 0 10:56 ? 00:00:02 syslogd -m 0
root 366 1 0 10:56 ? 00:00:00 klogd
Third
root 1 0 0 10:03 ? 00:00:09 init
root 2 1 0 10:03 ? 00:00:00 [keventd]
root 3 1 0 10:03 ? 00:00:00 [kswapd]
root 4 1 0 10:03 ? 00:00:00 [kreclaimd]
root 5 1 0 10:03 ? 00:00:00 [bdflush]
root 6 1 0 10:03 ? 00:00:02 [kupdated]
root 96 1 0 10:06 ? 00:00:00 [kreiserfsd]
root 356 1 0 10:06 ? 00:00:02 syslogd -m 0
root 366 1 0 10:06 ? 00:00:00 klogd
Fourth
root 1 0 0 09:53 ? 00:00:09 init
root 2 1 0 09:53 ? 00:00:00 [keventd]
root 3 1 0 09:53 ? 00:00:00 [kswapd]
root 4 1 0 09:53 ? 00:00:00 [kreclaimd]
root 5 1 0 09:53 ? 00:00:00 [bdflush]
root 6 1 0 09:53 ? 00:00:02 [kupdated]
root 96 1 0 09:55 ? 00:00:00 [kreiserfsd]
root 356 1 0 09:55 ? 00:00:02 syslogd -m 0
root 366 1 0 09:55 ? 00:00:00 klogd
Thoughts?