All of lore.kernel.org
 help / color / mirror / Atom feed
From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: strange, spurious seeming vector exception on pxa300
Date: Wed, 2 Dec 2009 17:04:00 +0100	[thread overview]
Message-ID: <20091202160400.GE14091@buzzloop.caiaq.de> (raw)
In-Reply-To: <20091202155057.GA30669@n2100.arm.linux.org.uk>

On Wed, Dec 02, 2009 at 03:50:57PM +0000, Russell King - ARM Linux wrote:
> > r12            0x401d6c20    1075670048
> > sp             0x412c8a2c    0x412c8a2c
> > lr             0x4029603c    1076453436
> > pc             0x400ec47c    0x400ec47c <f1+172>
> > fps            0x0    0
> > cpsr           0x60000010    1610612752
> 
> CPSR says NZCV=0110 (zero, carry).  32-bit user mode.
> 
> 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?

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

  reply	other threads:[~2009-12-02 16:04 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 [this message]
2009-12-02 16:39           ` Yeasah Pell

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=20091202160400.GE14091@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.