LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Dhaval Giani <dhaval@linux.vnet.ibm.com>
To: dAniel hAhler <dhahler@googlemail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: Regression with idle cpu cycle handling in 2.6.24 (compared to 2.6.22)
Date: Sun, 20 Jan 2008 09:33:39 +0530 [thread overview]
Message-ID: <20080120040339.GB16692@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080120033337.GA8277@linux.vnet.ibm.com>
On Sun, Jan 20, 2008 at 09:03:38AM +0530, Dhaval Giani wrote:
> On Sat, Jan 19, 2008 at 03:52:44PM +0100, dAniel hAhler wrote:
> > Hello,
> >
> > I've now found the reason and a workaround for this. Apparently, it's
> > related to CONFIG_FAIR_USER_SCHED and can be worked around by
> > assigning a really small value to the boinc users cpu_share (125 is
> > the uid of "boinc"):
> > $ echo 2 | sudo tee /sys/kernel/uids/125/cpu_share
> >
>
> Correct, that is the way to go about it.
>
> > While looking around, I've found the following patch, which seems to
> > address this:
> > http://www.ussg.iu.edu/hypermail/linux/kernel/0710.3/3849.html
> >
> > It has been posted here, but without any response.
> >
> > btw: writing 1 into "cpu_share" totally locks up the computer!
> >
>
> Can you please provide some more details. Can you go into another
> console (try ctrl-alt-f1) and try to reproduce the issue there. Could
> you take a photo of the oops/panic and upload it somewhere so that we
> can see it?
>
I've not been able to reproduce this problem on my system here. Do you
try to change the cpu_share of the current user?
--
regards,
Dhaval
next prev parent reply other threads:[~2008-01-20 4:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 14:05 dAniel hAhler
2008-01-19 14:52 ` dAniel hAhler
2008-01-20 3:33 ` Dhaval Giani
2008-01-20 4:03 ` Dhaval Giani [this message]
2008-01-21 17:18 ` Srivatsa Vaddagiri
2008-01-22 1:59 ` dAniel hAhler
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=20080120040339.GB16692@linux.vnet.ibm.com \
--to=dhaval@linux.vnet.ibm.com \
--cc=dhahler@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vatsa@linux.vnet.ibm.com \
--subject='Re: Regression with idle cpu cycle handling in 2.6.24 (compared to 2.6.22)' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).