On Jan 21, 2008 6:18 PM, Srivatsa Vaddagiri wrote:
> On Sun, Jan 20, 2008 at 09:03:38AM +0530, Dhaval Giani wrote:
> > > 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
On Sun, Jan 20, 2008 at 09:03:38AM +0530, Dhaval Giani wrote:
> > 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
On Sun, Jan 20, 2008 at 09:03:38AM +0530, Dhaval Giani wrote:
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
On Jan 21, 2008 6:18 PM, Srivatsa Vaddagiri wrote:
On Sun, Jan 20, 2008 at 09:03:38AM +0530, Dhaval Giani wrote:
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
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
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
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
While looking
Hello,
I have BOINC running in the background with niceness 19.
With a 2.6.22 kernel, only idle cpu cycles get assigned to this process, as
expected.
But with the 2.6.24 kernel, the BOINC process gets at least about half of
all CPU cycles, even if there's another process (owned by another user)
Hello,
I have BOINC running in the background with niceness 19.
With a 2.6.22 kernel, only idle cpu cycles get assigned to this process, as
expected.
But with the 2.6.24 kernel, the BOINC process gets at least about half of
all CPU cycles, even if there's another process (owned by another user)
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
While looking
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):
$
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
12 matches
Mail list logo
