Re: [BUG] 2.6.29.1 debugobjects warning

[Ingo Molnar]

* Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:

> On Thu, 23 Apr 2009 10:00:02 -0400
> Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/