From: Tony Lindgren <tony@atomide.com>
To: "Markku Ahvenjärvi" <markku.ahvenjarvi@nomovok.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: am35xx memory management issues
Date: Wed, 25 Nov 2015 10:37:09 -0800 [thread overview]
Message-ID: <20151125183709.GL2517@atomide.com> (raw)
In-Reply-To: <56546CAD.4060007@nomovok.com>
* Markku Ahvenjärvi <markku.ahvenjarvi@nomovok.com> [151124 05:57]:
> On 13.11.2015 15:05, Markku Ahvenjärvi wrote:
> > On 12.11.2015 19:06, Tony Lindgren wrote:
> >>
> >> Also please check if leaving out CONFIG_SMP_ON_UP affects things.
> >
> > Alright, will do.
>
> We've been testing omap2plus defconfig without other omaps and without CONFIG_SMP_ON_UP. So far we haven't seen any panics, but I've had only a few units testing it.
OK
> Meanwhile we've been testing our custom board with a configuration that is quite close to omap2plus, including other omaps and CONFIG_SMP_ON_UP. We've had couple of panics, so it seems that these doesn't affect the problem. We had 15 units running stress-ng and it took ~8 days until we saw first panic, so if omap2plus is affected it is quite rare.
Hmm so to confirm.. Is omap2plus_defconfig stable on all boards including your custom
board?
> Any other suggestions?
Maybe provide output of what changes make the problem happen with your custom
.config if you have not already done:
$ make savedefconfig
$ cp defconfig arch/arm/configs/omap2plus_defconfig
$ git diff
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: am35xx memory management issues
Date: Wed, 25 Nov 2015 10:37:09 -0800 [thread overview]
Message-ID: <20151125183709.GL2517@atomide.com> (raw)
In-Reply-To: <56546CAD.4060007@nomovok.com>
* Markku Ahvenj?rvi <markku.ahvenjarvi@nomovok.com> [151124 05:57]:
> On 13.11.2015 15:05, Markku Ahvenj?rvi wrote:
> > On 12.11.2015 19:06, Tony Lindgren wrote:
> >>
> >> Also please check if leaving out CONFIG_SMP_ON_UP affects things.
> >
> > Alright, will do.
>
> We've been testing omap2plus defconfig without other omaps and without CONFIG_SMP_ON_UP. So far we haven't seen any panics, but I've had only a few units testing it.
OK
> Meanwhile we've been testing our custom board with a configuration that is quite close to omap2plus, including other omaps and CONFIG_SMP_ON_UP. We've had couple of panics, so it seems that these doesn't affect the problem. We had 15 units running stress-ng and it took ~8 days until we saw first panic, so if omap2plus is affected it is quite rare.
Hmm so to confirm.. Is omap2plus_defconfig stable on all boards including your custom
board?
> Any other suggestions?
Maybe provide output of what changes make the problem happen with your custom
.config if you have not already done:
$ make savedefconfig
$ cp defconfig arch/arm/configs/omap2plus_defconfig
$ git diff
Regards,
Tony
next prev parent reply other threads:[~2015-11-25 18:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5644AD53.3020303@nomovok.com>
2015-11-12 17:06 ` am35xx memory management issues Tony Lindgren
2015-11-12 17:06 ` Tony Lindgren
2015-11-13 13:05 ` Markku Ahvenjärvi
2015-11-13 13:05 ` Markku Ahvenjärvi
2015-11-24 13:57 ` Markku Ahvenjärvi
2015-11-24 13:57 ` Markku Ahvenjärvi
2015-11-25 18:37 ` Tony Lindgren [this message]
2015-11-25 18:37 ` Tony Lindgren
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=20151125183709.GL2517@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=markku.ahvenjarvi@nomovok.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.