public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Bryan Wu <bryan.wu@canonical.com>,
	linux-omap@vger.kernel.org,
	Ricardo Salveti de Araujo <ricardo.salveti@canonical.com>
Subject: RE: Passing mem=1G to kernel on Panda, system is unstable.
Date: Fri, 14 Jan 2011 13:42:58 +0530	[thread overview]
Message-ID: <641ab84b6cedfd62b9b6bedeae077f1b@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin+ZjUoD9i+JxV7wW2+U6oEp42PdP5R4gdtzy=F@mail.gmail.com>

Bryan,
> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> owner@vger.kernel.org] On Behalf Of Bryan Wu
> Sent: Tuesday, January 11, 2011 10:22 PM
> To: linux-omap@vger.kernel.org; Ricardo Salveti de Araujo
> Subject: Passing mem=1G to kernel on Panda, system is unstable.
>
> Hi folks,
>
> We are trying to build kernel package or GCC natively on OMAP4 panda
> board. With the mainline 2.6.37 kernel or Ubuntu Natty 2.6.35 based
> kernel, we met same instabilities on the system when we try to use
> mem=1G on the board.
>
> Please find our bug tracker here:
> https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/633227
> and I think another bug is also related:
> https://bugs.launchpad.net/ubuntu/+source/linux-ti-
> omap4/+bug/690370.
> System will freeze at all when building GCC natively on Panda.
>
> Did any folks meet this issue? or we need more simple test case to
> catch the root cause of this issue.
>
Haven't seen this issue on my SDP with 2.6.37.
Have you enabled HIGHMEM, when tried mem = 1G on 2.6.37 ?

  parent reply	other threads:[~2011-01-14  8:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 16:52 Passing mem=1G to kernel on Panda, system is unstable Bryan Wu
2011-01-12 23:50 ` Paul Walmsley
2011-01-13  0:02   ` Bryan Wu
2011-01-14  5:41     ` Paul Walmsley
2011-01-14 10:09       ` Bryan Wu
2011-01-14 17:11         ` Jan, Sebastien
2011-01-14 17:22           ` Santosh Shilimkar
2011-01-14 17:48             ` Bryan Wu
2011-01-14 17:48             ` Jan, Sebastien
2011-01-14 18:41               ` Bryan Wu
2011-01-14 18:55                 ` Santosh Shilimkar
2011-01-14 19:06                   ` Bryan Wu
2011-01-14 20:26                     ` Bryan Wu
2011-01-14  8:12 ` Santosh Shilimkar [this message]
2011-01-14  8:56   ` Santosh Shilimkar
2011-01-14 10:14     ` Bryan Wu
2011-01-14 10:12   ` Bryan Wu
2011-01-17 18:41     ` Jan, Sebastien

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=641ab84b6cedfd62b9b6bedeae077f1b@mail.gmail.com \
    --to=santosh.shilimkar@ti.com \
    --cc=bryan.wu@canonical.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=ricardo.salveti@canonical.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