Hi Ingo,
On Wed, Sep 11, 2013 at 07:18:14PM +0400, Alexey Vlasov wrote:
> On Thu, Sep 05, 2013 at 01:12:52PM +0200, Ingo Molnar wrote:
> >
> > Could you try the latest -tip tree at:
> >
> >git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> >
> > In particular this fix:
> >
> >
Hi Ingo,
On Wed, Sep 11, 2013 at 07:18:14PM +0400, Alexey Vlasov wrote:
On Thu, Sep 05, 2013 at 01:12:52PM +0200, Ingo Molnar wrote:
Could you try the latest -tip tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
In particular this fix:
5a8e01f8fa51
On Thu, Sep 05, 2013 at 01:12:52PM +0200, Ingo Molnar wrote:
>
> Could you try the latest -tip tree at:
>
>git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
>
> In particular this fix:
>
>5a8e01f8fa51 sched/cputime: Do not scale when utime == 0
>
> Could perhaps fix the
On Thu, Sep 05, 2013 at 01:12:52PM +0200, Ingo Molnar wrote:
Could you try the latest -tip tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
In particular this fix:
5a8e01f8fa51 sched/cputime: Do not scale when utime == 0
Could perhaps fix the phantom CPU
* Alexey Vlasov wrote:
> On Sun, Aug 25, 2013 at 04:28:37PM +0200, Peter Zijlstra wrote:
>
> > and a function (or function-graph)
> > trace for when this happens?
>
> Unfortunately I could not make trace.
> First when migration threads start to eat CPUs and when I turn on trace:
> # echo
* Alexey Vlasov ren...@renton.name wrote:
On Sun, Aug 25, 2013 at 04:28:37PM +0200, Peter Zijlstra wrote:
and a function (or function-graph)
trace for when this happens?
Unfortunately I could not make trace.
First when migration threads start to eat CPUs and when I turn on trace:
#
On Sun, Aug 25, 2013 at 04:28:37PM +0200, Peter Zijlstra wrote:
> and a function (or function-graph)
> trace for when this happens?
Unfortunately I could not make trace.
First when migration threads start to eat CPUs and when I turn on trace:
# echo function > current_tracer
# echo 1 >
On Sun, Aug 25, 2013 at 04:28:37PM +0200, Peter Zijlstra wrote:
and a function (or function-graph)
trace for when this happens?
Unfortunately I could not make trace.
First when migration threads start to eat CPUs and when I turn on trace:
# echo function current_tracer
# echo 1 tracing_on
Hi Peter,
On Sun, Aug 25, 2013 at 04:28:37PM +0200, Peter Zijlstra wrote:
>
> Gargh.. I've never seen anything like that. Nor ever had a report like
> this. Is there anything in particular one can do to try and reproduce
> this?
I don't know how to reproduce it. This happens by itself and only
(CCs)
On Thu, 2013-08-22 at 19:00 +0400, Alexey Vlasov wrote:
> Hi,
>
> Beginning from 3.7 including 3.10 kernel, I noticed that from time to
> time all CPUs turn out to be busy 100% and at the moment websites of my
> clients work slowly or don’t work at all.
>
> top screen:
>
(CCs)
On Thu, 2013-08-22 at 19:00 +0400, Alexey Vlasov wrote:
Hi,
Beginning from 3.7 including 3.10 kernel, I noticed that from time to
time all CPUs turn out to be busy 100% and at the moment websites of my
clients work slowly or don’t work at all.
top screen:
Hi Peter,
On Sun, Aug 25, 2013 at 04:28:37PM +0200, Peter Zijlstra wrote:
Gargh.. I've never seen anything like that. Nor ever had a report like
this. Is there anything in particular one can do to try and reproduce
this?
I don't know how to reproduce it. This happens by itself and only on
Hi,
Beginning from 3.7 including 3.10 kernel, I noticed that from time to
time all CPUs turn out to be busy 100% and at the moment websites of my
clients work slowly or don’t work at all.
top screen:
https://www.dropbox.com/s/psuk2cwn6exinyd/3.9.cpu_migration.jpg
All CPUs are busy with kernel
Hi,
Beginning from 3.7 including 3.10 kernel, I noticed that from time to
time all CPUs turn out to be busy 100% and at the moment websites of my
clients work slowly or don’t work at all.
top screen:
https://www.dropbox.com/s/psuk2cwn6exinyd/3.9.cpu_migration.jpg
All CPUs are busy with kernel
14 matches
Mail list logo
