From: yeasah@comrex.com (Yeasah Pell)
To: linux-arm-kernel@lists.infradead.org
Subject: strange, spurious seeming vector exception on pxa300
Date: Wed, 02 Dec 2009 11:39:10 -0500 [thread overview]
Message-ID: <4B16982E.2000704@comrex.com> (raw)
In-Reply-To: <20091202160400.GE14091@buzzloop.caiaq.de>
Daniel Mack wrote:
> On Wed, Dec 02, 2009 at 03:50:57PM +0000, Russell King - ARM Linux wrote:
>>
>>
>> Given that the conditions are clearly wrong for a vector exception, I would
>> say that you're hitting some kind of hardware bug - maybe caused by a dirty
>> power supply to the PXA, causing it to misbehave?
>>
Of course I desperately want to believe this, as then I can ignore all
this insanity and move on, but it's a bit difficult to swallow that some
kind of hardware issue would cause a failure that is so consistent (same
instruction every time, regardless of physical/virtual memory locations,
compilation flags, etc.) yet caused absolutely no other perceptible
problems...
> We've had trouble of that kind as well some month ago with an early
> prototype. It wasn't an exception we got, but the bug was clearly
> hitting the same code path every single time, so this issue might be
> related. Eventually it went away with new board revision which made wire
> patching around the DDR SDRAM unnecessary (i.e, cleaner signal pathes).
>
> Strange enough, I would have expected such flaws to cause processor
> misbeviour of all sorts, totally random and unpredictable. The fact that
> is was the same function we always ended up in is still some kind of
> miracle I can't explain.
>
> Daniel
>
...and having some anecdotal evidence of that kind of situation
happening is helpful.
Thanks, guys.
prev parent reply other threads:[~2009-12-02 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 22:13 strange, spurious seeming vector exception on pxa300 Yeasah Pell
2009-12-02 6:00 ` Eric Miao
2009-12-02 6:07 ` Eric Miao
2009-12-02 14:40 ` Yeasah Pell
2009-12-02 15:50 ` Russell King - ARM Linux
2009-12-02 16:04 ` Daniel Mack
2009-12-02 16:39 ` Yeasah Pell [this message]
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=4B16982E.2000704@comrex.com \
--to=yeasah@comrex.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).