<br><br><div class="gmail_quote">On Wed, Oct 7, 2009 at 10:44 AM, Bill Gatliff <span dir="ltr"><<a href="mailto:bgat@billgatliff.com">bgat@billgatliff.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Russell King - ARM Linux wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tue, Oct 06, 2009 at 10:43:26AM -0500, Bill Gatliff wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The OOPS messages suggest that the machine has run off into stuff that isn't code, which would be consistent with the stack pointer getting blown out of the stack memory.<br>
<br>
</blockquote>
<br>
I don't follow your line of reasoning.<br>
</blockquote>
<br>
I protected myself by saying I was "speculating". :)<br>
<br>
I think some of the other dumps I saw from him were less clear as to the problem, which combined with his descriptions of how he was triggering the event made me think about stack corruption as a meta-problem.<br>
<br>
Stack corruption could result in register value corruption, for sure. And the fact that his board doesn't fail in the same way each time makes me look more at the pattern of OOPS dumps rather than the individual ones.<br>
<br>
But you've definitely looked at this dump in more detail than I did. So I could be speculating in the wrong direction altogether. I was just trying to distract him until you solved the problem. :)<br>
<br></blockquote></div>Ha! Bill gives the Jedi wave "this isn't the bug you've been looking for".<br>