From: jochen.armkernel@leahnim.org (Jochen De Smet)
To: linux-arm-kernel@lists.infradead.org
Subject: Undefined instruction (ldrshtgt?) on mirabox with 3.11-rc7
Date: Sat, 31 Aug 2013 20:37:41 -0400 [thread overview]
Message-ID: <52228C55.7040503@leahnim.org> (raw)
In-Reply-To: <20130831235434.GM6617@n2100.arm.linux.org.uk>
On 8/31/2013 19:54, Russell King - ARM Linux wrote:
> On Sat, Aug 31, 2013 at 07:00:29PM -0400, Jochen De Smet wrote:
> Hmm, disassemble /m... I'm not up with gdb I'm afraid.
Supposed to show mixed source/assembler I believe.
> Notice the destination addresses similarity to the address of the first
> instruction we think was executed - 0xc0208778 vs c0208378. Here's
> the instruction opcodes for branches to those two locations:
>
> c02107d8: 1affdfe6 bne c0208778
> c02107d8: 1affdee6 bne c0208378
>
> See the single bit difference there on bit 8?
>
> So, this is what I think: either _something_ has cleared that bit, or
> you have a problem with your SDRAM wiring, or your SDRAM containing
> this location is going bad and is suffering from a bit error at this
> location.
>
> I'm afraid that I think you have a hardware problem.
The only counter-indication I have is that the 3.10 kernel I've been
running has
never had any issues, nor the default 2.6.x kernel that came with it. I
might have
just gotten lucky with exactly what those compiled to though I suppose?
I've got 2 of these boxes, so I'll update the kernel on the second one
to this version
as well and see if it reproduces there.
Thanks a lot for the fast diagnosis.
J.
prev parent reply other threads:[~2013-09-01 0:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 16:31 Undefined instruction (ldrshtgt?) on mirabox with 3.11-rc7 Jochen De Smet
2013-08-31 20:06 ` Russell King - ARM Linux
2013-08-31 23:00 ` Jochen De Smet
2013-08-31 23:54 ` Russell King - ARM Linux
2013-09-01 0:37 ` Jochen De Smet [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=52228C55.7040503@leahnim.org \
--to=jochen.armkernel@leahnim.org \
--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