From: Thomas Gleixner <tglx@linutronix.de>
To: Bernhard Rosenkraenzer <bero@arklinux.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-rc2-mm1: kernel BUG at kernel/timer.c:213
Date: Sun, 27 Nov 2005 20:47:48 +0100 [thread overview]
Message-ID: <1133120868.32542.329.camel@tglx.tec.linutronix.de> (raw)
In-Reply-To: <200511271951.55262.bero@arklinux.org>
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
prev parent reply other threads:[~2005-11-27 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-27 18:51 Bernhard Rosenkraenzer
2005-11-27 19:47 ` Thomas Gleixner [this message]
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=1133120868.32542.329.camel@tglx.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=bero@arklinux.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®