From: n.kinar@usask.ca (Nicholas Kinar)
To: linux-arm-kernel@lists.infradead.org
Subject: Kernel oops with undefined instruction when accessing memory on an AT91 custom system
Date: Sun, 15 May 2011 08:24:36 -0600 [thread overview]
Message-ID: <4DCFE224.4040506@usask.ca> (raw)
In-Reply-To: <20110515073326.GG30539@n2100.arm.linux.org.uk>
Russell King - ARM Linux wrote:
> On Sat, May 14, 2011 at 09:48:08PM -0600, Nicholas Kinar wrote:
>> 0/ I do not own an Atmel at91sam9rl-ek board (I wish that I did), but I
>> would hope to obtain one of these in the near future.
>> 1/ I am building this hardware for a research project, so I've only
>> created only one PCB. Eventually, I intend to make many more copies of
>> this design.
>> 2/ I've tried the same test with all of the caches disabled, and the
>> system runs very slowly (and consumes more power). However, I still
>> receive a kernel oops when running the mtest program (the SD card was
>> not mounted and the caches were off):
> This all looks like either noisy SDRAM signals or power problems for
> the CPU itself causing corruption.
>
Thanks for your response, Russell; this is greatly appreciated. Is
there anything that can be done in the kernel code to work around this
problem? I've checked the power supplies to the CPU, and these seem to
be stable. For dealing with noisy SDRAM signals, is there a way to slow
down the bus accesses so this problem becomes less apparent?
Nicholas
next prev parent reply other threads:[~2011-05-15 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-14 16:28 Kernel oops with undefined instruction when accessing memory on an AT91 custom system Nicholas Kinar
2011-05-14 20:43 ` Nicolas Ferre
2011-05-15 3:48 ` Nicholas Kinar
2011-05-15 7:33 ` Russell King - ARM Linux
2011-05-15 14:24 ` Nicholas Kinar [this message]
2011-05-14 21:41 ` Detlef Vollmann
2011-05-15 3:52 ` Nicholas Kinar
2011-05-15 15:08 ` Detlef Vollmann
2011-05-15 15:15 ` Nicholas Kinar
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=4DCFE224.4040506@usask.ca \
--to=n.kinar@usask.ca \
--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).