From: Peter Zijlstra <peterz@infradead.org>
To: Arun Sharma <arun@sharma-home.net>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: 2.6.37 kernel warning in perf_events code
Date: Fri, 11 Feb 2011 13:16:09 +0100 [thread overview]
Message-ID: <1297426569.5226.41.camel@laptop> (raw)
In-Reply-To: <AANLkTimwaOSC9CmO0rCPrRkCac-=Yj2PGg1DE_d0aM55@mail.gmail.com>
On Thu, 2011-02-10 at 16:57 -0800, Arun Sharma wrote:
> On Thu, Feb 10, 2011 at 4:42 PM, Arnaldo Carvalho de Melo
> <acme@redhat.com> wrote:
> > Is it possible for you to test this with 2.6.38-rc4? At least the user
> > level tools, just do:
>
> I tried the 2.6.38rc3 perf binary on two machines:
>
> kernel = 2.6.37: The machine hung solid on the first try.
> kernel = 2.6.38rc3: I could run it 10 times in a loop and no bad runs.
>
> Looks like this is already fixed in newer kernels.
I couldn't actually reproduce on .37 with the given details, so while
its already fixed it would be nice to figure out what patch fixed it so
we can make sure it ends up in .37-stable.
Could you provide exact reproduction details or maybe bisect the thing?
prev parent reply other threads:[~2011-02-11 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 2:50 2.6.37 kernel warning in perf_events code Arun Sharma
2011-02-10 19:08 ` Arnaldo Carvalho de Melo
2011-02-10 20:02 ` Arun Sharma
2011-02-10 20:20 ` Arnaldo Carvalho de Melo
2011-02-10 20:46 ` Arun Sharma
2011-02-11 0:42 ` Arnaldo Carvalho de Melo
2011-02-11 0:57 ` Arun Sharma
2011-02-11 12:16 ` Peter Zijlstra [this message]
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=1297426569.5226.41.camel@laptop \
--to=peterz@infradead.org \
--cc=acme@redhat.com \
--cc=arun@sharma-home.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).