On Mon, 2013-12-23 at 05:38 +0100, Mike Galbraith wrote: > On Sun, 2013-12-22 at 09:57 +0100, Mike Galbraith wrote: > > I'll let the box give > > RCU something to do for a couple days. No news is good news. > > Ho ho hum, merry christmas, gift attached. > > I'll beat on virgin -rt7, see if it survives, then re-apply RCU patch > and retest. This kernel had nohz_full enabled, along with Sebastian's > pending -rt fix for same, so RCU patch was not only not running solo, > box was running a known somewhat buggy config as well. Box was doing > endless tbench 64 when it started stalling fwiw. > > -Mike P.S. virgin -rt7 doing tbench 64 + make -j64 [ 97.907960] perf samples too long (3138 > 2500), lowering kernel.perf_event_max_sample_rate to 50000 [ 103.047921] perf samples too long (5544 > 5000), lowering kernel.perf_event_max_sample_rate to 25000 [ 181.561271] perf samples too long (10318 > 10000), lowering kernel.perf_event_max_sample_rate to 13000 [ 184.243750] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 1.084 msecs [ 248.914422] perf samples too long (19719 > 19230), lowering kernel.perf_event_max_sample_rate to 7000 [ 382.116674] NOHZ: local_softirq_pending 10 [ 405.201593] perf samples too long (36824 > 35714), lowering kernel.perf_event_max_sample_rate to 4000 [ 444.704185] NOHZ: local_softirq_pending 08 [ 444.704208] NOHZ: local_softirq_pending 08 [ 444.704579] NOHZ: local_softirq_pending 08 [ 444.704678] NOHZ: local_softirq_pending 08 [ 444.705100] NOHZ: local_softirq_pending 08 [ 444.705980] NOHZ: local_softirq_pending 08 [ 444.705994] NOHZ: local_softirq_pending 08 [ 444.708315] NOHZ: local_softirq_pending 08 [ 444.710348] NOHZ: local_softirq_pending 08 [ 474.435582] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 1.096 msecs [ 475.994055] perf samples too long (63124 > 62500), lowering kernel.perf_event_max_sample_rate to 2000 Those annoying perf gripes are generic, not -rt. -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
