From: Frederic Weisbecker <fweisbec@gmail.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org
Subject: Re: [sched next] overflowed cpu time for kernel threads in /proc/PID/stat
Date: Tue, 20 Aug 2013 17:15:11 +0200 [thread overview]
Message-ID: <20130820151509.GA17441@somewhere> (raw)
In-Reply-To: <20130820111426.GA27828@swordfish.datadirectnet.com>
On Tue, Aug 20, 2013 at 02:14:26PM +0300, Sergey Senozhatsky wrote:
> Hello,
> 3.11.0-rc6-next-20130820
>
> at some point an overflowed cpu time is reported in /proc/PID/stat
>
> cat /proc/10/stat
> 10 (rcu_preempt) S 2 0 0 0 -1 2129984 0 0 0 0 0 406 0 0 20 0 1 0 10 0 0 18446744073709551615 0 0 0 0 0 0 0 2147483647 0 18446744073709551615 0 0 17 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> cat /proc/10/stat
> 10 (rcu_preempt) S 2 0 0 0 -1 2129984 0 0 0 0 0 406 0 0 20 0 1 0 10 0 0 18446744073709551615 0 0 0 0 0 0 0 2147483647 0 18446744073709551615 0 0 17 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> cat /proc/10/stat
> 10 (rcu_preempt) S 2 0 0 0 -1 2129984 0 0 0 0 0 407 0 0 20 0 1 0 10 0 0 18446744073709551615 0 0 0 0 0 0 0 2147483647 0 18446744073709551615 0 0 17 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> cat /proc/10/stat
> 10 (rcu_preempt) S 2 0 0 0 -1 2129984 0 0 0 0 0 407 0 0 20 0 1 0 10 0 0 18446744073709551615 0 0 0 0 0 0 0 2147483647 0 18446744073709551615 0 0 17 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> cat /proc/10/stat
> 10 (rcu_preempt) S 2 0 0 0 -1 2129984 0 0 0 0 1844674407370 477 0 0 20 0 1 0 10 0 0 18446744073709551615 0 0 0 0 0 0 0 2147483647 0 18446744073709551615 0 0 17 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> ^^^^^^^^^
> cat /proc/10/stat
> 10 (rcu_preempt) S 2 0 0 0 -1 2129984 0 0 0 0 1844674407370 597 0 0 20 0 1 0 10 0 0 18446744073709551615 0 0 0 0 0 0 0 2147483647 0 18446744073709551615 0 0 17 0 0 0 0 0 0 0 0 0 0 0 0 0 0
>
> (seems there are several more -1UL in output)
>
>
> oddly enough, I see this happening only for RCU
>
> ps aux | grep rcu
> root 8 0.0 0.0 0 0 ? S 12:42 0:00 [rcuc/0]
> root 9 0.0 0.0 0 0 ? S 12:42 0:00 [rcub/0]
> root 10 62422329 0.0 0 0 ? R 12:42 21114581:37 [rcu_preempt]
> root 11 0.1 0.0 0 0 ? S 12:42 0:02 [rcuop/0]
> root 12 62422329 0.0 0 0 ? S 12:42 21114581:35 [rcuop/1]
>
> -ss
Hello,
Please upload your config.
I'm adding Stanislaw in Cc in case it relates to cputime scaling.
next prev parent reply other threads:[~2013-08-20 15:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 11:14 [sched next] overflowed cpu time for kernel threads in /proc/PID/stat Sergey Senozhatsky
2013-08-20 15:15 ` Frederic Weisbecker [this message]
2013-08-20 15:35 ` Sergey Senozhatsky
2013-08-20 15:42 ` Frederic Weisbecker
2013-08-20 15:53 ` Sergey Senozhatsky
2013-08-20 18:48 ` Sergey Senozhatsky
2013-08-21 15:39 ` Sergey Senozhatsky
2013-08-30 23:04 ` Frederic Weisbecker
2013-08-31 19:01 ` Sergey Senozhatsky
2013-09-08 10:56 ` Frederic Weisbecker
2013-09-08 10:59 ` Frederic Weisbecker
2013-09-02 12:28 ` Sergey Senozhatsky
2013-09-02 13:07 ` Frederic Weisbecker
2013-09-02 13:39 ` Sergey Senozhatsky
2013-09-02 13:50 ` Stanislaw Gruszka
2013-09-02 14:00 ` Sergey Senozhatsky
2013-09-03 8:43 ` Stanislaw Gruszka
2013-09-03 9:33 ` Sergey Senozhatsky
2013-09-03 13:15 ` Sergey Senozhatsky
2013-09-03 18:09 ` Sergey Senozhatsky
2013-09-03 18:32 ` Ingo Molnar
2013-09-04 12:08 ` [PATCH -tip] sched/cputime: do not scale when utime == 0 Stanislaw Gruszka
2013-09-04 12:33 ` Ingo Molnar
2013-09-04 13:16 ` [PATCH -tip v2] " Stanislaw Gruszka
2013-09-04 14:31 ` Ingo Molnar
2013-09-04 14:37 ` [tip:timers/urgent] sched/cputime: Do " tip-bot for Stanislaw Gruszka
2013-09-04 15:35 ` Frederic Weisbecker
2013-09-02 14:13 ` [sched next] overflowed cpu time for kernel threads in /proc/PID/stat Frederic Weisbecker
2013-09-02 14:24 ` Sergey Senozhatsky
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=20130820151509.GA17441@somewhere \
--to=fweisbec@gmail.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=sgruszka@redhat.com \
/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.