From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: Rescheduling interrupts
Date: Tue, 22 Jan 2008 14:55:14 +0200 [thread overview]
Message-ID: <200801221455.16814.caglar@pardus.org.tr> (raw)
In-Reply-To: <20080122105741.GG21149@elte.hu>
Hi;
22 Oca 2008 Sal tarihinde, Ingo Molnar şunları yazmıştı:
> * S.Çağlar Onur <caglar@pardus.org.tr> wrote:
>
> > Top causes for wakeups:
> > 59,9% (238,4) <kernel IPI> : Rescheduling interrupts
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > 14,7% ( 58,6) amarokapp : schedule_timeout (process_timeout)
>
> hm, would be nice to figure out what causes these IPIs. Could you stick
> something like this into arch/x86/kernel/smp_32.c's
> smp_send_reschedule() function [this is the function that generates the
> IPI]:
>
> static void native_smp_send_reschedule(int cpu)
> {
> WARN_ON(cpu_is_offline(cpu));
> send_IPI_mask(cpumask_of_cpu(cpu), RESCHEDULE_VECTOR);
> if (panic_timeout > 0) {
> panic_timeout--;
> printk("IPI from task %s:%d on CPU#%d:\n",
> current->comm, current->pid, cpu);
> dump_stack();
> }
> }
>
> NOTE: if you run an SMP kernel then first remove these two lines from
> kernel/printk.c:
>
> if (!oops_in_progress && waitqueue_active(&log_wait))
> wake_up_interruptible(&log_wait);
>
> otherwise you'll get lockups. (the IPI is sent while holding the
> runqueue lock, so the printks will lock up)
>
> then wait for the bad condition to occur on your system and generate a
> stream of ~10 backtraces, via:
>
> echo 10 > /proc/sys/kernel/panic
>
> you should be getting 10 immediate backtraces - please send them to us.
> The backtraces should show the place that generates the wakeups. [turn
> on CONFIG_FRAME_POINTERS=y to get high quality backtraces.]
>
> If you do _not_ get 10 immediate backtraces, then something in the
> system is generating such IPIs outside of the scheduler's control. That
> would suggest some other sort of borkage.
>
> Ingo
I grabbed the logs two times to make sure to catch needed info. 1st [1] one is generated while "Rescheduling interrupts" wakeups ~200 times and 2nd one generated for ~350 wakeups.
[1] http://cekirdek.pardus.org.tr/~caglar/dmesg.1st
[2] http://cekirdek.pardus.org.tr/~caglar/dmesg.2nd
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
next prev parent reply other threads:[~2008-01-22 12:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 23:19 Rescheduling interrupts S.Çağlar Onur
2008-01-22 10:57 ` Ingo Molnar
2008-01-22 12:55 ` S.Çağlar Onur [this message]
2008-01-22 15:23 ` Ingo Molnar
2008-01-22 15:37 ` Ingo Molnar
2008-01-22 16:00 ` S.Çağlar Onur
2008-01-22 15:55 ` S.Çağlar Onur
2008-01-22 16:05 ` Ingo Molnar
2008-01-22 16:11 ` S.Çağlar Onur
2008-01-22 16:22 ` S.Çağlar Onur
2008-01-22 17:03 ` Matt Mackall
2008-01-22 19:27 ` Ingo Molnar
[not found] ` <p73fxwoncs4.fsf@crumb.suse.de>
2008-01-23 15:52 ` Matt Mackall
2008-05-13 18:03 ` Vegard Nossum
2008-05-13 19:04 ` Vegard Nossum
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=200801221455.16814.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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