There really isn't anything you can do about D state processes. I consider
D to mean dead for this reason. I've seen Netscape go into D state
temporarily (for such an amount of time that I was able to see it) but it
soon returned to S state.
One of the 2.4.0-test kernels had a major deadlock problem for me
(everything was going D state including lilo (when writing out data to the
MBR) and shutdown, among other things.. in fact, I think Netscape might
have been the first to go into D state that night come to think of it).
The next test kernel that I tried seemed to have fixed the problem.
D state generally means deadlock. There's nothing you can really do except
hope it corrects itself... or reboot.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
