Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753353Ab3CNWRV (ORCPT ); Thu, 14 Mar 2013 18:17:21 -0400 Received: from mail-vb0-f47.google.com ([209.85.212.47]:51828 "EHLO mail-vb0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753064Ab3CNWRU (ORCPT ); Thu, 14 Mar 2013 18:17:20 -0400 MIME-Version: 1.0 In-Reply-To: References: <20130226070247.GA14094@gmail.com> Date: Thu, 14 Mar 2013 15:17:19 -0700 X-Google-Sender-Auth: LjU9jUBrfrTvcz7olCXqR5zZbdc Message-ID: Subject: Re: [GIT PULL] perf fixes From: Linus Torvalds To: Stephane Eranian 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: 1031 Lines: 30 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. > 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. Linus -- 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/