On Sat, 2002-08-24 at 13:12, Thunder from the hill wrote:
> We have to check
> 1. process kicking code
> 2. process killing code
> 3. memory allocation code
> 4. read/write code
The problem can be anywhere, actually. #4 (and other file I/O) is the
best bet though, I suspect.
It is caused by any mismatched locking - it is a good debugging check
regardless of preemption.
The only known place I or others see it now is on shutdown, since we
have kernel threads that do not drop the BKL and other locks when they
shutdown since the system is about to halt anyway.
There was some reports of XFS earlier... I thought they were fixed (I
talked to those guys). Maybe some other rogue module...
Robert Love
-
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 Aug 31 2002 - 22:00:14 EST