From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: Help request - ASoC recursion issue
Date: Tue, 24 Jul 2012 23:46:50 +0100 [thread overview]
Message-ID: <20120724224649.GE1767@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <500E4E2C.3060804@linaro.org>
On Tue, Jul 24, 2012 at 08:26:36AM +0100, Lee Jones wrote:
> Yes, I am inclined to agree with you. I just thought it was
> uncharacteristic of a memory corruption error, as can reliably reproduce
> the bootlog above. What's even more strange is that the issue only
> arises on one of my two _identical_ development boards.
It's not that unusual depending on where the cause is - for example,
copying an initialised struct to the wrong place, and things like the
DAPM graph which are big and pointer driven are often affected.
prev parent reply other threads:[~2012-07-24 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 14:05 Help request - ASoC recursion issue Lee Jones
2012-07-23 14:39 ` Mark Brown
2012-07-23 14:50 ` Lee Jones
2012-07-23 14:56 ` Lee Jones
2012-07-23 18:12 ` Will Deacon
2012-07-24 7:26 ` Lee Jones
2012-07-24 22:46 ` Mark Brown [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=20120724224649.GE1767@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.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).