From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752754AbbDRDPe (ORCPT ); Fri, 17 Apr 2015 23:15:34 -0400 Received: from ebox.rath.org ([23.92.25.96]:43425 "EHLO ebox.rath.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751703AbbDRDPc (ORCPT ); Fri, 17 Apr 2015 23:15:32 -0400 Message-ID: <5531CC47.9000008@rath.org> Date: Fri, 17 Apr 2015 20:15:19 -0700 From: Nikolaus Rath User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0 MIME-Version: 1.0 To: Mike Galbraith CC: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, "Rafael J. Wysocki" , Pavel Machek Subject: Re: Help with debugging intermittent crash on resume from hibernation References: <8761a3s1vq.fsf@vostro.rath.org> <87vbhwwdzz.fsf@vostro.rath.org> <1426823821.3150.4.camel@gmail.com> In-Reply-To: <1426823821.3150.4.camel@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/19/2015 08:57 PM, Mike Galbraith wrote: > (+CC) > > On Thu, 2015-03-19 at 20:21 -0700, Nikolaus Rath wrote: >> On Mar 13 2015, Nikolaus Rath wrote: >>> Hello, >>> >>> In about one out of 10 resumes from hibernation, my system resets after >>> the hibernation image has been loaded. I am hibernating using >>> >>> # echo platform > /sys/power/disk >>> # echo disk > /sys/power/state >>> >>> When testing hibernation using >>> >>> # echo core > /sys/power/pm_test >>> # echo platform > /sys/power/disk >>> # echo disk > /sys/power/state >>> >>> I was not able to produce the same failure. >>> >>> I then tried attaching a serial console and booted with >>> console=ttyS0,115200n8 no_console_suspend. For the failed attempt, the >>> last messages before the reset are: >> [...] >> >> I reproduced the same problem with 4.0.0-rc3. Is there anything I can do >> to get more debugging information? I also found that blacklisting the nouveau module seems to dramatically reduce the occurence of this problem (it only happened once since I blacklisted the module which is probably about ~30 resumes ago). Is there anything I can do to help debug this issue? Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«