From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757336Ab0JVOiO (ORCPT ); Fri, 22 Oct 2010 10:38:14 -0400 Received: from mx1.redhat.com ([209.132.183.28]:33701 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755197Ab0JVOiN (ORCPT ); Fri, 22 Oct 2010 10:38:13 -0400 Date: Fri, 22 Oct 2010 10:36:57 -0400 From: Jason Baron To: Peter Zijlstra Cc: Ingo Molnar , Steven Rostedt , LKML , Andrew Morton , Frederic Weisbecker , Thomas Gleixner , "H. Peter Anvin" , Arnaldo Carvalho de Melo , tj@kernel.org Subject: Re: [PATCH][GIT PULL] tracing: Fix compile issue for trace_sched_wakeup.c Message-ID: <20101022143656.GB6498@redhat.com> References: <1287508282.16971.386.camel@gandalf.stny.rr.com> <20101019184111.GA17266@elte.hu> <20101020154045.GA18353@elte.hu> <1287659656.16971.573.camel@gandalf.stny.rr.com> <20101021112614.GB26984@elte.hu> <20101022014441.GA1948@redhat.com> <1287735271.15336.18.camel@twins> <20101022141349.GA6498@redhat.com> <1287757382.15336.45.camel@twins> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1287757382.15336.45.camel@twins> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 22, 2010 at 04:23:02PM +0200, Peter Zijlstra wrote: > On Fri, 2010-10-22 at 10:13 -0400, Jason Baron wrote: > > On Fri, Oct 22, 2010 at 10:14:31AM +0200, Peter Zijlstra wrote: > > > On Thu, 2010-10-21 at 21:44 -0400, Jason Baron wrote: > > > > > > > I finally found that we actually continue to run after the above > > > > apparent 'hang'. That is, we continue to make progress updating the jump > > > > labels. And doing a dump of all the system tasks at the time of the hang > > > > showed the processes in various places besides the stop machine threads. > > > > Thus, I thought that perhaps, for some reason the stop machine threads > > > > weren't being scheduled. > > > > > > > > Thus, I tried commenting out the special scheduling that is set up for > > > > stop machine threads, and that fixed the hang. I haven't yet looked into > > > > what might be going wrong with that scheduling...but maybe somebody else > > > > knows... > > > > > > Hrmm, so are you saying rq->stop was runnable but not running? > > > > yes, that's what it seems like. > > > > > > > > That would imply broken wakeup-preemption, does something like the below > > > cure that? > > > > > > > > > > no still seeing the same hang with the below patch...also, as a data point I > > backed out the patch that adds the stop_sched_class and that resolved the hang > > as well - just as a data point. > > Weird... and there's no hotplugging happening, right? > don't think so. > Can this be reproduced in qemu? I don't have a i386-smp machine around > to use. > its actually an amd 64-bit system with a 32-bit install of f13... > Could you trace the thing with all sched (except the sched_stat) > tracepoints enabled? I think there's a sysrq key to dump the trace once > the machine's stuck.. > the current test is triguring this on boot testing enabling/disabling the tracepoints...so it would be interesting to disable the boot test, and see if I can re-produce it at run-time...which will make getting the trace much easier :) -Jason