Quantcast
Channel: Intel Communities: Message List
Viewing all articles
Browse latest Browse all 20046

Fail to suspend Edison board - Yocto image ww42

$
0
0

Hi everyone,

 

In my seeking of low power consumption, I have tried to put the Edison board in a S3 mode (suspend to RAM).

I am doing it by

 

 

 

echo mem > /sys/power/state

 

However, the board start to suspend then fail and resume.

So I have check dmesg:

 

 

 

# dmesg


[  165.846622] CFG80211-ERROR) wl_is_linkdown : Link down Reason : WLC_E_DEAUTH
[  165.851966] cfg80211: Calling CRDA to update world regulatory domain
[  165.854519] i2c_pmic_adap i2c_pmic_adap: pmic_i2c_suspend
[  165.854553] bcove_thrm bcove_thrm: suspend called.
[  165.855091] bcmsdh_sdmmc_suspend Enter
[  165.855098] bcmsdh_sdmmc_suspend Enter
[  165.902152] bcmsdh_sdmmc_resume Enter
[  165.902186] pci_pm_suspend(): sdhci_pci_suspend+0x0/0xc0 returns -16
[  165.902206] dpm_run_callback(): pci_pm_suspend+0x0/0x1b0 returns -16
[  165.902221] PM: Device 0000:00:01.3 failed to suspend async: error -16
[  165.923411] PM: Some devices failed to suspend
[  165.923763] bcove_thrm bcove_thrm: resume called.
[  165.923789] i2c_pmic_adap i2c_pmic_adap: pmic_i2c_resume
[  166.031975] PM: resume of devices complete after 108.559 msecs
[  166.034090] PM: Finishing wakeup.
[  166.043454] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  166.034105] Restarting tasks ... done.
root@edison:/sys/power#

 

As you may notice, something goes wrong with the Device 0000:00:01.3

lspci -v

 

gave me this for this device:

 

 

 


00:01.3 SD Host controller: Intel Corporation Device 1190 (rev 01) (prog-if 01)
        Flags: bus master, fast devsel, latency 64, IRQ 38        Memory at ff3fb000 (32-bit, non-prefetchable) [size=256]        Capabilities: [b0] Power Management version 3        Capabilities: [b8] Vendor Specific Information: Len=08 <?>        Capabilities: [c0] PCI-X non-bridge device        Capabilities: [100] Vendor Specific Information: ID=0000 Rev=0 Len=024<?>        Kernel driver in use: sdhci-pci

 

Do you guys have any idea about what's wrong with this?

 

Thank you in advance.


Viewing all articles
Browse latest Browse all 20046

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>