From: Dave Jones <davej@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
linux-kbuild@vger.kernel.org
Subject: Re: tracing ring_buffer_resize oops.
Date: Thu, 24 May 2012 17:15:20 -0400 [thread overview]
Message-ID: <20120524211520.GA2800@redhat.com> (raw)
In-Reply-To: <1337891586.13348.202.camel@gandalf.stny.rr.com>
On Thu, May 24, 2012 at 04:33:06PM -0400, Steven Rostedt wrote:
> I'm kicking off the ktest that initially caused this issue hoping that
> it reproduces the bad tree again.
>
> BTW, did you happen to upgrade gcc or anything? The ktest I run does
> test against different gcc's and I don't think I had it do a make clean
> between the switch. That may be the cause of this problem too :-?
No gcc updates. It's a Fedora 17 box, so there's been hardly any updates this
last week or so as things have been frozen leading into the release.
Dave
next prev parent reply other threads:[~2012-05-24 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120524160146.GA6226@redhat.com>
[not found] ` <1337876398.13348.178.camel@gandalf.stny.rr.com>
[not found] ` <20120524172223.GA10689@redhat.com>
[not found] ` <1337880914.13348.189.camel@gandalf.stny.rr.com>
[not found] ` <20120524184728.GA13201@redhat.com>
[not found] ` <1337885672.13348.194.camel@gandalf.stny.rr.com>
[not found] ` <20120524191147.GA13936@redhat.com>
[not found] ` <1337887495.13348.195.camel@gandalf.stny.rr.com>
[not found] ` <20120524200541.GA6552@redhat.com>
2012-05-24 20:18 ` tracing ring_buffer_resize oops Steven Rostedt
2012-05-24 20:33 ` Steven Rostedt
2012-05-24 21:15 ` Dave Jones [this message]
2012-05-24 21:25 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120524211520.GA2800@redhat.com \
--to=davej@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox