Re: Processes hanging in D state in 2.4.3 - any findings?
Hi List, I saw this in the archive. And I guess, I am also seeing this problem on 2.4.4. But I am not sure. Has this problem of rw_semaphore been fixed in 2.4.4 ? If not any idea, when will this be fixed ? Regards, -hiren (408)970-3062 [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Processes hanging in D state in 2.4.3 - any findings?
Hi List, I saw this in the archive. And I guess, I am also seeing this problem on 2.4.4. But I am not sure. Has this problem of rw_semaphore been fixed in 2.4.4 ? If not any idea, when will this be fixed ? Regards, -hiren (408)970-3062 [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Processes hanging in D state in 2.4.3 - any findings?
> 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Processes hanging in D state in 2.4.3 - any findings?
"Eloy A. Paris" wrote: > > 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. > 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... - - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
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.- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
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.- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Processes hanging in D state in 2.4.3 - any findings?
"Eloy A. Paris" wrote: 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. 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... - - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Processes hanging in D state in 2.4.3 - any findings?
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
