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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
