From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Sebastien Jan <s-jan@ti.com>, Bryan Wu <bryan.wu@canonical.com>
Cc: Paul Walmsley <paul@pwsan.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 22:52:17 +0530 [thread overview]
Message-ID: <36befcf1947882da51ace32cbfb0b922@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimmnUq19qmBgAetA-+pkrCxwwfwA-kaBtAOqVeu@mail.gmail.com>
Seb,
> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> owner@vger.kernel.org] On Behalf Of Jan, Sebastien
> Sent: Friday, January 14, 2011 10:41 PM
> To: Bryan Wu
> Cc: Paul Walmsley; linux-omap@vger.kernel.org; Ricardo Salveti de
> Araujo
> Subject: Re: Passing mem=1G to kernel on Panda, system is unstable.
>
> On Fri, Jan 14, 2011 at 11:09 AM, Bryan Wu <bryan.wu@canonical.com>
> wrote:
> > On Fri, Jan 14, 2011 at 1:41 PM, Paul Walmsley <paul@pwsan.com>
> wrote:
> >> On Thu, 13 Jan 2011, Bryan Wu wrote:
> >>
> >>> On Thu, Jan 13, 2011 at 7:50 AM, Paul Walmsley <paul@pwsan.com>
> wrote:
> >>> > On Wed, 12 Jan 2011, Bryan Wu wrote:
> >>> >
> >>> > Does the problem also happen if you boot with 'nosmp' on the
> kernel
> >>> > command line?
> >>>
> >>> Yeah, I think so, since Sebastien reported that 'nosmp' doesn't
> work either.
> >>
> >> Will try to find time to give this a shot. You might want to try
> a build
> >> without CONFIG_SMP set to see if it helps.
> >>
> > Thanks a lot, man. Sebastien and I will try to disable CONFIG_SMP
> with
> > mainline kernel on Panda.
>
> I just tested with the 2.6.37 mainline kernel and Bryan config, and
> can reproduce the issue with CONFIG_SMP disabled.
Can you try the patch I sent on the list as well ?
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-01-14 17:22 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 [this message]
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
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=36befcf1947882da51ace32cbfb0b922@mail.gmail.com \
--to=santosh.shilimkar@ti.com \
--cc=bryan.wu@canonical.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=ricardo.salveti@canonical.com \
--cc=s-jan@ti.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