From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756642AbcB0PqS (ORCPT ); Sat, 27 Feb 2016 10:46:18 -0500 Received: from one.firstfloor.org ([193.170.194.197]:46334 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756331AbcB0PqR (ORCPT ); Sat, 27 Feb 2016 10:46:17 -0500 Date: Sat, 27 Feb 2016 16:46:14 +0100 From: Andi Kleen To: Jiri Olsa Cc: Arnaldo Carvalho de Melo , Ingo Molnar , Peter Zijlstra , Andi Kleen , Stephane Eranian , Wang Nan , zheng.z.yan@intel.com, Kan Liang , LKML Subject: Re: [BUG] Core2 cpu triggers hard lockup with perf test Message-ID: <20160227154614.GL5083@two.firstfloor.org> References: <20160227123636.GB30858@krava.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160227123636.GB30858@krava.redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > I can't find what's special about Core2 CPU PEBS setup, > it seems that oher CPUs are ok (tried on ivb/snb/hsw). > > reverting the 156174999dd1 fixed the issue for me Ok multi-record PEbS was never tested on Core 2. I suppose we can enable it only on Nehalem+ -Andi -- ak@linux.intel.com -- Speaking for myself only.