Date: Wed, 29 Jan 2014 08:17:32 +0100
From: Ingo Molnar <mingo@kernel.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org, Peter Zijlstra <a.p.zijlstra@chello.nl>,
        Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
        Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: another perf_fuzzer soft lockup
Message-ID: <20140129071731.GA30643@gmail.com>
References: <alpine.DEB.2.10.1401281554010.8613@vincent-weaver-1.um.maine.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.10.1401281554010.8613@vincent-weaver-1.um.maine.edu>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org


* Vince Weaver <vincent.weaver@maine.edu> wrote:

> After some idle time I've started running the perf_fuzzer again.
> 
> It quickly found this lockup on a core2 system running 3.13 (yes, I 
> should probably be running 3.14-git but I'd rather wait for rc1 
> first).

JFYI, if -git looks too dangerous to you (and I cannot blame you for 
that view in the middle of a merge window) then tip:master is usually 
a pretty safe substitute for testing, it's the v3.14 perf code on a 
v3.13 base.

> It looks like it's stuck in a lock in generic_exec_single() while 
> calling perf_event_task_output()?
> 
> I'll try to see if I can come up with a test case.

Thanks, those testcases are always very useful!

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/