Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752684AbcC0VJK (ORCPT ); Sun, 27 Mar 2016 17:09:10 -0400 Received: from e35.co.us.ibm.com ([32.97.110.153]:54108 "EHLO e35.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751329AbcC0VJI (ORCPT ); Sun, 27 Mar 2016 17:09:08 -0400 X-IBM-Helo: d03dlp02.boulder.ibm.com X-IBM-MailFrom: paulmck@linux.vnet.ibm.com X-IBM-RcptTo: linux-kernel@vger.kernel.org Date: Sun, 27 Mar 2016 14:09:14 -0700 From: "Paul E. McKenney" To: Peter Zijlstra Cc: Jacob Pan , Josh Triplett , Ross Green , Mathieu Desnoyers , John Stultz , Thomas Gleixner , lkml , Ingo Molnar , Lai Jiangshan , dipankar@in.ibm.com, Andrew Morton , rostedt , David Howells , Eric Dumazet , Darren Hart , =?iso-8859-1?Q?Fr=E9d=E9ric?= Weisbecker , Oleg Nesterov , pranith kumar , "Chatre, Reinette" Subject: Re: rcu_preempt self-detected stall on CPU from 4.5-rc3, since 3.17 Message-ID: <20160327210914.GD4287@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <686568926.5862.1456259651418.JavaMail.zimbra@efficios.com> <20160223205522.GT3522@linux.vnet.ibm.com> <20160226005638.GV3522@linux.vnet.ibm.com> <20160318210011.GA571@cloud> <20160318235641.GH4287@linux.vnet.ibm.com> <20160321092230.75f23fa9@yairi> <20160327205439.GY6356@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160327205439.GY6356@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16032721-0013-0000-0000-0000215B09A5 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1784 Lines: 43 On Sun, Mar 27, 2016 at 10:54:39PM +0200, Peter Zijlstra wrote: > On Mon, Mar 21, 2016 at 09:22:30AM -0700, Jacob Pan wrote: > > > > We're seeing a similar stall (~60 seconds) on an x86 development > > > > system here. Any luck tracking down the cause of this? If not, any > > > > suggestions for traces that might be helpful? > > > +Reinette, she has the system that can reproduce the issue. I > > believe she is having some other problems with it at the moment. But > > the .config should be available. Version is v4.5. > > Does that system have MONITOR/MWAIT errata? On the off-chance that this question was also directed at me, here is what I am running on. I am running in a qemu/KVM virtual machine, in case that matters. Thanx, Paul processor : 63 vendor_id : GenuineIntel cpu family : 6 model : 47 model name : Intel(R) Xeon(R) CPU E7- 4820 @ 2.00GHz stepping : 2 microcode : 0x37 cpu MHz : 1064.000 cache size : 18432 KB physical id : 3 siblings : 16 core id : 25 cpu cores : 8 apicid : 243 initial apicid : 243 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt aes lahf_lm ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid bogomips : 3990.01 clflush size : 64 cache_alignment : 64 address sizes : 44 bits physical, 48 bits virtual power management: