From: Marcus C. <ma...@mc...> - 2002-11-06 00:31:30
|
Following up on my own post: When I add debug printouts, the problem moves. So what we have here is a logic bomb. In both cases where I have been able to identify an actual codepoint where the kernel oopses though, it's been right after a call to __cli(), and the problem has been caused by a bogus value in r30/r31. So it almost looks like these registers are clobbered by an interrupt. Which would probably mean that the stack is trodden on somewhere inside the interrupt handler, causing the bogus values to be read back from the stack upon interrupt return. // Marcus |