MIME-Version: 1.0
In-Reply-To: <CABPqkBTh1Fph=GTOzN_2Q9coqLpiR3hcqVk1PBubUUEO7D=zsA@mail.gmail.com>
References: <20130226070247.GA14094@gmail.com>
	<CA+55aFxdR6_8734T9y2Edyotf0u-SgPPgjazFuQa1atSUGK9LA@mail.gmail.com>
	<CA+55aFziwaP21NVyVb_UP3okiX7fXoo4DQ7zudhxAwPM10_Tuw@mail.gmail.com>
	<CABPqkBR2HeDmuTVg5RA=5D0xXJbXxqSxMDf7MW0iCGnurQb7jw@mail.gmail.com>
	<CA+55aFzDMwHyPxqxNKRz0Y3vFhZOqtHMvPbvNXAD6C+-_=UAhg@mail.gmail.com>
	<CABPqkBTTY7RBSXJw4kqdd0c07Ykz-Wy8TFUQ+hzBSn=5v2yz2w@mail.gmail.com>
	<CABPqkBTh1Fph=GTOzN_2Q9coqLpiR3hcqVk1PBubUUEO7D=zsA@mail.gmail.com>
Date: Thu, 14 Mar 2013 23:53:37 +0100
Message-ID: <CABPqkBTQCce3ve9cP-Ajbtb7FSVggB_bL7Dmpq8KeG_7Gfx0Og@mail.gmail.com>
Subject: Re: [GIT PULL] perf fixes
From: Stephane Eranian <eranian@google.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>,
        Arnaldo Carvalho de Melo <acme@infradead.org>,
        Peter Zijlstra <a.p.zijlstra@chello.nl>,
        Thomas Gleixner <tglx@linutronix.de>,
        Andrew Morton <akpm@linux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1564
Lines: 40

On Thu, Mar 14, 2013 at 11:42 PM, Stephane Eranian <eranian@google.com> wrote:
> On Thu, Mar 14, 2013 at 11:19 PM, Stephane Eranian <eranian@google.com> wrote:
>> On Thu, Mar 14, 2013 at 11:17 PM, Linus Torvalds
>> <torvalds@linux-foundation.org> wrote:
>>> On Thu, Mar 14, 2013 at 3:09 PM, Stephane Eranian <eranian@google.com> 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.
>
> Ok, it happens on my IVB desktop too, so I can investigate...

It's not specific to IVB either, it hangs on my Nehalem desktop as well.
--
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/