From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
gregkh@suse.de, linux-kernel@vger.kernel.org,
cpufreq@vger.kernel.org
Subject: Re: [BUG] 2.6.29.1 debugobjects warning
Date: Fri, 24 Apr 2009 08:49:37 +0200 [thread overview]
Message-ID: <20090424064937.GD21739@elte.hu> (raw)
In-Reply-To: <20090423164638.3b5769c6.akpm@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> wrote:
> On Thu, 23 Apr 2009 10:00:02 -0400
> Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> wrote:
>
> > ODEBUG: init active object type: timer_list
> It seems to be complaining that cpufreq_governor_dbs() is running
> init_timer() against a timer which has already been initialised
> once.
Not just already initialized - but also active. There's these states
for an object:
ODEBUG_STATE_NONE,
ODEBUG_STATE_INIT,
ODEBUG_STATE_INACTIVE,
ODEBUG_STATE_ACTIVE,
ODEBUG_STATE_DESTROYED,
So the 'init active object type' warning above suggests that an
init_timer() has been done on an already running timer. If true then
that is a bad bug - can corrupt timer state, etc.
Thomas, do you agree?
Ingo
next prev parent reply other threads:[~2009-04-24 6:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 14:00 [BUG] 2.6.29.1 debugobjects warning Mathieu Desnoyers
2009-04-23 23:46 ` Andrew Morton
2009-04-24 4:34 ` [PATCH -stable] cpufreq fix timer teardown in conservative governor (2.6.28.x, 2.6.29.1) Mathieu Desnoyers
2009-04-28 12:57 ` Mathieu Desnoyers
2009-04-24 4:35 ` [PATCH] cpufreq fix timer teardown in conservative governor (2.6.30-rc2) Mathieu Desnoyers
2009-04-24 6:18 ` Len Brown
2009-04-24 16:12 ` Mathieu Desnoyers
2009-04-26 14:47 ` Henrique de Moraes Holschuh
2009-04-26 16:31 ` Mathieu Desnoyers
2009-04-24 4:38 ` [PATCH] cpufreq fix timer teardown in ondemand governor (2.6.28.x, 2.6.29.1, 2.6.30-rc2) Mathieu Desnoyers
2009-04-28 13:00 ` Mathieu Desnoyers
2009-04-24 6:49 ` Ingo Molnar [this message]
2009-04-24 15:07 ` [BUG] 2.6.29.1 debugobjects warning Mathieu Desnoyers
2009-04-27 11:30 ` Thomas Gleixner
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=20090424064937.GD21739@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=cpufreq@vger.kernel.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox