Messages in this thread | | | Date | Wed, 27 Jan 1999 13:34:56 +0100 (CET) | From | Andrea Arcangeli <> | Subject | Re: did you seen a process stuck in D state? if so read this (nono it's not the fix ;) |
| |
On Wed, 27 Jan 1999, Andrew Over wrote:
> Hi Andrea. > > I applied your patch, and while it helped for some processes, it failed > on others. I wound up with 60 something tasks in the D state (all on > "wait_on_sup..." according to WCHAN), but only got 2 OOPS. > alt-sysrq-T generated another couple of OOPSes.
Could you apply this my patch against clean 2.2.0:
ftp://e-mind.com/pub/linux/arca-tree/2.2.0_arca-4.gz
and tell me if you still can reproduce the process stuck in D state?
There was a big race in 2.2.0. I know at least some of the report of process in D state are been automagically fixed fixing the mmput/get race, but maybe there are some other things to fix...
> >>EIP: c0110cdb <__down+ab/fc> > Trace: c0110c10 <generate_oops+0/20> > Trace: c01b12dc <__down_failed+8/c> > Trace: c012af58 <real_lookup+24/7c> > Trace: c012b13e <lookup_dentry+10a/1b8> > Trace: c012b2b5 <open_namei+6d/370> > Trace: c01097c4 <system_call+34/38>
This doesn't look like the mmget/mmput race but maybe...
Thanks for having applyed my semaphore deadlock detector and given me back a very useful report.
Andrea Arcangeli
- 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/
| |