All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: CF Adad <cfadad@rocketmail.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Please help! AM35xx mm/slab.c BUG
Date: Wed, 6 Jun 2012 00:10:25 -0700	[thread overview]
Message-ID: <20120606071024.GP12766@atomide.com> (raw)
In-Reply-To: <CAMQu2gw2bGNwot_xVPdAsYjZChzzNib2USg8Ci+W5aLbenPnqA@mail.gmail.com>

* Shilimkar, Santosh <santosh.shilimkar@ti.com> [120605 23:41]:
> 
> I don't know the AMXX architecture that well but looking at the
> crash-log, am not sure GPMC should play in role here.
> What I think is, it is mostly memory corruption and can be caused by
> many reasons as Tony outlined.

Bad GPMC timings can cause corruption on the smsc fifo, which can
cause random oopses especially with nfsroot.

I was seeing that on my zoom3 with nfsroot with bad muxing for GPMC
until we applied bce492c0 (ARM: OMAP2+: UART: Fix incorrect population of
default uart pads). That's easy to test by leaving out GPMC.
 
> To ensure that, your memory is in good state, can you run memtester
> for long duration and see that you
> are not getting any memory failures. Try to give the maximum memory
> size as a an input to memtester.

Yes and that should be left running for a few weeks on a group of
devices to verify things work once you think you have all the issues
fixed.

Regards,

Tony

 
> You can download one from [1]
> 
> Regards
> Santosh
> [1] http://pyropus.ca/software/memtester/

  parent reply	other threads:[~2012-06-06  7:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05  6:37 Please help! AM35xx mm/slab.c BUG CF Adad
2012-06-05  7:08 ` Tony Lindgren
2012-06-05 16:29   ` CF Adad
2012-06-06  6:14     ` CF Adad
2012-06-06  6:36       ` Shilimkar, Santosh
2012-06-06  7:08         ` CF Adad
2012-06-06  7:10         ` Tony Lindgren [this message]
2012-06-06  7:51           ` CF Adad
2012-06-06  8:41             ` Tony Lindgren
2012-06-06 10:37               ` Jarkko Nikula
2012-06-06 15:53                 ` CF Adad
2012-06-07  9:32             ` Mohammed, Afzal
2012-06-07 19:50               ` CF Adad
2012-06-12 11:14                 ` Mohammed, Afzal
2012-06-12 15:27                   ` CF Adad
2012-06-14 17:28                   ` CF Adad
2012-06-14 19:10                     ` jean-philippe francois
2012-06-15  4:23                       ` CF Adad
2012-06-19  1:29                   ` CF Adad
2012-06-19  6:29                     ` Mohammed, Afzal

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=20120606071024.GP12766@atomide.com \
    --to=tony@atomide.com \
    --cc=cfadad@rocketmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=santosh.shilimkar@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 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.