linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: bgat@billgatliff.com (Bill Gatliff)
To: linux-arm-kernel@lists.infradead.org
Subject: i.MX31 kernel panic and irq
Date: Wed, 07 Oct 2009 09:44:27 -0500	[thread overview]
Message-ID: <4ACCA94B.60708@billgatliff.com> (raw)
In-Reply-To: <20091007132051.GB11371@n2100.arm.linux.org.uk>

Russell King - ARM Linux wrote:
> On Tue, Oct 06, 2009 at 10:43:26AM -0500, Bill Gatliff wrote:
>   
>> 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.
>>     
>
> I don't follow your line of reasoning.

I protected myself by saying I was "speculating".  :)

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.

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.

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.  :)


b.g.

-- 
Bill Gatliff
bgat at billgatliff.com

  reply	other threads:[~2009-10-07 14:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 15:08 i.MX31 kernel panic and irq Wolf, Rene, HRO-GP
2009-10-06 15:43 ` Bill Gatliff
2009-10-07  7:57   ` Wolf, Rene, HRO-GP
2009-10-07 12:45     ` Bill Gatliff
2009-10-07 13:20   ` Russell King - ARM Linux
2009-10-07 14:44     ` Bill Gatliff [this message]
2009-10-08  1:21       ` Brian Hutchinson
2009-10-08  8:16       ` Wolf, Rene, HRO-GP

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4ACCA94B.60708@billgatliff.com \
    --to=bgat@billgatliff.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).