rcu_preempt running flat out on idle desktop.
On what should be an idle desktop, I'm seeing really strange things.
The XFCE CPU meter shows both cores are running with no idle time.
here's the top of the top(1) output..
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10 root 20 0 0 0 0 S 200.0 0.0 185301:36 rcu_preempt 553 root 20 0 268m 76m 6764 S 200.0 2.6 144579:53 Xorg 1199 root 20 0 0 0 0 S 200.0 0.0 306:17.85 kworker/1:0 501 root 20 0 0 0 0 S 200.0 0.0 4471:03 kworker/0:2 12 root 20 0 0 0 0 S 200.0 0.0 67277:16 rcuop/1 1237 davej 20 0 535m 15m 8484 S 200.0 0.5 3645:16 Terminal 859 davej 20 0 117m 3036 1336 S 200.0 0.1 1986:55 htop
There are a lot of processes allegedly using "200%" of CPU time, a handful in the "196%" range, and then a bunch at 0.
rcu_preempt is staying at the top of the list while everything else bubbles up the list.
And what's up with those TIME entries? Box has only been up a few hours, so those numbers look really crazy.
RCU options for this build are..
CONFIG_TREE_PREEMPT_RCU=yCONFIG_PREEMPT_RCU=yCONFIG_RCU_STALL_COMMON=yCONFIG_RCU_USER_QS=yCONFIG_RCU_FANOUT=64CONFIG_RCU_FANOUT_LEAF=16
# CONFIG_RCU_FANOUT_EXACT is not set
# CONFIG_RCU_FAST_NO_HZ is not setCONFIG_TREE_RCU_TRACE=yCONFIG_RCU_BOOST=yCONFIG_RCU_BOOST_PRIO=1CONFIG_RCU_BOOST_DELAY=500CONFIG_RCU_NOCB_CPU=yCONFIG_RCU_NOCB_CPU_ALL=yCONFIG_DEBUG_OBJECTS_RCU_HEAD=yCONFIG_PROVE_RCU=y
# CONFIG_PROVE_RCU_REPEATEDLY is not setCONFIG_PROVE_RCU_DELAY=yCONFIG_SPARSE_RCU_POINTER=y
# CONFIG_RCU_TORTURE_TEST is not setCONFIG_RCU_CPU_STALL_TIMEOUT=60CONFIG_RCU_CPU_STALL_VERBOSE=y
# CONFIG_RCU_CPU_STALL_INFO is not setCONFIG_RCU_TRACE=y
Dave
Quoted 15 lines · Dave Jones
On what should be an idle desktop, I'm seeing really strange things.
The XFCE CPU meter shows both cores are running with no idle time.
here's the top of the top(1) output..
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10 root 20 0 0 0 0 S 200.0 0.0 185301:36 rcu_preempt 553 root 20 0 268m 76m 6764 S 200.0 2.6 144579:53 Xorg 1199 root 20 0 0 0 0 S 200.0 0.0 306:17.85 kworker/1:0 501 root 20 0 0 0 0 S 200.0 0.0 4471:03 kworker/0:2 12 root 20 0 0 0 0 S 200.0 0.0 67277:16 rcuop/1 1237 davej 20 0 535m 15m 8484 S 200.0 0.5 3645:16 Terminal 859 davej 20 0 117m 3036 1336 S 200.0 0.1 1986:55 htop
Quoted 2 lines
There are a lot of processes allegedly using "200%" of CPU time, a handful in the "196%" range, and then a bunch at 0.
Yow!!! 185301 minutes is 128 days, which is a truly impressive amount of CPU time to accumulate in a few short hours.
Quoted 24 lines
rcu_preemptis staying at the top of the list while everything else bubbles up the list.And what's up with those TIME entries? Box has only been up a few hours, so those numbers look really crazy.
RCU options for this build are..
CONFIG_TREE_PREEMPT_RCU=yCONFIG_PREEMPT_RCU=yCONFIG_RCU_STALL_COMMON=yCONFIG_RCU_USER_QS=yCONFIG_RCU_FANOUT=64CONFIG_RCU_FANOUT_LEAF=16
#CONFIG_RCU_FANOUT_EXACTis not set
#CONFIG_RCU_FAST_NO_HZis not setCONFIG_TREE_RCU_TRACE=yCONFIG_RCU_BOOST=yCONFIG_RCU_BOOST_PRIO=1CONFIG_RCU_BOOST_DELAY=500CONFIG_RCU_NOCB_CPU=yCONFIG_RCU_NOCB_CPU_ALL=yCONFIG_DEBUG_OBJECTS_RCU_HEAD=yCONFIG_PROVE_RCU=y
Quoted 8 lines
#
CONFIG_PROVE_RCU_REPEATEDLYis not setCONFIG_PROVE_RCU_DELAY=yCONFIG_SPARSE_RCU_POINTER=y
#CONFIG_RCU_TORTURE_TESTis not setCONFIG_RCU_CPU_STALL_TIMEOUT=60CONFIG_RCU_CPU_STALL_VERBOSE=y
#CONFIG_RCU_CPU_STALL_INFOis not setCONFIG_RCU_TRACE=y
This is 3.9, or Linus's current tree? I am guessing the latter, but figured I should ask.
Thanx, Paul
Quoted 11 lines · Paul E. McKenney
Quoted 9 lines · Dave Jones
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10 root 20 0 0 0 0 S 200.0 0.0 185301:36 rcu_preempt 553 root 20 0 268m 76m 6764 S 200.0 2.6 144579:53 Xorg 1199 root 20 0 0 0 0 S 200.0 0.0 306:17.85 kworker/1:0 501 root 20 0 0 0 0 S 200.0 0.0 4471:03 kworker/0:2 12 root 20 0 0 0 0 S 200.0 0.0 67277:16 rcuop/1 1237 davej 20 0 535m 15m 8484 S 200.0 0.5 3645:16 Terminal 859 davej 20 0 117m 3036 1336 S 200.0 0.1 1986:55 htop
Quoted 5 lines
Quoted 2 lines
There are a lot of processes allegedly using "200%" of CPU time, a handful in the "196%" range, and then a bunch at 0.
Yow!!! 185301 minutes is 128 days, which is a truly impressive amount of CPU time to accumulate in a few short hours.
perf top doesn't show anything out of the ordinary. Just as an idle desktop should behave, it's spending a bunch of time in delay_tsc.
Quoted 2 lines
This is 3.9, or Linus's current tree? I am guessing the latter, but figured I should ask.
Yeah, the latter. (v3.9-11572-g5af43c2)
Dave
Quoted 18 lines · Dave Jones
Quoted 11 lines · Paul E. McKenney
Quoted 9 lines · Dave Jones
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10 root 20 0 0 0 0 S 200.0 0.0 185301:36 rcu_preempt 553 root 20 0 268m 76m 6764 S 200.0 2.6 144579:53 Xorg 1199 root 20 0 0 0 0 S 200.0 0.0 306:17.85 kworker/1:0 501 root 20 0 0 0 0 S 200.0 0.0 4471:03 kworker/0:2 12 root 20 0 0 0 0 S 200.0 0.0 67277:16 rcuop/1 1237 davej 20 0 535m 15m 8484 S 200.0 0.5 3645:16 Terminal 859 davej 20 0 117m 3036 1336 S 200.0 0.1 1986:55 htopQuoted 5 lines
Quoted 2 lines
There are a lot of processes allegedly using "200%" of CPU time, a handful in the "196%" range, and then a bunch at 0.
Yow!!! 185301 minutes is 128 days, which is a truly impressive amount of CPU time to accumulate in a few short hours.
Quoted 7 lines
perf top doesn't show anything out of the ordinary. Just as an idle desktop should behave, it's spending a bunch of time in
delay_tsc.Quoted 2 lines
This is 3.9, or Linus's current tree? I am guessing the latter, but figured I should ask.
Yeah, the latter. (v3.9-11572-g5af43c2)
Do you have CONFIG_NO_HZ_FULL=y? We just might have a bug in tickless CPU-time accounting...
Thanx, Paul
Quoted 22 lines · Paul E. McKenney
Quoted 21 lines · Dave Jones
Quoted 11 lines · Paul E. McKenney
Quoted 9 lines · Dave Jones
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10 root 20 0 0 0 0 S 200.0 0.0 185301:36 rcu_preempt 553 root 20 0 268m 76m 6764 S 200.0 2.6 144579:53 Xorg 1199 root 20 0 0 0 0 S 200.0 0.0 306:17.85 kworker/1:0 501 root 20 0 0 0 0 S 200.0 0.0 4471:03 kworker/0:2 12 root 20 0 0 0 0 S 200.0 0.0 67277:16 rcuop/1 1237 davej 20 0 535m 15m 8484 S 200.0 0.5 3645:16 Terminal 859 davej 20 0 117m 3036 1336 S 200.0 0.1 1986:55 htopQuoted 5 lines
Quoted 2 lines
There are a lot of processes allegedly using "200%" of CPU time, a handful in the "196%" range, and then a bunch at 0.
Yow!!! 185301 minutes is 128 days, which is a truly impressive amount of CPU time to accumulate in a few short hours.
perf top doesn't show anything out of the ordinary. Just as an idle desktop should behave, it's spending a bunch of time in
delay_tsc.
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
This is 3.9, or Linus's current tree? I am guessing the latter, but figured I should ask.
Yeah, the latter. (v3.9-11572-g5af43c2)
Do you have
CONFIG_NO_HZ_FULL=y? We just might have a bug in tickless CPU-time accounting...
I never saw a new config option I didn't like.
CONFIG_NO_HZ_FULL=yCONFIG_NO_HZ_FULL_ALL=y
Dave
Quoted 26 lines · Dave Jones
Quoted 25 lines · Paul E. McKenney
Quoted 24 lines · Dave Jones
Quoted 11 lines · Paul E. McKenney
Quoted 9 lines · Dave Jones
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10 root 20 0 0 0 0 S 200.0 0.0 185301:36 rcu_preempt 553 root 20 0 268m 76m 6764 S 200.0 2.6 144579:53 Xorg 1199 root 20 0 0 0 0 S 200.0 0.0 306:17.85 kworker/1:0 501 root 20 0 0 0 0 S 200.0 0.0 4471:03 kworker/0:2 12 root 20 0 0 0 0 S 200.0 0.0 67277:16 rcuop/1 1237 davej 20 0 535m 15m 8484 S 200.0 0.5 3645:16 Terminal 859 davej 20 0 117m 3036 1336 S 200.0 0.1 1986:55 htopQuoted 5 lines
Quoted 2 lines
There are a lot of processes allegedly using "200%" of CPU time, a handful in the "196%" range, and then a bunch at 0.
Yow!!! 185301 minutes is 128 days, which is a truly impressive amount of CPU time to accumulate in a few short hours.
perf top doesn't show anything out of the ordinary. Just as an idle desktop should behave, it's spending a bunch of time in
delay_tsc.Quoted 2 lines
This is 3.9, or Linus's current tree? I am guessing the latter, but figured I should ask.
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
Yeah, the latter. (v3.9-11572-g5af43c2)
Do you have
CONFIG_NO_HZ_FULL=y? We just might have a bug in tickless CPU-time accounting...I never saw a new config option I didn't like.
;-) ;-) ;-)
Quoted 2 lines
CONFIG_NO_HZ_FULL=yCONFIG_NO_HZ_FULL_ALL=y
Adding Frederic on CC...
Thanx, Paul
2013/5/8 Dave Jones <[email protected]>:
Quoted 12 lines · Paul E. McKenney
Quoted 11 lines · Dave Jones
Quoted 10 lines
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10 root 20 0 0 0 0 S 200.0 0.0 185301:36 rcu_preempt 553 root 20 0 268m 76m 6764 S 200.0 2.6 144579:53 Xorg 1199 root 20 0 0 0 0 S 200.0 0.0 306:17.85 kworker/1:0 501 root 20 0 0 0 0 S 200.0 0.0 4471:03 kworker/0:2 12 root 20 0 0 0 0 S 200.0 0.0 67277:16 rcuop/1 1237 davej 20 0 535m 15m 8484 S 200.0 0.5 3645:16 Terminal 859 davej 20 0 117m 3036 1336 S 200.0 0.1 1986:55 htop
Quoted 5 lines
Quoted 5 lines
Quoted 2 lines
There are a lot of processes allegedly using "200%" of CPU time, a handful in the "196%" range, and then a bunch at 0.
Yow!!! 185301 minutes is 128 days, which is a truly impressive amount of CPU time to accumulate in a few short hours.
Right, Ingo has reported something about strange high numbers in top too. I need to investigate that.
Thanks.
Quoted 13 lines · Frederic Weisbecker
2013/5/8 Dave Jones <[email protected]>:
Quoted 12 lines · Paul E. McKenney
Quoted 11 lines · Dave Jones
Quoted 10 lines
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10 root 20 0 0 0 0 S 200.0 0.0 185301:36 rcu_preempt 553 root 20 0 268m 76m 6764 S 200.0 2.6 144579:53 Xorg 1199 root 20 0 0 0 0 S 200.0 0.0 306:17.85 kworker/1:0 501 root 20 0 0 0 0 S 200.0 0.0 4471:03 kworker/0:2 12 root 20 0 0 0 0 S 200.0 0.0 67277:16 rcuop/1 1237 davej 20 0 535m 15m 8484 S 200.0 0.5 3645:16 Terminal 859 davej 20 0 117m 3036 1336 S 200.0 0.1 1986:55 htop
Quoted 8 lines
Quoted 5 lines
Quoted 5 lines
Quoted 2 lines
There are a lot of processes allegedly using "200%" of CPU time, a handful in the "196%" range, and then a bunch at 0.
Yow!!! 185301 minutes is 128 days, which is a truly impressive amount of CPU time to accumulate in a few short hours.
Right, Ingo has reported something about strange high numbers in top too. I need to investigate that.
For CPU-intense loops I have seen a small anomaly with "slightly higher CPU usage numbers" - sometimes going to 101% or so but still converging to around 99.9% in the long run.
The 200% bug pasted by Dave here seems to be very big and seems to affect all tasks not just true CPU-loopers. So I'd suggest reproducing and fixing Dave's bug first - that might fix the small anomaly I've seen.
Thanks,
Ingo
2013/5/8 Dave Jones <[email protected]>:
Quoted 42 lines
On what should be an idle desktop, I'm seeing really strange things.
The XFCE CPU meter shows both cores are running with no idle time.
here's the top of the top(1) output..
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10 root 20 0 0 0 0 S 200.0 0.0 185301:36 rcu_preempt 553 root 20 0 268m 76m 6764 S 200.0 2.6 144579:53 Xorg 1199 root 20 0 0 0 0 S 200.0 0.0 306:17.85 kworker/1:0 501 root 20 0 0 0 0 S 200.0 0.0 4471:03 kworker/0:2 12 root 20 0 0 0 0 S 200.0 0.0 67277:16 rcuop/1 1237 davej 20 0 535m 15m 8484 S 200.0 0.5 3645:16 Terminal 859 davej 20 0 117m 3036 1336 S 200.0 0.1 1986:55 htopThere are a lot of processes allegedly using "200%" of CPU time, a handful in the "196%" range, and then a bunch at 0.
rcu_preemptis staying at the top of the list while everything else bubbles up the list.And what's up with those TIME entries? Box has only been up a few hours, so those numbers look really crazy.
RCU options for this build are..
CONFIG_TREE_PREEMPT_RCU=yCONFIG_PREEMPT_RCU=yCONFIG_RCU_STALL_COMMON=yCONFIG_RCU_USER_QS=yCONFIG_RCU_FANOUT=64CONFIG_RCU_FANOUT_LEAF=16
#CONFIG_RCU_FANOUT_EXACTis not set
#CONFIG_RCU_FAST_NO_HZis not setCONFIG_TREE_RCU_TRACE=yCONFIG_RCU_BOOST=yCONFIG_RCU_BOOST_PRIO=1CONFIG_RCU_BOOST_DELAY=500CONFIG_RCU_NOCB_CPU=yCONFIG_RCU_NOCB_CPU_ALL=yCONFIG_DEBUG_OBJECTS_RCU_HEAD=yCONFIG_PROVE_RCU=y
Quoted 8 lines
#
CONFIG_PROVE_RCU_REPEATEDLYis not setCONFIG_PROVE_RCU_DELAY=yCONFIG_SPARSE_RCU_POINTER=y
#CONFIG_RCU_TORTURE_TESTis not setCONFIG_RCU_CPU_STALL_TIMEOUT=60CONFIG_RCU_CPU_STALL_VERBOSE=y
#CONFIG_RCU_CPU_STALL_INFOis not setCONFIG_RCU_TRACE=y
I can't reproduce that issue even with the above setting. Could you please send me your whole config?
Thanks.
Quoted 4 lines · Frederic Weisbecker
Quoted 2 lines
RCU options for this build are..
I can't reproduce that issue even with the above setting. Could you please send me your whole config?
http://paste.fedoraproject.org/11363/36813375/raw/
Dave
Quoted 8 lines · Dave Jones
Quoted 4 lines · Frederic Weisbecker
Quoted 2 lines
RCU options for this build are..
I can't reproduce that issue even with the above setting. Could you please send me your whole config?
Sorry it took me some time to get that config booting, I ran into other unrelated crashes.
So I'm observing the exact opposite than you: the processes appear to have no load nor to consume cputime. Even if I use some dumb user loop. Top don't even show it.
I'm digging further and will tell you when I get more info.
Thanks.
Quoted 10 lines · Frederic Weisbecker
Quoted 8 lines · Dave Jones
Quoted 4 lines · Frederic Weisbecker
Quoted 2 lines
RCU options for this build are..
I can't reproduce that issue even with the above setting. Could you please send me your whole config?
Quoted 8 lines
Sorry it took me some time to get that config booting, I ran into other unrelated crashes.
So I'm observing the exact opposite than you: the processes appear to have no load nor to consume cputime. Even if I use some dumb user loop. Top don't even show it.
I'm digging further and will tell you when I get more info.
So I'm still seeing this on rc4.
Here's my 'idle' firewall, just routing packets:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4405 root 20 0 0 0 0 S 400.0 0.0 52336:27 kworker/2:0 20968 davej 20 0 115m 1840 1092 R 400.0 0.1 2297:48 top 964 named 20 0 383m 32m 2896 S 400.0 1.7 81384:54 named 10 root 20 0 0 0 0 S 400.0 0.0 195403:05 rcu_preempt 20830 davej 20 0 125m 2172 1024 S 400.0 0.1 939:36.10 sshd 11 root 20 0 0 0 0 S 400.0 0.0 42644:33 rcuop/0 13 root 20 0 0 0 0 S 400.0 0.0 34729:04 rcuop/2 754 lighttpd 20 0 54640 2692 1732 S 400.0 0.1 35286:11 lighttpd 756 root 20 0 216m 10m 6116 S 400.0 0.5 34143:41 snmpd 35 root 20 0 0 0 0 S 400.0 0.0 12790:56 ksoftirqd/2 19893 root 20 0 0 0 0 S 400.0 0.0 12570:49 kworker/0:1 20059 root 20 0 0 0 0 S 400.0 0.0 4666:30 kworker/1:1 32 root rt 0 0 0 0 S 400.0 0.0 8780:22 watchdog/2 792 root 20 0 92220 2516 632 S 400.0 0.1 7821:28 sendmail 25 root rt 0 0 0 0 S 400.0 0.0 8780:21 watchdog/0 26 root rt 0 0 0 0 S 400.0 0.0 8780:22 watchdog/1 38 root rt 0 0 0 0 S 400.0 0.0 8780:22 watchdog/3 19167 root 20 0 0 0 0 S 400.0 0.0 7804:04 kworker/3:2
Every process is either 400%, or 0%.
Here's my desktop box, just writing this email:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
10 root 20 0 0 0 0 S 200.0 0.0 35134:00 rcu_preempt
12 root 20 0 0 0 0 S 200.0 0.0 14059:47 rcuop/1
12528 root 20 0 0 0 0 S 200.0 0.0 1012:56 kworker/0:1
12999 davej 20 0 115m 1700 956 R 200.0 0.1 1:09.10 top
4799 root 20 0 0 0 0 S 200.0 0.0 3510:40 kworker/1:1
1 root 20 0 50760 5092 1648 S 0.0 0.2 3:14.96 systemd
2 root 20 0 0 0 0 S 0.0 0.0 1:40.55 kthreadd Every process 200% or 0%.
Dave
Quoted 58 lines · Dave Jones
Quoted 10 lines · Frederic Weisbecker
Quoted 8 lines · Dave Jones
Quoted 4 lines · Frederic Weisbecker
Quoted 2 lines
RCU options for this build are..
I can't reproduce that issue even with the above setting. Could you please send me your whole config?
Quoted 8 lines
Sorry it took me some time to get that config booting, I ran into other unrelated crashes.
So I'm observing the exact opposite than you: the processes appear to have no load nor to consume cputime. Even if I use some dumb user loop. Top don't even show it.
I'm digging further and will tell you when I get more info.
So I'm still seeing this on rc4.
Here's my 'idle' firewall, just routing packets:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4405 root 20 0 0 0 0 S 400.0 0.0 52336:27 kworker/2:0 20968 davej 20 0 115m 1840 1092 R 400.0 0.1 2297:48 top 964 named 20 0 383m 32m 2896 S 400.0 1.7 81384:54 named 10 root 20 0 0 0 0 S 400.0 0.0 195403:05 rcu_preempt 20830 davej 20 0 125m 2172 1024 S 400.0 0.1 939:36.10 sshd 11 root 20 0 0 0 0 S 400.0 0.0 42644:33 rcuop/0 13 root 20 0 0 0 0 S 400.0 0.0 34729:04 rcuop/2 754 lighttpd 20 0 54640 2692 1732 S 400.0 0.1 35286:11 lighttpd 756 root 20 0 216m 10m 6116 S 400.0 0.5 34143:41 snmpd 35 root 20 0 0 0 0 S 400.0 0.0 12790:56 ksoftirqd/2 19893 root 20 0 0 0 0 S 400.0 0.0 12570:49 kworker/0:1 20059 root 20 0 0 0 0 S 400.0 0.0 4666:30 kworker/1:1 32 root rt 0 0 0 0 S 400.0 0.0 8780:22 watchdog/2 792 root 20 0 92220 2516 632 S 400.0 0.1 7821:28 sendmail 25 root rt 0 0 0 0 S 400.0 0.0 8780:21 watchdog/0 26 root rt 0 0 0 0 S 400.0 0.0 8780:22 watchdog/1 38 root rt 0 0 0 0 S 400.0 0.0 8780:22 watchdog/3 19167 root 20 0 0 0 0 S 400.0 0.0 7804:04 kworker/3:2Every process is either 400%, or 0%.
Here's my desktop box, just writing this email:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10 root 20 0 0 0 0 S 200.0 0.0 35134:00 rcu_preempt 12 root 20 0 0 0 0 S 200.0 0.0 14059:47 rcuop/1 12528 root 20 0 0 0 0 S 200.0 0.0 1012:56 kworker/0:1 12999 davej 20 0 115m 1700 956 R 200.0 0.1 1:09.10 top 4799 root 20 0 0 0 0 S 200.0 0.0 3510:40 kworker/1:1 1 root 20 0 50760 5092 1648 S 0.0 0.2 3:14.96 systemd 2 root 20 0 0 0 0 S 0.0 0.0 1:40.55 kthreadd
Quoted 1 line
Every process 200% or 0%.
I see, would you mind testing this branch?
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers/urgent
It might help, I specially think about 45eacc692771bd2b1ea3d384e6345cab3da10861 ("vtime: Use consistent clocks among nohz accounting") which fixes an issue with cputime accounting that resulted in similar symptoms.
Thanks.
Quoted 4 lines · Frederic Weisbecker
Quoted 1 line
Every process 200% or 0%.
I see, would you mind testing this branch?
Quoted 8 lines
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers/urgentIt might help, I specially think about
45eacc692771bd2b1ea3d384e6345cab3da10861("vtime: Use consistent clocks among nohz accounting") which fixes an issue with cputime accounting that resulted in similar symptoms.Thanks.
5 hours of uptime so far, without anything looking weird. I'll keep an eye on it, but this is looking a lot better so far.
Dave
Quoted 10 lines · Frederic Weisbecker
Quoted 1 line
Every process 200% or 0%.
I see, would you mind testing this branch?
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers/urgentIt might help, I specially think about
45eacc692771bd2b1ea3d384e6345cab3da10861("vtime: Use consistent clocks among nohz accounting") which fixes an issue with cputime accounting that resulted in similar symptoms.
So that patch has been in 'urgent' for a month. Can someone move it to really-urgent or whatever is necessary to get it into Linus' tree ?
DAve
Quoted 9 lines · Dave Jones
Quoted 7 lines · Frederic Weisbecker
Quoted 1 line
Every process 200% or 0%.
I see, would you mind testing this branch?
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers/urgent
Quoted 6 lines
Quoted 3 lines
It might help, I specially think about
45eacc692771bd2b1ea3d384e6345cab3da10861("vtime: Use consistent clocks among nohz accounting") which fixes an issue with cputime accounting that resulted in similar symptoms.So that patch has been in 'urgent' for a month. Can someone move it to really-urgent or whatever is necessary to get it into Linus' tree ?
Another week passes...
This is kind of ridiculous.
Dave
Quoted 10 lines · Dave Jones
Quoted 9 lines · Dave Jones
Quoted 7 lines · Frederic Weisbecker
Quoted 1 line
Every process 200% or 0%.
I see, would you mind testing this branch?
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers/urgent
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
It might help, I specially think about
45eacc692771bd2b1ea3d384e6345cab3da10861("vtime: Use consistent clocks among nohz accounting") which fixes an issue with cputime accounting that resulted in similar symptoms.So that patch has been in 'urgent' for a month. Can someone move it to really-urgent or whatever is necessary to get it into Linus' tree ?
Another week passes...
It was sent to Linus two days before your mail and Linus merged it at around the time you wrote your mail.
So it should be all in -rc7, unless I'm missing something?
Thanks,
Ingo
Quoted 20 lines · Ingo Molnar
Quoted 17 lines · Dave Jones
Quoted 15 lines · Dave Jones
Quoted 10 lines · Frederic Weisbecker
Quoted 1 line
Every process 200% or 0%.
I see, would you mind testing this branch?
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers/urgentIt might help, I specially think about
45eacc692771bd2b1ea3d384e6345cab3da10861("vtime: Use consistent clocks among nohz accounting") which fixes an issue with cputime accounting that resulted in similar symptoms.So that patch has been in 'urgent' for a month. Can someone move it to really-urgent or whatever is necessary to get it into Linus' tree ?
Quoted 6 lines
Quoted 1 line
Another week passes...
It was sent to Linus two days before your mail and Linus merged it at around the time you wrote your mail.
So it should be all in -rc7, unless I'm missing something?
Ah sorry I missed that merge. It's all fine indeed.
Thanks!