From: Francis Moreau <francis.moro@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: 3.12: ethernet controller missing after resuming from suspend to RAM
Date: Thu, 12 Dec 2013 10:28:20 +0100 [thread overview]
Message-ID: <52A981B4.5070000@gmail.com> (raw)
In-Reply-To: <52A96D01.1050503@gmail.com>
On 12/12/2013 09:00 AM, Francis Moreau wrote:
> Hello,
>
> I'm encountering an issue after resuming my system from suspend to RAM:
> my ethernet controller is missing, it seems that the kernel doesn't see
> it anymore. It's missing from /sys/class/net.
>
> Before suspending, this is what lspci gives.
>
> 03:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 0a)
> Subsystem: CLEVO/KAPOK Computer Device 0540
> Flags: bus master, fast devsel, latency 0, IRQ 46
> I/O ports at e000 [size=256]
> Memory at f0a04000 (64-bit, prefetchable) [size=4K]
> Memory at f0a00000 (64-bit, prefetchable) [size=16K]
> Capabilities: [40] Power Management version 3
> Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
> Capabilities: [70] Express Endpoint, MSI 01
> Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
> Capabilities: [d0] Vital Product Data
> Capabilities: [100] Advanced Error Reporting
> Capabilities: [160] Device Serial Number 02-00-00-00-68-4c-e0-00
> Kernel driver in use: r8169
> Kernel modules: r8169
>
> I can't see anything obvious in dmesg.
>
> Could anybody help me to fix this ?
>
Additionnal information: I have the same symptom when doing suspend to disk.
Thanks.
next prev parent reply other threads:[~2013-12-12 9:27 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 8:00 3.12: ethernet controller missing after resuming from suspend to RAM Francis Moreau
2013-12-12 9:28 ` Francis Moreau [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2014-02-05 23:42 Bastien Traverse
2014-02-06 7:38 ` 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
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
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=52A981B4.5070000@gmail.com \
--to=francis.moro@gmail.com \
--cc=linux-kernel@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).