From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751513AbaHII7U (ORCPT <rfc822;w@1wt.eu>);
	Sat, 9 Aug 2014 04:59:20 -0400
Received: from cantor2.suse.de ([195.135.220.15]:38708 "EHLO mx2.suse.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751249AbaHII7Q (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Sat, 9 Aug 2014 04:59:16 -0400
Date: Sat, 09 Aug 2014 10:59:13 +0200
Message-ID: <s5hegwqghsu.wl%tiwai@suse.de>
From: Takashi Iwai <tiwai@suse.de>
To: Janek Kozicki <janek_listy@wp.pl>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>, linux-kernel@vger.kernel.org,
        Zhang Rui <rui.zhang@intel.com>,
        "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
        Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: 3.16 crashes on resume from Suspend-To-disk, Intel pci_bus problem?
In-Reply-To: <20140808182559.643f3b33@absurd>
References: <CALGCz1qs2A7BCbcK3vzYRxJeOESVKc7c9kcSpP0NrQFLr1UpUg@mail.gmail.com>
	<20140805115834.5e5e76f0@absurd>
	<20140805190709.2b19c10a@absurd>
	<140743930.1Lg0eFFrXs@vostro.rjw.lan>
	<s5h4mxo3aot.wl%tiwai@suse.de>
	<20140808182559.643f3b33@absurd>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/24.3
 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

At Fri, 8 Aug 2014 18:25:59 +0200,
Janek Kozicki wrote:
> 
> Full reply, along with CONFIG_PM_TRACE_RTC=y results is below.
(snip)
>
> Now I tried to identify the problem. There are two magic numbers
> recorded in realtime clock:
> 
> pci     0000:ff:0d.1: hash matches
> pci_bus 0000:ff: hash matches
> 
> The 0000:ff: is strange, like no particular piece of hardware driver is wrong, but whole bus?
> 
> The 0000:ff:0d.1 from lspci is a following thing:
> 
> ff:0d.1 System peripheral [0880]: Intel Corporation Ivytown Unicast Registers [8086:0ee3] (rev 04)
>         Subsystem: Super Micro Computer Inc Device [15d9:0628]
>         Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
>         Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> 
> 
> So that's the best I could do so far. Currently I am waiting for more
> instructions from you on how to proceed.
> 
> PS: I am pretty sure that my hardware is not broken.

So, the PM hang problem still exists although the kernel WARNING is
gone after the patch, right?  Then the kernel WARNING was a red
herring.  It should be fixed, but it wasn't the real cause of the
hang.

I'll apply the patch to sound git tree in anyway, as it look like a
right fix for kernel WARNING.


Takashi