Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: 12.10 & 13.04 Vivobook s400ca suspend issue

  1. #1
    Join Date
    Apr 2013
    Beans
    17

    12.10 & 13.04 Vivobook s400ca suspend issue

    Hi all,

    I seem to have a slight suspend issue that existed in 12.10 and still persists in 13.04.

    If I turn on my laptop (Asus Vivobook S400ca), log in, do some work (or whatever) and shut the lid, it suspends properly. Power light blinks to indicate suspend/low power mode.

    Later, I wake the laptop up, log in, do some work or whatever and shut the lid again. Now it no longer suspends the laptop. Power light remains on with a steady light indicating the machine isn't suspending. I was wondering if anyone else had this issue or had any tips. Compatibility notes at linlap indicate that suspend/resume works, but I wonder if the tester tried more then once....
    Last edited by nethfel; April 25th, 2013 at 09:40 PM. Reason: set solved prefix

  2. #2
    Join Date
    Jun 2005
    Location
    Toronto, Canada
    Beans
    Hidden!
    Distro
    Xubuntu Development Release

    Re: 12.10 & 13.04 Vivobook s400ca suspend issue

    Be curious to see the log files.

    First, clear out the existing log file:
    Code:
    sudo mv /var/log/pm-suspend.log /var/log/pm-suspend.log.BAK
    Then, suspend twice (or at least until you get the issue).

    Finally, post back a copy of that log file:
    Code:
    pastebinit /var/log/pm-suspend.log
    ...and post back the link that is generated.

    In addition, the results of the following command might also be useful:
    Code:
    cat /var/log/syslog | grep PM:

  3. #3
    Join Date
    Apr 2013
    Beans
    17

    Re: 12.10 & 13.04 Vivobook s400ca suspend issue

    Ok, here it is:

    http://paste.ubuntu.com/5602171/

    Suspend worked flawlessly the first time, opened the lid, woke up the machine, opened a web page, closed the lid, power light remained normal (full on) and machine never went to sleep. I know for sure beyond the power indicator because I have it set currently in BIOS to not wake when lid is opened and I have to normally press the power button to wake the machine up, but after the second lid close/open, power button is lit like on and mouse movement or key press causes the display to come up (backlight is on prior to pressing a key). I have tested with both the laptop in lid controlled wakeup and with power button wake up, same results (default is opening lid will wake machine)

    here's the syslog entries:

    Code:
    Apr 25 14:30:35 reliant-ub kernel: [ 1501.443637] PM: Syncing filesystems ... done.
    Apr 25 14:30:36 reliant-ub kernel: [ 1501.560791] PM: Device 0000:03:00.0 failed to suspend async: error -5
    Apr 25 14:30:36 reliant-ub kernel: [ 1501.876696] PM: Some devices failed to suspend
    Apr 25 14:30:36 reliant-ub kernel: [ 1502.210329] PM: resume of devices complete after 334.027 msecs
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000000a0000 - 0000000000100000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 0000000020000000 - 0000000020200000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 0000000040004000 - 0000000040005000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d573c000 - 00000000d573d000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d574a000 - 00000000d5d4b000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d5d4b000 - 00000000d5d4e000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d5d66000 - 00000000d5d67000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d5d68000 - 00000000d5d6e000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d5d70000 - 00000000d5d7a000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d5f10000 - 00000000d5f14000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d5f5e000 - 00000000d5f65000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d5f67000 - 00000000d5f86000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d5f89000 - 00000000d5f8b000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d5fa2000 - 00000000d5fa8000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d5fb0000 - 00000000d5fb1000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d5fc0000 - 00000000d5fc1000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d5fcc000 - 00000000d5fd1000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d5ff0000 - 00000000d5ff2000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d6007000 - 00000000d6008000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d601a000 - 00000000d6041000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d6055000 - 00000000d6056000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d6057000 - 00000000d6059000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d605a000 - 00000000d605f000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d6074000 - 00000000d661c000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d661c000 - 00000000d689c000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d689c000 - 00000000d68a1000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d68a2000 - 00000000d68e5000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d6cfd000 - 00000000d6ff4000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d7000000 - 00000000d7c00000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000d7c00000 - 00000000dfe00000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000dfe00000 - 00000000f8000000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000f8000000 - 00000000fc000000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000fc000000 - 00000000fec00000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000fec00000 - 00000000fec01000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000fec01000 - 00000000fed00000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000fed00000 - 00000000fed04000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000fed04000 - 00000000fed1c000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000fed1c000 - 00000000fed20000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000fed20000 - 00000000fee00000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000fee00000 - 00000000fee01000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000fee01000 - 00000000ff000000
    Apr 25 14:44:53 reliant-ub kernel: [    0.000000] PM: Registered nosave memory: 00000000ff000000 - 0000000100000000
    Apr 25 14:44:53 reliant-ub kernel: [    0.227216] PM: Registering ACPI NVS region [mem 0xd574a000-0xd5d4afff] (6295552 bytes)
    Apr 25 14:44:53 reliant-ub kernel: [    0.227325] PM: Registering ACPI NVS region [mem 0xd661c000-0xd689bfff] (2621440 bytes)
    Apr 25 14:44:53 reliant-ub kernel: [    0.227372] PM: Registering ACPI NVS region [mem 0xd68a2000-0xd68e4fff] (274432 bytes)
    Apr 25 14:47:24 reliant-ub kernel: [  174.411235] PM: Syncing filesystems ... done.
    Apr 25 14:47:44 reliant-ub kernel: [  174.851325] PM: suspend of devices complete after 375.435 msecs
    Apr 25 14:47:44 reliant-ub kernel: [  174.851462] PM: late suspend of devices complete after 0.134 msecs
    Apr 25 14:47:44 reliant-ub kernel: [  174.931170] PM: noirq suspend of devices complete after 79.842 msecs
    Apr 25 14:47:44 reliant-ub kernel: [  174.987265] PM: Saving platform NVS memory
    Apr 25 14:47:44 reliant-ub kernel: [  175.159587] PM: Restoring platform NVS memory
    Apr 25 14:47:44 reliant-ub kernel: [  175.394285] PM: noirq resume of devices complete after 143.714 msecs
    Apr 25 14:47:44 reliant-ub kernel: [  175.394421] PM: early resume of devices complete after 0.106 msecs
    Apr 25 14:47:44 reliant-ub kernel: [  177.917972] PM: resume of devices complete after 2527.829 msecs
    Apr 25 14:48:20 reliant-ub kernel: [  214.317574] PM: Syncing filesystems ... done.
    Apr 25 14:48:21 reliant-ub kernel: [  214.441417] PM: Device 0000:03:00.0 failed to suspend async: error -5
    Apr 25 14:48:21 reliant-ub kernel: [  214.758866] PM: Some devices failed to suspend
    Apr 25 14:48:21 reliant-ub kernel: [  215.098079] PM: resume of devices complete after 339.615 msecs
    Last edited by nethfel; April 25th, 2013 at 08:58 PM. Reason: remove excess from syslog

  4. #4
    Join Date
    Jun 2005
    Location
    Toronto, Canada
    Beans
    Hidden!
    Distro
    Xubuntu Development Release

    Re: 12.10 & 13.04 Vivobook s400ca suspend issue

    Apr 25 14:48:21 reliant-ub kernel: [ 214.441417] PM: Device 0000:03:00.0 failed to suspend async: error -5
    What device is 0000:03:00.0?
    Code:
    lspci
    ...should help to identify it.

  5. #5
    Join Date
    Apr 2013
    Beans
    17

    Re: 12.10 & 13.04 Vivobook s400ca suspend issue

    The ethernet adapter....

    nethfel@reliant-ub:~$ lspci | grep 3:00.0
    03:00.0 Ethernet controller: Qualcomm Atheros AR8161 Gigabit Ethernet (rev 10)

  6. #6
    Join Date
    Jun 2005
    Location
    Toronto, Canada
    Beans
    Hidden!
    Distro
    Xubuntu Development Release

    Re: 12.10 & 13.04 Vivobook s400ca suspend issue

    Quote Originally Posted by nethfel View Post
    The ethernet adapter....

    nethfel@reliant-ub:~$ lspci | grep 3:00.0
    03:00.0 Ethernet controller: Qualcomm Atheros AR8161 Gigabit Ethernet (rev 10)
    What modules is it using? Maybe we can force unload them.
    Code:
    sudo lspci -vnn | grep -A12 Ethernet
    ...look for "kernel driver in use"

  7. #7
    Join Date
    Apr 2013
    Beans
    17

    Re: 12.10 & 13.04 Vivobook s400ca suspend issue

    Here's what I've got:

    Code:
    03:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8161 Gigabit Ethernet [1969:1091] (rev 10)
    	Subsystem: ASUSTeK Computer Inc. Device [1043:200f]
    	Flags: bus master, fast devsel, latency 0, IRQ 19
    	Memory at f7c00000 (64-bit, non-prefetchable) [size=256K]
    	I/O ports at e000 [size=128]
    	Capabilities: [40] Power Management version 3
    	Capabilities: [58] Express Endpoint, MSI 00
    	Capabilities: [c0] MSI: Enable- Count=1/16 Maskable+ 64bit+
    	Capabilities: [d8] MSI-X: Enable- Count=16 Masked-
    	Capabilities: [100] Advanced Error Reporting
    	Capabilities: [180] Device Serial Number ff-46-89-09-74-d0-2b-ff
    	Kernel driver in use: alx
    I could blacklist the module, but I'd hate to loose my ethernet connectivity for when I need it.

  8. #8
    Join Date
    Jun 2005
    Location
    Toronto, Canada
    Beans
    Hidden!
    Distro
    Xubuntu Development Release

    Re: 12.10 & 13.04 Vivobook s400ca suspend issue

    I guess you're wireless now. Try manually unloading the ethernet driver:
    Code:
    sudo modprobe -r alx
    ...then trying a number of suspends and see if they work now.

    If so, we can force unload this module on every suspend and reload on resume.

  9. #9
    Join Date
    Apr 2013
    Beans
    17

    Re: 12.10 & 13.04 Vivobook s400ca suspend issue

    yup,, working fine now. I see a brief set of text about a resume sync but it appears to be related to the alx (I suspended/resumed several times to make sure it was working so I had an opportunity to read the message repeatedly )

    Now, my next question is where/how do I setup the system to remove/add the module on sleep/resume respectively?

  10. #10
    Join Date
    Jun 2005
    Location
    Toronto, Canada
    Beans
    Hidden!
    Distro
    Xubuntu Development Release

    Re: 12.10 & 13.04 Vivobook s400ca suspend issue

    Create the file /etc/pm/config.d/modules with the following content:
    Code:
    SUSPEND_MODULES="alx"
    That should do it.

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •