Message-ID: <1337885672.13348.194.camel@gandalf.stny.rr.com>
Subject: Re: tracing ring_buffer_resize oops.
From: Steven Rostedt <rostedt@goodmis.org>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
        Frederic Weisbecker <fweisbec@gmail.com>,
        Ingo Molnar <mingo@redhat.com>
Date: Thu, 24 May 2012 14:54:32 -0400
In-Reply-To: <20120524184728.GA13201@redhat.com>
References: <20120524160146.GA6226@redhat.com>
	 <1337876398.13348.178.camel@gandalf.stny.rr.com>
	 <20120524172223.GA10689@redhat.com>
	 <1337880914.13348.189.camel@gandalf.stny.rr.com>
	 <20120524184728.GA13201@redhat.com>
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1077
Lines: 31

On Thu, 2012-05-24 at 14:47 -0400, Dave Jones wrote:
> On Thu, May 24, 2012 at 01:35:14PM -0400, Steven Rostedt wrote:
> 
>  > Hmm, I wonder if this is the break point change :-/
>  > 
>  > Do you have NMIs enabled? I didn't have 'paranoid_exit' in my backtrace
>  > when I saw the bug.
> 
> $ grep NMI .config
> CONFIG_OPROFILE_NMI_TIMER=y
> CONFIG_HAVE_PERF_EVENTS_NMI=y
> CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=y
> CONFIG_HPWDT_NMI_DECODING=y
> # CONFIG_DEBUG_NMI_SELFTEST is not set

Could you email your entire config. I haven't been able to trigger the
bug again. Maybe your config might do it :-/

Also, how reproducible is it? When it triggered for me, it was constant.
Every boot and test failed. But after I did the make mrproper, I have
not been able to trigger it again. This is why I put it down as a bad
build.

-- Steve


--
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/