Re: 3.12: ethernet controller missing after resuming from suspend to RAM

[Rafael J. Wysocki]

On Thursday, December 12, 2013 06:43:03 PM Francis Moreau wrote:
> Hi Rafael,
> 
> On 12/12/2013 03:57 PM, Rafael J. Wysocki wrote:
> > On Thursday, December 12, 2013 09:00:01 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.
> > 
> > Please send a dmesg output including the first suspend-resume cycle
> > after a fresh boot (the one when you lose the NIC).
> 
> Here it is.
> 
> Actually I can see this now:
> 
> [   42.400974] r8169 0000:03:00.2: System wakeup disabled by ACPI

This should be harmless.

Please run lspci -vv before and after suspend and send both results.

Thanks,
Rafael

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/