On Mon, Jul 24, 2000 at 01:46:40AM +0200, Ralf Baechle wrote:
> On Sun, Jul 23, 2000 at 11:25:44AM +0200, octave klaba wrote:
> > [...]
> > root 16705 0.0 0.1 1140 516 ? D 13:25 0:00 /sbin/shutdown -t3 -r 0 w
> > root 16706 0.0 0.0 0 0 ? Z 13:25 0:00 [shutdown <defunct>]
> > [...]
> Something is foobar'ed. The latter process has already died and the first
> process is in a state where it cannot be killed. A process usually
> shouldn't be in `D' state for a longer time. If it is then the usual
> reason is something like access of a NFS access to a server which doesn't
> answer or hopefully more rare, a bug.
As a note I've made most vital processes on a early 2.2.x system (x in {4,7})
go D by creating a swapfile which was 64MB large and telling mkswap it was
128MB. After a while it got utilized over 64MB and things started to break
down..
//Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jul 23 2000 - 21:00:20 EST