Re: [Bug 43227] New: BUG: Bad page state in process wcg_gfam_6.11_i

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


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: signature.asc
Description: Digital signature


[Site Home]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Tools]     [DDR & Rambus]     [Asterisk Internet PBX]     [Linux API]     [Monitors]

Add to Google Google PageRank Checking tool