From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: Bad Page dump (help)
Date: Thu, 31 Jul 2014 08:43:44 -0500 [thread overview]
Message-ID: <20140731134344.GA19512@saruman.home> (raw)
In-Reply-To: <53D9E10F.6040408@xenomai.org>
Hi,
On Thu, Jul 31, 2014 at 08:24:15AM +0200, Gilles Chanteperdrix wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 07/29/2014 09:07 PM, Felipe Balbi wrote:
> > Hi Russell,
> >
> > I'm bringing up a new board on today's linux-next but I'm having a bunch
> > of bad_page() calls due to _mapcount not being zero (full logs
> > attached). What could cause that ? Any hints on how to debug ? It's as
> > if page_mapcount_reset() wasn't called for the pages which are causing
> > issues.
>
> FWIW, the same issue appeared on a Cogent CSB637 board (the last board
> I use not using DT) in between 3.13 and 3.14. I ran a bisect and found
> that reverting the following commit:
>
> commit 84f452b1e8fc73ac0e31254c66e3e2260ce5263d
> Author: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Date: Sun Jun 30 00:28:46 2013 -0400
>
> ARM: mm: Remove bootmem code and switch to NO_BOOTMEM
>
> Now with dma_mask series merged and max*pfn has consistent meaning on ARM
> as rest of the arch's thanks to RMK's mega series, lets switch ARM code
> to NO_BOOTMEM. With NO_BOOTMEM change, now we use memblock allocator to
> reserve space for crash kernel to have one less dependency with nobootmem
> allocator wrapper.
>
> Tested with both flat memory and sparse (faked) memory models with highmem
> enabled.
Thanks I'll give this a shot.
> Seemed to make the issue disappear. I later found out that changing the
> kernel options also made the issue disappear.
which kernel options did you change ?
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140731/53edcf6c/attachment.sig>
next prev parent reply other threads:[~2014-07-31 13:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 19:07 Bad Page dump (help) Felipe Balbi
2014-07-29 19:55 ` Russell King - ARM Linux
2014-07-29 20:17 ` Felipe Balbi
2014-07-31 14:53 ` Russell King - ARM Linux
2014-07-31 15:30 ` Felipe Balbi
2014-07-31 23:04 ` Felipe Balbi
2014-07-31 6:24 ` Gilles Chanteperdrix
2014-07-31 13:43 ` Felipe Balbi [this message]
2014-07-31 14:23 ` Felipe Balbi
2014-07-31 14:00 ` Russell King - ARM Linux
2014-07-31 17:42 ` Gilles Chanteperdrix
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=20140731134344.GA19512@saruman.home \
--to=balbi@ti.com \
--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).