From: Mike Galbraith <efault@gmx.de>
To: Marton Balint <cus@fazekas.hu>
Cc: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Andreas Mohr <andi@lisas.de>,
linux-kernel@vger.kernel.org
Subject: Re: CPU scheduler weirdness?
Date: Fri, 04 Sep 2009 08:26:01 +0200 [thread overview]
Message-ID: <1252045561.7005.7.camel@marge.simson.net> (raw)
In-Reply-To: <alpine.LNX.2.00.0909032350580.20701@cinke.fazekas.hu>
On Thu, 2009-09-03 at 23:57 +0200, Marton Balint wrote:
> >> In the meantime, I updated my original C program and also created a kernel
> >> module (schedtest_mod.c) which causes the same scheduling problems as the
> >> kernel module of my TV card. The kernel module is a skeleton of the
> >> infrared sensor polling code in cx88-input.c. It uses
> >> schedule_delayed_work, this seems to cause the problem. The C program
> >> (schedtest.c) is also updated, it now detects the number of CPU cores, from
> >> now, what you can set as a command line parameter is the CPU core number,
> >> on which the schedtest processes will not quit. (previously this was always
> >> the last core).
> >>
> >> So to reproduce the bug on a dual core system, compile and insert the
> >> kernel module (schedtest_mod.c). Then check dmesg, it should contain on
> >> which CPU core is the delayed_work running. You should use the CPU core id
> >> of the _other_ CPU core as a command line parameter to the updated
> >> schedtest program.
> >>
> >> And by the way, thank you guys for the help so far, hopefully we'll get to
> >> the bottom of this :)
> >
> > I reproduced the bug with the previously provided kernel module and C program
> > on a different computer (it's a laptop with a core2 duo P8400 CPU), and also
> > bisected the bug to this commit:
> >
> > sched: fine-tune SD_MC_INIT:
> > 14800984706bf6936bbec5187f736e928be5c218
> >
> > If I add again the removed SD_BALANCE_NEWIDLE to flags, then everything works
> > as expected. So what would be the correct fix for this bug? Revert the patch?
> > Or just add SD_BALANCE_NEWIDLE to flags?
Or, figure out what's going weird with that module loaded.
> Ingo, Peter, could any of you guys have a look at the commit that caused
> this bug? Is it OK to revert it? Or a fix somewhere else is necessary? I'm
> pushing this because I hope that this bug will get fixed in the upcoming
> stable kernel...
Where does your schedtest.c and schedtest_mod.c live?
-Mike
next prev parent reply other threads:[~2009-09-04 6:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 0:58 CPU scheduler weirdness? Marton Balint
2009-08-13 8:42 ` Andreas Mohr
2009-08-13 15:39 ` Marton Balint
2009-08-13 15:58 ` Andreas Mohr
2009-08-18 19:49 ` Marton Balint
2009-08-19 7:04 ` Peter Zijlstra
2009-08-19 12:01 ` Marton Balint
2009-08-19 12:10 ` Peter Zijlstra
2009-08-19 12:34 ` Marton Balint
2009-08-19 18:42 ` Peter Zijlstra
2009-08-20 0:10 ` Marton Balint
2009-08-20 10:56 ` Ingo Molnar
2009-08-20 16:56 ` Marton Balint
2009-08-29 14:15 ` Marton Balint
2009-09-03 21:57 ` Marton Balint
2009-09-04 6:26 ` Mike Galbraith [this message]
2009-09-04 7:53 ` Marton Balint
2009-09-04 12:26 ` Mike Galbraith
2009-09-04 8:40 ` Peter Zijlstra
2009-09-04 12:40 ` Ingo Molnar
2009-09-04 15:31 ` Marton Balint
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=1252045561.7005.7.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=andi@lisas.de \
--cc=cus@fazekas.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.