Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752302AbaJ0KuL (ORCPT ); Mon, 27 Oct 2014 06:50:11 -0400 Received: from roy.gaast.net ([80.101.33.21]:37575 "EHLO mail.gaast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751230AbaJ0KuK (ORCPT ); Mon, 27 Oct 2014 06:50:10 -0400 Message-ID: <544E235C.5010908@gaast.net> Date: Mon, 27 Oct 2014 10:50:04 +0000 From: Wilmer van der Gaast User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130112 Icedove/17.0.2 MIME-Version: 1.0 To: Yinghai Lu CC: Bjorn Helgaas , "Rafael J. Wysocki" , Pavel Machek , Rafael Wysocki , "linux-kernel@vger.kernel.org" Subject: Re: Machine crashes right *after* ~successful resume References: <543F049F.5090605@gaast.net> <543F9182.9000004@gaast.net> <544033CF.3080104@gaast.net> <5442FE58.5020700@gaast.net> <5446D2D8.2090203@gaast.net> <20141022125354.GA3832@gaast.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Yinghai, Thanks again for your time! I've applied your two patches, and as a wild guess also added pci=dump to my kernel cmdline though I guess that just gave me a boot-time dump - which mostly didn't make it into my dmesg. I accidentally booted with no_console_suspend on the first run, which still caused no output at all on the failed resume. I'm including the output of that anyway, but also I have a run with that flag removed, and annoyingly the crash appears to happen before the dump during the crash finishes - while dumping info for this device, it seems: 04:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892 (rev 10) (prog-if 01 [Subtractive decode]) (More info in my lspci.txt) Wondering what device that is exactly, I stumbled upon http://sourceforge.net/p/linux1394/mailman/message/29755048/ where someone describes it as a "cheap and crappy PCI bridge". More and more I wonder if I should just buy a new motherboard - sadly this one wasn't even that cheap. :-( Though I don't know if the output stopping while dumping output for this device means that it is the culprit, is printk() to the serial console in any way blocking/buffered? Anyway, dumps are in: http://gaast.net/~wilmer/.lkml/bad3.17-pcidumps-no_console_suspend.txt http://gaast.net/~wilmer/.lkml/bad3.17-pcidumps.txt Cheers, Wilmer van der Gaast. -- +-------- .''`. - -- ---+ + - -- --- ---- ----- ------+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---------------+ +------ ----- ---- --- -- - + -- 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/