lkml.org 
[lkml]   [2014]   [Feb]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: 3.12: ethernet controller missing after resuming from suspend to RAM
Date
On Friday, February 07, 2014 12:27:03 AM you wrote:
[...]

> [ 49.170694] video LNXVIDEO:01: Restoring backlight state
> [ 49.644845] ACPI: \_SB_.AC__: ACPI_NOTIFY_BUS_CHECK event: unsupported
> [ 49.646671] jme 0000:04:00.5: irq 50 for MSI/MSI-X
> [ 49.671645] jme 0000:04:00.5 eth0: Link is down

Well, this means that Ethernet device is present after the resume.

> [ 49.671717] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 49.674119] iwlwifi 0000:05:00.0: L1 Enabled; Disabling L0S
> [ 49.681037] iwlwifi 0000:05:00.0: Radio type=0x1-0x3-0x1
> [ 49.778035] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [ 49.806241] xhci_hcd 0000:02:00.0: no hotplug settings from platform
> [ 49.859417] iwlwifi 0000:05:00.0: no hotplug settings from platform
> [ 56.264694] wlan0: authenticate with [STRIPPED]
> [ 56.277969] wlan0: send auth to [STRIPPED] (try 1/3)
> [ 56.282076] wlan0: authenticated
> [ 56.283879] wlan0: associate with [STRIPPED] (try 1/3)
> [ 56.297196] wlan0: RX AssocResp from [STRIPPED] (capab=0x411 status=0 aid=6)
> [ 56.303746] wlan0: associated
> [ 56.303826] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

Can you check the lspci differences between before/after the suspend-resume
cycle?

--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.


\
 
 \ /
  Last update: 2014-02-07 01:21    [W:0.097 / U:2.856 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site