From: Andrew Morton <akpm@osdl.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: hch@infradead.org, anton@samba.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpu hotplug fix
Date: Sat, 20 Mar 2004 15:12:30 -0800 [thread overview]
Message-ID: <20040320151230.7527914a.akpm@osdl.org> (raw)
In-Reply-To: <1079780351.18972.48.camel@bach>
Rusty Russell <rusty@rustcorp.com.au> wrote:
>
> Name: Remove Strange start_cpu_timer Code
> Status: Untested
>
> Why is start_cpu_timer checking for fn being NULL? And why isn't
> every CPU's reap_timer initialized in cpucache_init (which is an
> __init function).
>
> Clean up this mess by just starting the timer in start_cpu_timer.
oy.
Program received signal SIGTRAP, Trace/breakpoint trap.
0xc0128e32 in add_timer_on (timer=0xc120d880, cpu=1) at kernel/timer.c:225
225 BUG_ON(timer_pending(timer) || !timer->function);
(gdb) bt
#0 0xc0128e32 in add_timer_on (timer=0xc120d880, cpu=1) at kernel/timer.c:225
#1 0xc01446b5 in cpuup_callback (nfb=0xc0472800, action=4, hcpu=0x1) at mm/slab.c:595
#2 0xc012dc67 in notifier_call_chain (n=0x4, val=2, v=0x1) at kernel/sys.c:169
#3 0xc0134b63 in cpu_up (cpu=1) at kernel/cpu.c:192
#4 0xc05e0650 in smp_init () at init/main.c:364
#5 0xc0103161 in init (unused=0x0) at init/main.c:626
#6 0xc010728d in kernel_thread_helper () at arch/i386/kernel/process.c:246
(gdb) p timer->function
$1 = (void (*)(long unsigned int)) 0
I'll simply mark start_cpu_timer() as __devinit.
next prev parent reply other threads:[~2004-03-20 23:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-20 6:36 Anton Blanchard
2004-03-20 7:40 ` Christoph Hellwig
2004-03-20 10:59 ` Rusty Russell
2004-03-20 23:12 ` Andrew Morton [this message]
2004-03-22 6:36 ` Rusty Russell
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=20040320151230.7527914a.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=anton@samba.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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
Powered by JetHome