From: Catalin Marinas <catalin.marinas@arm.com>
To: naveen yadav <yad.naveen@gmail.com>
Cc: linux-mm <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [ARM]crash on 2.6.35.11
Date: Wed, 4 May 2011 15:21:26 +0100 [thread overview]
Message-ID: <BANLkTi=WYk3_wQ8R1x9JD3-A+asO3cyo4Q@mail.gmail.com> (raw)
In-Reply-To: <BANLkTik17MGwWwFb=CzBduFy9Mn-Ze+ptA@mail.gmail.com>
(fixing up the linux-arm-kernel list address)
On 4 May 2011 14:18, naveen yadav <yad.naveen@gmail.com> wrote:
> On Wed, May 4, 2011 at 3:55 PM, Catalin Marinas <catalin.marinas@arm.com> wrote:
>> On 4 May 2011 11:09, naveen yadav <yad.naveen@gmail.com> wrote:
>>> We are running linux kernel 2.6.35.11 on Cortex a-8. when I run a
>>> simple program expect to give oom.
>>> But it crash with following crash log
>>
>> Could you post the full kernel boot log and .config file?
>
> Pls find attached log
It looks like a problem with the memory configuration on your board.
You have sparsemem sections which are not fully populated. The
mainline kernel still has problems in this area.
You can try this patch (not sure it applies cleanly on 2.6.35 but it's
not difficult to fix):
http://article.gmane.org/gmane.linux.ports.arm.kernel/112994
--
Catalin
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2011-05-04 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 10:09 [ARM]crash on 2.6.35.11 naveen yadav
2011-05-04 10:16 ` Fwd: " naveen yadav
2011-05-11 19:36 ` Russell King - ARM Linux
2011-05-04 10:25 ` Catalin Marinas
2011-05-04 13:18 ` naveen yadav
2011-05-04 14:21 ` Catalin Marinas [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='BANLkTi=WYk3_wQ8R1x9JD3-A+asO3cyo4Q@mail.gmail.com' \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=yad.naveen@gmail.com \
/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).