From: thiago.bauermann@gmail.com (Thiago Jung Bauermann)
To: linux-arm-kernel@lists.infradead.org
Subject: Kernel 3.4 error on Dreamplug: [vectors]: mlock failed: Cannot allocate memory
Date: Thu, 31 May 2012 01:32:10 -0300 [thread overview]
Message-ID: <1338438730.4173.8.camel@hactar> (raw)
In-Reply-To: <20120531030931.GX24238@titan.lakedaemon.net>
On Wed, 2012-05-30 at 23:09 -0400, Jason Cooper wrote:
> Please try a vanilla v3.4 kernel with CONFIG_ARM_APPENDED_DTB.
To be honest I don't feel comfortable about doing that. One
knowledgeable guy on the debian-kernel mailing list said that "the
Kconfig entry for ARM_APPENDED_DTB is quite scary about enabling it and
booting without a DTB appended"[1] and indeed it doesn't look very
encouraging.
Another message on the thread talks about "concerns about damaging other
boards"[2] (maybe I am misreading this one?).
[1] http://lists.debian.org/debian-kernel/2012/03/msg00049.html
[2] http://lists.debian.org/debian-kernel/2012/03/msg00645.html
Is there a risk of damaging the board if it is accidentally booted with
the wrong DTB or without one?
Does it help if I test with only dreamplug-3.4.0.patch (which adds
CONFIG_MACH_DREAMPLUG) applied?
--
[]'s
Thiago Jung Bauermann
next prev parent reply other threads:[~2012-05-31 4:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 18:06 Kernel 3.4 error on Dreamplug: [vectors]: mlock failed: Cannot allocate memory Thiago Jung Bauermann
2012-05-31 0:51 ` Jason Cooper
2012-05-31 2:24 ` Thiago Jung Bauermann
2012-05-31 3:09 ` Jason Cooper
2012-05-31 4:32 ` Thiago Jung Bauermann [this message]
2012-05-31 13:31 ` Jason Cooper
2012-06-01 2:17 ` Thiago Jung Bauermann
2012-06-01 10:50 ` Jason Cooper
2012-06-10 20:16 ` Simon Baatz
2012-06-11 13:04 ` Zdenek Kabelac
2012-06-11 13:06 ` Zdenek Kabelac
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=1338438730.4173.8.camel@hactar \
--to=thiago.bauermann@gmail.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).