Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753362Ab3CNWTQ (ORCPT ); Thu, 14 Mar 2013 18:19:16 -0400 Received: from mail-qc0-f169.google.com ([209.85.216.169]:63320 "EHLO mail-qc0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753200Ab3CNWTP (ORCPT ); Thu, 14 Mar 2013 18:19:15 -0400 MIME-Version: 1.0 In-Reply-To: References: <20130226070247.GA14094@gmail.com> Date: Thu, 14 Mar 2013 23:19:14 +0100 Message-ID: Subject: Re: [GIT PULL] perf fixes From: Stephane Eranian To: Linus Torvalds Cc: Ingo Molnar , Arnaldo Carvalho de Melo , Peter Zijlstra , Thomas Gleixner , Andrew Morton , Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1202 Lines: 34 On Thu, Mar 14, 2013 at 11:17 PM, Linus Torvalds wrote: > On Thu, Mar 14, 2013 at 3:09 PM, Stephane Eranian wrote: >> >> Could be related to suspend/resume. But were you running perf across >> that resume/suspend cycle? > > No. > > In most cases I was running a perf record before and after (but not > *while* suspending) > > In at least one other crash, I didn't run perf before at all, so the > first time I used perf was after the resume. > > So in no cases did I actually have any perf stuff active over the > suspend itself. > Ok, simpler test case then. >> Let's see if we can reproduce the problem on the same ChromeBook you >> have. Don't have one myself. > > I don't imagine it should be about chromebook per se, because afaik > all of pmu suspend/resume is done by the kernel, no firmware involved. > > So I'd assume it should happen with any IvyBridge. > Will try on a desktop IvyBridge too. -- 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/