linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sami Liedes <sami.liedes@iki.fi>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Bug 43227] New: BUG: Bad page state in process wcg_gfam_6.11_i
Date: Sat, 12 May 2012 01:23:41 +0300	[thread overview]
Message-ID: <20120511222341.GD7387@sli.dy.fi> (raw)
In-Reply-To: <20120511133234.6130b69a.akpm@linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 981 bytes --]

On Fri, May 11, 2012 at 01:32:34PM -0700, Andrew Morton wrote:
> Sure, thanks, that might turn something up. 
> Documentation/SubmitChecklist recommends 
> 
> : 12: Has been tested with CONFIG_PREEMPT, CONFIG_DEBUG_PREEMPT,
> :     CONFIG_DEBUG_SLAB, CONFIG_DEBUG_PAGEALLOC, CONFIG_DEBUG_MUTEXES,
> :     CONFIG_DEBUG_SPINLOCK, CONFIG_DEBUG_ATOMIC_SLEEP, CONFIG_PROVE_RCU
> :     and CONFIG_DEBUG_OBJECTS_RCU_HEAD all simultaneously enabled.
> 
> although that list might be a bit out of date; it certainly should
> include CONFIG_DEBUG_VM!

I wonder if there's somewhere a recommended list of generally most
useful debug options that only have a moderate performance impact? I'd
be happy to use a set of useful debug flags that generally impacts
performance by, say, <10%, on the computers I use for my everyday work
to help catch bugs. But it's sometimes quite hard to assess the impact
of different Kernel hacking options from just the description...

	Sami

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2012-05-11 22:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-43227-27@https.bugzilla.kernel.org/>
2012-05-11 19:59 ` [Bug 43227] New: BUG: Bad page state in process wcg_gfam_6.11_i Andrew Morton
2012-05-11 20:02   ` Sami Liedes
2012-05-11 20:32     ` Andrew Morton
2012-05-11 20:59       ` Dave Jones
2012-05-11 22:23       ` Sami Liedes [this message]
2012-05-14  0:25         ` Dave Jones
2012-05-11 20:06   ` Dave Jones
2012-05-11 20:10     ` Andrew Morton
2012-05-11 22:14       ` Sami Liedes
2012-05-11 21:30   ` Hugh Dickins
2012-05-11 22:56     ` Sami Liedes
2012-05-14  0:30     ` Dave Jones

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=20120511222341.GD7387@sli.dy.fi \
    --to=sami.liedes@iki.fi \
    --cc=akpm@linux-foundation.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-mm@kvack.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).