On Mon, 2002-12-02 at 00:21, Andrea Arcangeli wrote:
> On Sun, Dec 01, 2002 at 02:37:13PM +0000, Nuno Monteiro wrote:
> >
> > Trace; c0117114 <__run_task_queue+4c/60>
> > Trace; c011e0e9 <context_thread+11d/19c>
> > Trace; c010588c <kernel_thread+28/38>
>
> ok, now it's clear what the problem is. there are inuse-dirty inodes
> that triggers a deadlock in the schedule-capable
> try_to_sync_unused_inodes of 2.4.20rc2aa1 (that avoided me to backout an
> otherwise corrupt lowlatency fix). It can trigger only in UP,
> in SMP the other cpu can always run kupdate that will flush all dirty
> inodes, so it would lockup one cpu as worse for 2.5 sec, this is
> probably why I couldn't reproduce it, I assume all of you reproducing
> the deadlock were running on an UP machine (doesn't matter if the kernel
Correct (for me anyways).
> was compiled for SMP or not).
>
> Can you give a spin to this untested incremental fix?
>
Yep, this also works for me.
> thanks,
>
> Andrea
Cheers, (excellent work)
Andrew Clayton
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 07 2002 - 22:00:14 EST