On Fri, 2002-08-09 at 16:22, Jun Sun wrote:
> Call me crazy - I have seen crash like this. As you can see, the register is
> loaded with one value and on next instruction it shows another value. What
> the hell is it possibly going on?
As presented, this seems exceedingly unlikely; even processor bugs don't
look quite like this. You just don't lose state in such a blatant
I'd be more inclined to believe that we took an interrupt and somehow
the saved processor state was corrupted. The positioning of the code
looks suspicious to me; we're shortly into a bottom half, which means
if we just, say, unmasked an interrupt in the SCD, we could quite
possibly take the interrupt around then.
Unfortunately, unless you can reliably reproduce this crash, there's not
enough info there to really do more than speculate wildly.