Subject: Re: 2.6.15-rc2-mm1: kernel BUG at kernel/timer.c:213
From: Thomas Gleixner <tglx@linutronix.de>
Reply-To: tglx@linutronix.de
To: Bernhard Rosenkraenzer <bero@arklinux.org>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <200511271951.55262.bero@arklinux.org>
References: <200511271951.55262.bero@arklinux.org>
Content-Type: text/plain
Organization: linutronix
Date: Sun, 27 Nov 2005 20:47:48 +0100
Message-Id: <1133120868.32542.329.camel@tglx.tec.linutronix.de>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1004
Lines: 26

On Sun, 2005-11-27 at 19:51 +0100, Bernhard Rosenkraenzer wrote:
> This happens when modprobe-ing rt2500 (http://rt2400.sf.net/) -- since the 
> same driver works perfectly on older kernels, the timer rework may be at 
> fault (didn't have a lot of time to look into this yet)

------------[ cut here ]------------
> kernel BUG at kernel/timer.c:213!
> 
        BUG_ON(!timer->function);

The caller of __mod_timer did not fill in the function member.

I decoded the conglomeration of characters which seems to be the driver
source - shudder - and actually the init code of the driver initializes
the TuningTimer after register_netdev, which leads to a race with the
hotplug code. "Working perfectly" on older kernels is just by chance not
by design.

	tglx


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/