From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Fwd: [ARM]crash on 2.6.35.11
Date: Wed, 11 May 2011 20:36:02 +0100 [thread overview]
Message-ID: <20110511193602.GK5315@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <BANLkTi=oZ0Mr33rL=QNmzDuaKLNezoKBXg@mail.gmail.com>
On Wed, May 04, 2011 at 03:46:55PM +0530, naveen yadav wrote:
> Attaching test case
>
> Dear all,
>
> 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
You need to include the memory layout information - eg, the boot log,
and /proc/iomem. Also are you using sparsemem? If so, how is it
configured?
next prev parent reply other threads:[~2011-05-11 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTimLd-qY-OeKqnf2EoTfvAHWQZVchw@mail.gmail.com>
2011-05-04 10:16 ` Fwd: [ARM]crash on 2.6.35.11 naveen yadav
2011-05-11 19:36 ` Russell King - ARM Linux [this message]
[not found] ` <BANLkTi=xz4w3p4bc5T4-YvkC3tYdwKhWGA@mail.gmail.com>
[not found] ` <BANLkTik17MGwWwFb=CzBduFy9Mn-Ze+ptA@mail.gmail.com>
2011-05-04 14:21 ` Catalin Marinas
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=20110511193602.GK5315@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).