On Sat, 2003-03-29 at 16:42, Shawn Starr wrote:
> How can I go about debugging this? How can I find the path causing
> the problem?
Begin by finding out where the EIP is. It should be a spin_lock(). The
oops says it is kernel/timer.c:258.
This line is a double locking of an already-locked lock. So find where
the initial lock was. The oops said that is kernel/timer.c:398.
Look at the call chain (from the oops) from the first to the second
lock. Someone assumed it could not happen. Obviously they were wrong.
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 : Mon Mar 31 2003 - 22:00:34 EST