Processes hanging in D state in 2.4.3 - any findings?
Hi guys,
I have seen several messages posted to l-k about people reporting processes (mozilla most of the time) hanging in the D state in 2.4.3, but I haven't seen someone posting a possible explanation or solution to the problem.
Anyone knows where does the problem lie, or a workaround for the problem? I hate going through the fsck that happens when umount fails because processes are in the D state...
Cheers!
Eloy.-
Quoted 7 lines · Eloy A. Paris
Hi guys,
I have seen several messages posted to l-k about people reporting processes (mozilla most of the time) hanging in the D state in 2.4.3, but I haven't seen someone posting a possible explanation or solution to the problem.
It's due to problems in the rw_semaphore implementation. These were basically unused for a year, then a couple of weeks ago we started using them, and the problems came to light.
Quoted 3 lines
Anyone knows where does the problem lie, or a workaround for the problem? I hate going through the fsck that happens when umount fails because processes are in the D state...
I put out a patch yesterday which will fix the problem. Discussions are ongoing...
-
Quoted 7 lines
I have seen several messages posted to l-k about people reporting processes (mozilla most of the time) hanging in the D state in 2.4.3, but I haven't seen someone posting a possible explanation or solution to the problem.
Anyone knows where does the problem lie, or a workaround for the problem? I hate going through the fsck that happens when umount fails because processes are in the D state...
2.2.19 or wait for 2.4.4pre soon to fix the semaphore problem that causes this