From: Peter Wu <lekensteyn@gmail.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Bastien Traverse <bastien.traverse@gmail.com>,
linux-kernel@vger.kernel.org, francis.moro@gmail.com,
linux-pm@vger.kernel.org
Subject: Re: 3.12: ethernet controller missing after resuming from suspend to RAM
Date: Sat, 08 Feb 2014 22:34:23 +0100 [thread overview]
Message-ID: <2773460.zRzOP7I6SW@al> (raw)
In-Reply-To: <6111963.dPYocWnfhd@vostro.rjw.lan>
On Saturday 08 February 2014 16:01:36 Rafael J. Wysocki wrote:
> It looks like we fail to resume the device, then, for some reason.
>
> That may be a PCIe link issue or something similar.
>
> Is this a regression for you? If so, what's the last kernel that didn't
> have this problem? Does 3.13.y (as released by Greg, without and distro
> "improvements") have it too?
It was a regression from 3.11.x to 3.12 (and it is still broken with 3.13).
Due to some mistakes from my side, I have tested more configs:
(based on Arch Linux 3.13.1 x86_64 config)
(a) 3.13.2 with CONFIG_HOTPLUG_PCI=y, but CONFIG_HOTPLUG_PCI_ACPI=n works.
(b) 3.13.2 with CONFIG_HOTPLUG_PCI=y and CONFIG_HOTPLUG_PCI_ACPI=y is broken.
(c) 3.13.2 with CONFIG_HOTPLUG_PCI=n still works.
(my stripped config)
(d) 3.13.2 with CONFIG_HOTPLUG_PCI=y, but CONFIG_HOTPLUG_PCI_ACPI=n works.
With CONFIG_HOTPLUG_PCI_ACPI=y, the only difference in dmesg is:
(during boot)
acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
(after resume)
iwlwifi 0000:05:00.0: no hotplug settings from platform
xhci_hcd 0000:02:00.0: no hotplug settings from platform
(here, NetworkManager complains that a device has gone)
iwlwifi 0000:05:00.0: no hotplug settings from platform
Of course, with config (b), the ethernet adapter vanishes while it is still
present with configs (a), (c) and (d).
Time to do a bisect?
Peter
next prev parent reply other threads:[~2014-02-08 21:34 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52F2CC7B.80406@gmail.com>
2014-02-06 7:38 ` 3.12: ethernet controller missing after resuming from suspend to RAM Francis Moreau
2014-02-06 12:40 ` Rafael J. Wysocki
2014-02-06 13:33 ` Francis Moreau
2014-02-06 23:15 ` Bastien Traverse
2014-02-07 7:29 ` Francis Moreau
2014-02-06 21:08 ` Peter Wu
2014-02-06 23:28 ` Rafael J. Wysocki
2014-02-06 23:27 ` Peter Wu
2014-02-06 23:48 ` Rafael J. Wysocki
2014-02-07 13:43 ` Peter Wu
2014-02-08 15:01 ` Rafael J. Wysocki
2014-02-08 21:34 ` Peter Wu [this message]
2014-02-09 21:46 ` Rafael J. Wysocki
2014-02-09 23:18 ` Peter Wu
2014-02-10 0:52 ` Rafael J. Wysocki
2014-02-10 1:15 ` Peter Wu
2014-02-10 12:10 ` Rafael J. Wysocki
2014-02-10 12:20 ` Mika Westerberg
2014-02-10 22:39 ` Rafael J. Wysocki
2014-02-11 10:42 ` Mika Westerberg
2014-02-11 12:57 ` Rafael J. Wysocki
2014-02-11 18:17 ` Peter Wu
2014-02-11 23:58 ` Rafael J. Wysocki
2014-02-12 7:44 ` Francis Moreau
2014-02-12 14:04 ` Rafael J. Wysocki
2014-02-18 12:18 ` Bastien Traverse
2014-02-12 9:21 ` Mika Westerberg
2014-02-06 23:41 ` Bastien Traverse
2014-02-07 1:19 ` Rafael J. Wysocki
2014-02-09 18:44 ` Bastien Traverse
2014-02-09 22:07 ` Peter Wu
2014-02-11 18:14 ` Bastien Traverse
2014-02-10 8:17 ` Francis Moreau
[not found] <52A96D01.1050503@gmail.com>
2013-12-12 14:57 ` Rafael J. Wysocki
2013-12-12 17:43 ` Francis Moreau
2013-12-12 17:58 ` Rafael J. Wysocki
2013-12-12 19:17 ` Francis Moreau
2013-12-17 8:05 ` Francis Moreau
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=2773460.zRzOP7I6SW@al \
--to=lekensteyn@gmail.com \
--cc=bastien.traverse@gmail.com \
--cc=francis.moro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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;
as well as URLs for NNTP newsgroup(s).