Date: Wed, 6 Apr 2011 20:16:58 -0400
From: Don Zickus <dzickus@redhat.com>
To: Shaun Ruffell <sruffell@digium.com>
Cc: linux-kernel@vger.kernel.org, Cyrill Gorcunov <gorcunov@openvz.org>,
        Ingo Molnar <mingo@elte.hu>
Subject: Re: [regression 2.6.39-rc2][bisected] "perf, x86: P4 PMU - Read
 proper MSR register to catch" and NMIs
Message-ID: <20110407001658.GW12642@redhat.com>
References: <20110406223036.GA15721@digium.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110406223036.GA15721@digium.com>
User-Agent: Mutt/1.5.20 (2009-08-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 915
Lines: 22

On Wed, Apr 06, 2011 at 05:30:36PM -0500, Shaun Ruffell wrote:
> Hello Don,
> 
> I was able to bisect it down to commit 242214f9c1eeaae40, but I'm not
> certain where to go from here.  Is this something that is already known
> or is there more information I should try to collect? 

Nope, this is an ongoing issue.  What happened was the perf P4 nmi handler
was swallowing all the NMIs.  My patch fixed that and exposed a double NMI
problem.  We have been chasing it for a couple of months.  I think Cyril
was finally able to duplicate it (as he wrote the P4 code).  I have
confidence that he will find a fix for it soon. :-)

Thanks for the report though!

Cheers,
Don
--
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/