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?
Date: Sat, 09 Aug 2014 10:59:13 +0200 [thread overview]
Message-ID: <s5hegwqghsu.wl%tiwai@suse.de> (raw)
In-Reply-To: <20140808182559.643f3b33@absurd>
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
next prev parent reply other threads:[~2014-08-09 8:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 1:51 3.16-rcX crashes on resume from Suspend-To-RAM Markus Gutschke
2014-07-17 6:50 ` Markus Gutschke
2014-07-17 8:58 ` Zhang Rui
2014-07-17 17:27 ` Markus Gutschke
2014-07-22 0:22 ` Zhang Rui
2014-07-26 15:52 ` Markus Gutschke
2014-08-04 14:16 ` Pavel Machek
2014-08-04 16:06 ` Markus Gutschke
2014-08-05 1:30 ` Rafael J. Wysocki
2014-08-05 9:58 ` 3.16 crashes on resume from Suspend-To-disk Janek Kozicki
2014-08-05 17:07 ` Janek Kozicki
2014-08-05 23:15 ` Rafael J. Wysocki
2014-08-07 9:34 ` Takashi Iwai
2014-08-08 16:25 ` 3.16 crashes on resume from Suspend-To-disk, Intel pci_bus problem? Janek Kozicki
2014-08-08 16:29 ` Janek Kozicki
2014-08-09 8:59 ` Takashi Iwai [this message]
2014-08-09 9:56 ` Janek Kozicki
2014-08-09 12:13 ` Janek Kozicki
2014-08-13 9:43 ` 3.16 crashes on resume from Suspend-To-disk Janek Kozicki
2014-08-06 12:25 ` Pavel Machek
2014-08-07 17:54 ` Janek Kozicki
2014-08-05 2:44 ` 3.16-rcX crashes on resume from Suspend-To-RAM Zhang Rui
2014-08-06 18:31 ` Markus Gutschke
2014-08-06 18:56 ` Rafael J. Wysocki
2014-08-06 19:03 ` Markus Gutschke
2014-08-09 10:14 ` Markus Gutschke
2014-08-12 8:26 ` Zhang Rui
2014-08-12 16:11 ` Markus Gutschke
2014-08-15 17:17 ` Markus Gutschke
2014-08-16 0:46 ` Rafael J. Wysocki
2014-08-16 9:54 ` Markus Gutschke
2014-08-18 1:11 ` Zhang Rui
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hegwqghsu.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=janek_listy@wp.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®