From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: New dapm panic on beaver with next-20130730
Date: Wed, 31 Jul 2013 11:36:10 +0100 [thread overview]
Message-ID: <20130731103610.GH9858@sirena.org.uk> (raw)
In-Reply-To: <51F8B045.8030303@metafoo.de>
On Wed, Jul 31, 2013 at 08:35:49AM +0200, Lars-Peter Clausen wrote:
> 0x6b6b6b6b is poisoned freed memory. According to the source neither
> the INR Mux nor the INL Mux widget should have any sinks. Can you
> add a couple more printks:
Dan Carpenter sent a patch which is probably the issue - I'm trying to
figure out how to boot my Beaver board so hopefully I can test, it'll be
in -next tomorrow anyway.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130731/62a5d1e0/attachment-0001.sig>
next prev parent reply other threads:[~2013-07-31 10:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 5:36 New dapm panic on beaver with next-20130730 Olof Johansson
2013-07-31 6:05 ` Lars-Peter Clausen
2013-07-31 6:13 ` Olof Johansson
2013-07-31 6:35 ` Lars-Peter Clausen
2013-07-31 10:36 ` Mark Brown [this message]
2013-07-31 19:09 ` Stephen Warren
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=20130731103610.GH9858@sirena.org.uk \
--to=broonie@kernel.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;
as well as URLs for NNTP newsgroup(s).