All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: Witold Baryluk <baryluk@smp.if.uj.edu.pl>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Stanislaw Gruszka <sgruszka@redhat.com>,
	Marcin Slusarz <marcin.slusarz@gmail.com>
Subject: Re: ODEBUG: selftest warnings failed 4 != 5 (WARNING: at lib/debugobjects.c:908 check_results.constprop.9)
Date: Fri, 2 Mar 2012 13:17:56 -0800	[thread overview]
Message-ID: <20120302131756.32e7f788.akpm@linux-foundation.org> (raw)
In-Reply-To: <CAFLxGvy0yWe2utG-+vFw4BhfH-i0vfjNy3k6kUsxkN7M4BSWQg@mail.gmail.com>

On Fri, 2 Mar 2012 00:18:37 +0100
richard -rw- weinberger <richard.weinberger@gmail.com> wrote:

> On Sat, Feb 18, 2012 at 3:35 AM, Witold Baryluk
> <baryluk@smp.if.uj.edu.pl> wrote:
> > Hello everybody,
> >
> > I recently enabled a CONFIG_DEBUG_OBJECTS kconfig option, and this is what I got when booting
> >
> > ...
> > [ __ __0.000000] Linux version 3.3.0-rc3-t43-devel-smp-00278-g4903062-dirty (baryluk@sredniczarny) (gcc version 4.6.2 (Debian 4.6.2-14) ) #27 SMP Fri Feb 17 20:13:29 CE
> > ...
> > ...
> > ...
> > [ __ __0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
> > [ __ __0.000000] Hierarchical RCU implementation.
> > [ __ __0.000000] __RCU debugfs-based tracing is enabled.
> > [ __ __0.000000] __RCU lockdep checking is enabled.
> > [ __ __0.000000] NR_IRQS:2304 nr_irqs:256 16
> > [ __ __0.000000] CPU 0 irqstacks, hard=f5408000 soft=f540a000
> > [ __ __0.000000] Extended CMOS year: 2000
> > [ __ __0.000000] Console: colour VGA+ 80x25
> > [ __ __0.000000] console [tty0] enabled
> > [ __ __0.000000] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
> > [ __ __0.000000] ... MAX_LOCKDEP_SUBCLASSES: __8
> > [ __ __0.000000] ... MAX_LOCK_DEPTH: __ __ __ __ __48
> > [ __ __0.000000] ... MAX_LOCKDEP_KEYS: __ __ __ __8191
> > [ __ __0.000000] ... CLASSHASH_SIZE: __ __ __ __ __4096
> > [ __ __0.000000] ... MAX_LOCKDEP_ENTRIES: __ __ 16384
> > [ __ __0.000000] ... MAX_LOCKDEP_CHAINS: __ __ __32768
> > [ __ __0.000000] ... CHAINHASH_SIZE: __ __ __ __ __16384
> > [ __ __0.000000] __memory used by lock dependency info: 3823 kB
> > [ __ __0.000000] __per task-struct memory footprint: 1920 bytes
> > [ __ __0.000000] ------------------------
> > [ __ __0.000000] | Locking API testsuite:
> > ...
> > ...
> > [ __ __0.000000] -------------------------------------------------------
> > [ __ __0.000000] Good, all 218 testcases passed! |
> > [ __ __0.000000] ---------------------------------
> > [ __ __0.000000] ODEBUG: 14 of 14 active objects replaced
> > [ __ __0.000000] ------------[ cut here ]------------
> > [ __ __0.000000] WARNING: at lib/debugobjects.c:908 check_results.constprop.9+0x11c/0x140()
> > [ __ __0.000000] Hardware name: 2669UYD
> > [ __ __0.000000] ODEBUG: selftest warnings failed 4 != 5
> 
> This warning is still present.
> Andrew?

Dunno, sorry.  There are only two patches to bisect through - try
reverting b84d435cc228e ("debugobjects: Extend to assert that an object
is initialized") and then feac18dda25134 ("debugobjects: Be smarter
about static objects")?  

  reply	other threads:[~2012-03-02 21:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-18  2:35 ODEBUG: selftest warnings failed 4 != 5 (WARNING: at lib/debugobjects.c:908 check_results.constprop.9) Witold Baryluk
2012-03-01 23:18 ` richard -rw- weinberger
2012-03-02 21:17   ` Andrew Morton [this message]
2012-03-02 21:20     ` Stephen Boyd
2012-03-02 21:23       ` Andrew Morton

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=20120302131756.32e7f788.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=baryluk@smp.if.uj.edu.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin.slusarz@gmail.com \
    --cc=richard.weinberger@gmail.com \
    --cc=sboyd@codeaurora.org \
    --cc=sgruszka@redhat.com \
    --cc=tglx@linutronix.de \
    /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.