[Bug 951548] New: system takes over a minute to fully wakeup after suspend, hibernate is even faster - openSUSE Bugs - openSUSE Mailing Lists

newer
[Bug 930048] latest krfb crashes...

[Bug 951548] New: system takes over a minute to fully wakeup after suspend, hibernate is even faster

older
[Bug 931176] Kontact crashed after...

bugzilla_noreply＠novell.com

22 Oct 2015 22 Oct '15

07:32

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 Bug ID: 951548 Summary: system takes over a minute to fully wakeup after suspend, hibernate is even faster Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 RC1 1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: abittner@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I have that other bug #boo950657 where I was reporting something slightly related On my testing system (amd apu, 32gig ram, single sata hdd, vga screen), after systemctl suspend. When it powered down, the atx power led pulsates indicating that it is sleeping in some way. And then a few seconds later I wake the machine again e.g. via keyboard keypress, it immediately semi-wakes (cpu fan rotating slower, but hdd waking again spinning up) it stays in this calmer state for over a minute, no hdd activity other than spin is being heard and no hdd led activity seen. The screen stays in powerdown mode as well all this time. After the minute+ screen wakes up the hdd does some activity audibly heard and then the login/lockscreen is being presented. I kind of figured, that hibernate mode is actually quicker for me. When I first discovered this behavior I even reset my machine after maybe like ten or twenty seconds as I had thought that suspend or sleep mode was not working at all and freezing my machine and having incompatibilities. What does the linux kernel or these power states do during this minute? Am I misunderstanding the suspend and the hibernate states? Hibernate does write the ram content to disk, doesnt it? And then powers off. As after hibernate my system goes through POST/Bios and doesnt present the grub menu but immediately boots back into the state where it left off, so reads back the ram contents from disk into memory and continues. But what does suspend actually then do so differently that it takes this long in some limbo state? Is this suspend supposed to be the same state as if I had a laptop and closing the lid? Does the linux kernel have more additional states? Maybe I am only looking for a laptop lid closed state or similar to be able to quickly recover from it. Waiting a minute to wake up is not really usable. Linux linux-ang0 4.1.10-1-default #1 SMP PREEMPT Mon Oct 12 11:24:48 UTC 2015 (67a24e6) x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are on the CC list for the bug.

Attachments:

attachment.htm (text/html — 4.2 KB)

Reply

Sign in to reply online Use email software

Show replies by date

bugzilla_noreply＠novell.com

22 Oct 22 Oct

08:26

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c1 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abittner@opensuse.org, | |tiwai@suse.com Flags| |needinfo?(abittner@opensuse | |.org) --- Comment #1 from Takashi Iwai --- Please give the detailed hardware information, and the full kernel message after suspend resume. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

08:37

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c2 --- Comment #2 from andreas bittner --- Created attachment 652751 --> http://bugzilla.opensuse.org/attachment.cgi?id=652751&action=edit dmesg output dmesg output, probably plenty of hardware information. bios is set for iommu enable, bios is latest for this board (board name: asus f2a85-m pro revision 1.03) CPU0: AMD A10-5700 APU with Radeon(tm) HD Graphics (fam: 15, model: 10, stepping: 01) -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

08:43

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c3 --- Comment #3 from andreas bittner --- via the commandline testuser@linux-ang0:~/maidsafe.org> date && systemctl suspend Thu Oct 22 10:40:24 CEST 2015 testuser@linux-ang0:~/maidsafe.org> date Thu Oct 22 10:42:01 CEST 2015 thats the total timeframe. i waited maybe two seconds after the hdd shut off, and woke the system again via space key on ps2/at keyboard. then quickly relogged in on the lockscreen and issued the second date command. the system always needs this 1+ minute timespan to wake up and is doing that hdd wakeup at the beginning of it and the slowly rotating cpu fan during this timespan. will add some logs if i find via journalctl? p.s. once i issued the systemctl suspend command via sudo, and then shut down but never woke up again. it never recovered not even after that minute+. does sudo systemctl suspend do things differently? not supposed to sudo that specific command? -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

08:48

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c4 andreas bittner changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(abittner@opensuse | |.org) | --- Comment #4 from andreas bittner --- at around 10:40, I still played with zypper ref and zypper lu, so the sleep happens after that. Here are the logs via sudo journalctl -xn 290 Oct 22 10:40:02 linux-ang0 sudo[21280]: testuser : TTY=pts/1 ; PWD=/home/testuser/maidsafe.org ; USER=root ; COMMAND=/usr/bin/zypper lu Oct 22 10:40:02 linux-ang0 sudo[21280]: pam_unix(sudo:session): session opened for user root by testuser(uid=0) Oct 22 10:40:04 linux-ang0 sudo[21280]: pam_unix(sudo:session): session closed for user root Oct 22 10:40:06 linux-ang0 sudo[21288]: testuser : TTY=pts/1 ; PWD=/home/testuser/maidsafe.org ; USER=root ; COMMAND=/usr/bin/zypper ref Oct 22 10:40:06 linux-ang0 sudo[21288]: pam_unix(sudo:session): session opened for user root by testuser(uid=0) Oct 22 10:40:09 linux-ang0 sudo[21288]: pam_unix(sudo:session): session closed for user root Oct 22 10:40:10 linux-ang0 sudo[21296]: testuser : TTY=pts/1 ; PWD=/home/testuser/maidsafe.org ; USER=root ; COMMAND=/usr/bin/zypper lu Oct 22 10:40:10 linux-ang0 sudo[21296]: pam_unix(sudo:session): session opened for user root by testuser(uid=0) Oct 22 10:40:10 linux-ang0 sudo[21296]: pam_unix(sudo:session): session closed for user root Oct 22 10:40:24 linux-ang0 polkitd[799]: Registered Authentication Agent for unix-process:21311:17105123 (system bus name :1.312 [/usr/bin/pkttyagent --notify-fd 5 --fallb Oct 22 10:40:24 linux-ang0 NetworkManager[791]: <info> sleep requested (sleeping: no enabled: yes) Oct 22 10:40:24 linux-ang0 NetworkManager[791]: <info> sleeping... Oct 22 10:40:24 linux-ang0 NetworkManager[791]: <info> (eth0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Oct 22 10:40:24 linux-ang0 polkitd[799]: Unregistered Authentication Agent for unix-process:21311:17105123 (system bus name :1.312, object path /org/freedesktop/PolicyKit1 Oct 22 10:40:24 linux-ang0 NetworkManager[791]: <info> (eth0): canceled DHCP transaction, DHCP client pid 19002 Oct 22 10:40:24 linux-ang0 NetworkManager[791]: <info> (eth0): DHCPv4 state changed bound -> done Oct 22 10:40:24 linux-ang0 NetworkManager[791]: <info> (eth0): canceled DHCP transaction Oct 22 10:40:24 linux-ang0 avahi-daemon[772]: Withdrawing address record for 2003:66:862a:2c00:5246:5dff:fe0a:9ac2 on eth0. Oct 22 10:40:24 linux-ang0 avahi-daemon[772]: Leaving mDNS multicast group on interface eth0.IPv6 with address 2003:66:862a:2c00:5246:5dff:fe0a:9ac2. Oct 22 10:40:24 linux-ang0 avahi-daemon[772]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::5246:5dff:fe0a:9ac2. Oct 22 10:40:24 linux-ang0 avahi-daemon[772]: Registering new address record for fe80::5246:5dff:fe0a:9ac2 on eth0.*. Oct 22 10:40:24 linux-ang0 avahi-daemon[772]: Withdrawing address record for fe80::5246:5dff:fe0a:9ac2 on eth0. Oct 22 10:40:24 linux-ang0 avahi-daemon[772]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::5246:5dff:fe0a:9ac2. Oct 22 10:40:24 linux-ang0 avahi-daemon[772]: Interface eth0.IPv6 no longer relevant for mDNS. Oct 22 10:40:24 linux-ang0 avahi-daemon[772]: Withdrawing address record for 192.168.178.31 on eth0. Oct 22 10:40:24 linux-ang0 avahi-daemon[772]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.178.31. Oct 22 10:40:24 linux-ang0 avahi-daemon[772]: Interface eth0.IPv4 no longer relevant for mDNS. Oct 22 10:40:24 linux-ang0 dns-resolver[21389]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... Oct 22 10:40:24 linux-ang0 dns-resolver[21391]: You can find my version in /etc/resolv.conf.netconfig Oct 22 10:40:24 linux-ang0 NetworkManager[791]: dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... Oct 22 10:40:24 linux-ang0 NetworkManager[791]: dns-resolver: You can find my version in /etc/resolv.conf.netconfig Oct 22 10:40:24 linux-ang0 NetworkManager[791]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... Oct 22 10:40:24 linux-ang0 NetworkManager[791]: You can find my version in /etc/resolv.conf.netconfig ... Oct 22 10:40:24 linux-ang0 dns-resolver[21566]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... Oct 22 10:40:24 linux-ang0 dns-resolver[21568]: You can find my version in /etc/resolv.conf.netconfig Oct 22 10:40:25 linux-ang0 NetworkManager[791]: dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... Oct 22 10:40:25 linux-ang0 NetworkManager[791]: dns-resolver: You can find my version in /etc/resolv.conf.netconfig Oct 22 10:40:25 linux-ang0 NetworkManager[791]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... Oct 22 10:40:25 linux-ang0 NetworkManager[791]: You can find my version in /etc/resolv.conf.netconfig ... Oct 22 10:40:25 linux-ang0 NetworkManager[791]: <info> NetworkManager state is now ASLEEP Oct 22 10:40:25 linux-ang0 kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Oct 22 10:40:25 linux-ang0 dbus[770]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Oct 22 10:40:25 linux-ang0 NetworkManager[791]: <info> (eth0): link disconnected Oct 22 10:40:25 linux-ang0 dbus[770]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Oct 22 10:40:25 linux-ang0 nm-dispatcher[21673]: Dispatching action 'down' for eth0 Oct 22 10:40:25 linux-ang0 kernel: PM: Syncing filesystems ... done. Oct 22 10:40:25 linux-ang0 kernel: PM: Preparing system for mem sleep Oct 22 10:41:55 linux-ang0 kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Oct 22 10:41:55 linux-ang0 kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Oct 22 10:41:55 linux-ang0 kernel: PM: Entering mem sleep Oct 22 10:41:55 linux-ang0 kernel: Suspending console(s) (use no_console_suspend to debug) Oct 22 10:41:55 linux-ang0 kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Oct 22 10:41:55 linux-ang0 kernel: sd 0:0:0:0: [sda] Stopping disk Oct 22 10:41:55 linux-ang0 kernel: serial 00:09: disabled Oct 22 10:41:55 linux-ang0 kernel: serial 00:09: System wakeup disabled by ACPI Oct 22 10:41:55 linux-ang0 kernel: i8042 kbd 00:08: System wakeup enabled by ACPI Oct 22 10:41:55 linux-ang0 kernel: PM: suspend of devices complete after 859.482 msecs Oct 22 10:41:55 linux-ang0 kernel: PM: late suspend of devices complete after 0.616 msecs Oct 22 10:41:55 linux-ang0 kernel: pcieport 0000:00:15.1: System wakeup enabled by ACPI Oct 22 10:41:55 linux-ang0 kernel: ohci-pci 0000:00:13.0: System wakeup enabled by ACPI Oct 22 10:41:55 linux-ang0 kernel: ehci-pci 0000:00:13.2: System wakeup enabled by ACPI Oct 22 10:41:55 linux-ang0 kernel: ehci-pci 0000:00:12.2: System wakeup enabled by ACPI Oct 22 10:41:55 linux-ang0 kernel: ohci-pci 0000:00:12.0: System wakeup enabled by ACPI Oct 22 10:41:55 linux-ang0 kernel: xhci_hcd 0000:00:10.1: System wakeup enabled by ACPI Oct 22 10:41:55 linux-ang0 kernel: xhci_hcd 0000:00:10.0: System wakeup enabled by ACPI Oct 22 10:41:55 linux-ang0 kernel: PM: noirq suspend of devices complete after 15.450 msecs Oct 22 10:41:55 linux-ang0 kernel: ACPI: Preparing to enter system sleep state S3 Oct 22 10:41:55 linux-ang0 kernel: ACPI : EC: EC stopped Oct 22 10:41:55 linux-ang0 kernel: PM: Saving platform NVS memory Oct 22 10:41:55 linux-ang0 kernel: Disabling non-boot CPUs ... Oct 22 10:41:55 linux-ang0 kernel: kvm: disabling virtualization on CPU1 Oct 22 10:41:55 linux-ang0 kernel: smpboot: CPU 1 is now offline Oct 22 10:41:55 linux-ang0 kernel: kvm: disabling virtualization on CPU2 Oct 22 10:41:55 linux-ang0 kernel: smpboot: CPU 2 is now offline Oct 22 10:41:55 linux-ang0 kernel: kvm: disabling virtualization on CPU3 Oct 22 10:41:55 linux-ang0 kernel: smpboot: CPU 3 is now offline Oct 22 10:41:55 linux-ang0 kernel: ACPI: Low-level resume complete Oct 22 10:41:55 linux-ang0 kernel: ACPI : EC: EC started Oct 22 10:41:55 linux-ang0 kernel: PM: Restoring platform NVS memory Oct 22 10:41:55 linux-ang0 kernel: Using NULL legacy PIC Oct 22 10:41:55 linux-ang0 kernel: LVT offset 0 assigned for vector 0x400 Oct 22 10:41:55 linux-ang0 kernel: [Firmware Bug]: cpu 0, try to use APIC500 (LVT offset 0) for vector 0xf9, but the register is already in use for vector 0x400 on another Oct 22 10:41:55 linux-ang0 kernel: [Firmware Bug]: cpu 0, failed to setup threshold interrupt for bank 4, block 0 (MSR00000413=0xc000000001000000) Oct 22 10:41:55 linux-ang0 kernel: [Firmware Bug]: cpu 0, try to use APIC500 (LVT offset 0) for vector 0xf9, but the register is already in use for vector 0x400 on another Oct 22 10:41:55 linux-ang0 kernel: [Firmware Bug]: cpu 0, failed to setup threshold interrupt for bank 4, block 1 (MSRC0000408=0xc000000001000000) Oct 22 10:41:55 linux-ang0 kernel: Enabling non-boot CPUs ... Oct 22 10:41:55 linux-ang0 kernel: x86: Booting SMP configuration: Oct 22 10:41:55 linux-ang0 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x11 Oct 22 10:41:55 linux-ang0 kernel: kvm: enabling virtualization on CPU1 Oct 22 10:41:55 linux-ang0 kernel: cache: parent cpu1 should not be sleeping Oct 22 10:41:55 linux-ang0 kernel: CPU1 is up Oct 22 10:41:55 linux-ang0 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x12 Oct 22 10:41:55 linux-ang0 kernel: kvm: enabling virtualization on CPU2 Oct 22 10:41:55 linux-ang0 kernel: cache: parent cpu2 should not be sleeping Oct 22 10:41:55 linux-ang0 kernel: CPU2 is up Oct 22 10:41:55 linux-ang0 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x13 Oct 22 10:41:55 linux-ang0 kernel: kvm: enabling virtualization on CPU3 Oct 22 10:41:55 linux-ang0 kernel: cache: parent cpu3 should not be sleeping Oct 22 10:41:55 linux-ang0 kernel: CPU3 is up Oct 22 10:41:55 linux-ang0 kernel: ACPI: Waking up from system sleep state S3 Oct 22 10:41:55 linux-ang0 kernel: ohci-pci 0000:00:12.0: System wakeup disabled by ACPI Oct 22 10:41:55 linux-ang0 kernel: ohci-pci 0000:00:13.0: System wakeup disabled by ACPI Oct 22 10:41:55 linux-ang0 kernel: ehci-pci 0000:00:13.2: System wakeup disabled by ACPI Oct 22 10:41:55 linux-ang0 kernel: xhci_hcd 0000:00:10.0: System wakeup disabled by ACPI Oct 22 10:41:55 linux-ang0 kernel: ehci-pci 0000:00:12.2: System wakeup disabled by ACPI Oct 22 10:41:55 linux-ang0 kernel: xhci_hcd 0000:00:10.1: System wakeup disabled by ACPI Oct 22 10:41:55 linux-ang0 kernel: pcieport 0000:00:15.1: System wakeup disabled by ACPI Oct 22 10:41:55 linux-ang0 kernel: PM: noirq resume of devices complete after 13.591 msecs Oct 22 10:41:55 linux-ang0 kernel: PM: early resume of devices complete after 0.517 msecs Oct 22 10:41:55 linux-ang0 kernel: rtc_cmos 00:05: System wakeup disabled by ACPI Oct 22 10:41:55 linux-ang0 kernel: usb usb5: root hub lost power or was reset Oct 22 10:41:55 linux-ang0 kernel: usb usb6: root hub lost power or was reset Oct 22 10:41:55 linux-ang0 kernel: i8042 kbd 00:08: System wakeup disabled by ACPI Oct 22 10:41:55 linux-ang0 kernel: serial 00:09: activated Oct 22 10:41:55 linux-ang0 kernel: [drm] PCIE GART of 1024M enabled (table at 0x0000000000277000). Oct 22 10:41:55 linux-ang0 kernel: radeon 0000:00:01.0: WB enabled Oct 22 10:41:55 linux-ang0 kernel: radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000030000c00 and cpu addr 0xffff880816b20c00 Oct 22 10:41:55 linux-ang0 kernel: radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90004035a18 Oct 22 10:41:55 linux-ang0 kernel: radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000030000c04 and cpu addr 0xffff880816b20c04 Oct 22 10:41:55 linux-ang0 kernel: radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000030000c08 and cpu addr 0xffff880816b20c08 Oct 22 10:41:55 linux-ang0 kernel: radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000030000c0c and cpu addr 0xffff880816b20c0c Oct 22 10:41:55 linux-ang0 kernel: radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000030000c10 and cpu addr 0xffff880816b20c10 Oct 22 10:41:55 linux-ang0 kernel: [drm] ring test on 0 succeeded in 1 usecs Oct 22 10:41:55 linux-ang0 kernel: [drm] ring test on 3 succeeded in 2 usecs Oct 22 10:41:55 linux-ang0 kernel: [drm] ring test on 4 succeeded in 2 usecs Oct 22 10:41:55 linux-ang0 kernel: usb usb9: root hub lost power or was reset Oct 22 10:41:55 linux-ang0 kernel: sd 0:0:0:0: [sda] Starting disk Oct 22 10:41:55 linux-ang0 kernel: [drm] ring test on 5 succeeded in 2 usecs Oct 22 10:41:55 linux-ang0 kernel: [drm] UVD initialized successfully. Oct 22 10:41:55 linux-ang0 kernel: [drm] ib test on ring 0 succeeded in 0 usecs Oct 22 10:41:55 linux-ang0 kernel: [drm] ib test on ring 3 succeeded in 0 usecs Oct 22 10:41:55 linux-ang0 kernel: [drm] ib test on ring 4 succeeded in 0 usecs Oct 22 10:41:55 linux-ang0 kernel: [drm] ib test on ring 5 succeeded Oct 22 10:41:55 linux-ang0 kernel: ata8: SATA link down (SStatus 0 SControl 300) Oct 22 10:41:55 linux-ang0 kernel: ata2: SATA link down (SStatus 0 SControl 300) Oct 22 10:41:55 linux-ang0 kernel: ata4: SATA link down (SStatus 0 SControl 300) Oct 22 10:41:55 linux-ang0 kernel: ata6: SATA link down (SStatus 0 SControl 300) Oct 22 10:41:55 linux-ang0 kernel: ata7: SATA link down (SStatus 0 SControl 300) Oct 22 10:41:55 linux-ang0 kernel: ata3: SATA link down (SStatus 0 SControl 300) Oct 22 10:41:55 linux-ang0 kernel: ata5: SATA link down (SStatus 0 SControl 300) Oct 22 10:41:55 linux-ang0 kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 22 10:41:55 linux-ang0 kernel: ata1.00: configured for UDMA/133 Oct 22 10:41:55 linux-ang0 kernel: usb 9-2: reset low-speed USB device number 2 using ohci-pci Oct 22 10:41:55 linux-ang0 kernel: PM: resume of devices complete after 955.171 msecs Oct 22 10:41:55 linux-ang0 kernel: PM: Finishing wakeup. Oct 22 10:41:55 linux-ang0 kernel: Restarting tasks ... done. Oct 22 10:41:55 linux-ang0 NetworkManager[791]: <info> wake requested (sleeping: yes enabled: yes) Oct 22 10:41:55 linux-ang0 NetworkManager[791]: <info> waking up... Oct 22 10:41:55 linux-ang0 NetworkManager[791]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Oct 22 10:41:55 linux-ang0 kernel: r8169 0000:04:00.0 eth0: link down Oct 22 10:41:55 linux-ang0 NetworkManager[791]: <info> NetworkManager state is now DISCONNECTED Oct 22 10:41:58 linux-ang0 kernel: r8169 0000:04:00.0 eth0: link up Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> (eth0): link connected Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40] Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> Auto-activating connection 'Wired connection 1'. Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> (eth0): Activation: starting connection 'Wired connection 1' (0c9f22ac-1576-4ada-bb4e-fe75e50ac867) Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> NetworkManager state is now CONNECTING Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0] Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0] Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds) Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> dhclient started with pid 21760 Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> address 192.168.178.31 Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> plen 24 (255.255.255.0) Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> gateway 192.168.178.1 Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> server identifier 192.168.178.1 Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> lease time 864000 Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> nameserver '192.168.178.1' Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> domain name 'fritz.box' Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> (eth0): DHCPv4 state changed unknown -> bound Oct 22 10:41:58 linux-ang0 avahi-daemon[772]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.31. ct 22 10:41:58 linux-ang0 avahi-daemon[772]: New relevant interface eth0.IPv4 for mDNS. Oct 22 10:41:58 linux-ang0 avahi-daemon[772]: Registering new address record for 192.168.178.31 on eth0.IPv4. Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> (eth0): device state change: ip-config -> ip-check (reason 'none') [70 80 0] Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> (eth0): device state change: ip-check -> secondaries (reason 'none') [80 90 0] Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0] Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> NetworkManager state is now CONNECTED_LOCAL Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> NetworkManager state is now CONNECTED_GLOBAL Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> Policy set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS. Oct 22 10:41:58 linux-ang0 dns-resolver[21836]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... Oct 22 10:41:58 linux-ang0 dns-resolver[21838]: You can find my version in /etc/resolv.conf.netconfig Oct 22 10:41:58 linux-ang0 NetworkManager[791]: dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... Oct 22 10:41:58 linux-ang0 NetworkManager[791]: dns-resolver: You can find my version in /etc/resolv.conf.netconfig Oct 22 10:41:58 linux-ang0 NetworkManager[791]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... Oct 22 10:41:58 linux-ang0 NetworkManager[791]: You can find my version in /etc/resolv.conf.netconfig ... Oct 22 10:41:58 linux-ang0 NetworkManager[791]: <info> (eth0): Activation: successful, device activated. Oct 22 10:41:58 linux-ang0 nm-dispatcher[21673]: Dispatching action 'up' for eth0 Oct 22 10:41:59 linux-ang0 avahi-daemon[772]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::5246:5dff:fe0a:9ac2. Oct 22 10:41:59 linux-ang0 avahi-daemon[772]: New relevant interface eth0.IPv6 for mDNS. Oct 22 10:41:59 linux-ang0 avahi-daemon[772]: Registering new address record for fe80::5246:5dff:fe0a:9ac2 on eth0.*. Oct 22 10:42:00 linux-ang0 NetworkManager[791]: <info> Activation (eth0) Beginning DHCPv6 transaction (timeout in 45 seconds) Oct 22 10:42:00 linux-ang0 NetworkManager[791]: <info> dhclient started with pid 21953 Oct 22 10:42:00 linux-ang0 NetworkManager[791]: <info> nameserver 'fd00::be05:43ff:fee6:cd1' Oct 22 10:42:00 linux-ang0 NetworkManager[791]: <info> (eth0): DHCPv6 state changed unknown -> bound Oct 22 10:42:00 linux-ang0 NetworkManager[791]: <info> Policy set 'Wired connection 1' (eth0) as default for IPv6 routing and DNS. Oct 22 10:42:00 linux-ang0 dns-resolver[22026]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... Oct 22 10:42:00 linux-ang0 dns-resolver[22028]: You can find my version in /etc/resolv.conf.netconfig Oct 22 10:42:00 linux-ang0 NetworkManager[791]: dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... Oct 22 10:42:00 linux-ang0 NetworkManager[791]: dns-resolver: You can find my version in /etc/resolv.conf.netconfig Oct 22 10:42:00 linux-ang0 NetworkManager[791]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... Oct 22 10:42:00 linux-ang0 NetworkManager[791]: You can find my version in /etc/resolv.conf.netconfig ... Oct 22 10:42:01 linux-ang0 NetworkManager[791]: <info> (eth0): DHCPv6 client pid 21953 exited with status 0 Oct 22 10:42:01 linux-ang0 NetworkManager[791]: <info> (eth0): DHCPv6 state changed bound -> done Oct 22 10:42:01 linux-ang0 nm-dispatcher[21673]: Dispatching action 'dhcp6-change' for eth0 Oct 22 10:42:02 linux-ang0 avahi-daemon[772]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::5246:5dff:fe0a:9ac2. Oct 22 10:42:02 linux-ang0 avahi-daemon[772]: Joining mDNS multicast group on interface eth0.IPv6 with address 2003:66:862a:2c00:5246:5dff:fe0a:9ac2. Oct 22 10:42:02 linux-ang0 avahi-daemon[772]: Registering new address record for 2003:66:862a:2c00:5246:5dff:fe0a:9ac2 on eth0.*. Oct 22 10:42:02 linux-ang0 avahi-daemon[772]: Withdrawing address record for fe80::5246:5dff:fe0a:9ac2 on eth0. Oct 22 10:45:01 linux-ang0 cron[22149]: pam_unix(crond:session): session opened for user root by (uid=0) Oct 22 10:45:01 linux-ang0 systemd[22150]: pam_unix(systemd-user:session): session opened for user root by (uid=0) Oct 22 10:45:01 linux-ang0 CRON[22149]: pam_unix(crond:session): session closed for user root Oct 22 10:45:01 linux-ang0 systemd[22151]: pam_unix(systemd-user:session): session closed for user root Oct 22 10:45:16 linux-ang0 sudo[22180]: testuser : TTY=pts/1 ; PWD=/home/testuser/maidsafe.org ; USER=root ; COMMAND=/usr/bin/journalctl -xn 20 Oct 22 10:45:16 linux-ang0 sudo[22180]: pam_unix(sudo:session): session opened for user root by testuser(uid=0) Oct 22 10:45:16 linux-ang0 sudo[22180]: pam_unix(sudo:session): session closed for user root Oct 22 10:45:31 linux-ang0 sudo[22185]: testuser : TTY=pts/1 ; PWD=/home/testuser/maidsafe.org ; USER=root ; COMMAND=/usr/bin/journalctl -xn 40 Oct 22 10:45:31 linux-ang0 sudo[22185]: pam_unix(sudo:session): session opened for user root by testuser(uid=0) Oct 22 10:45:31 linux-ang0 sudo[22185]: pam_unix(sudo:session): session closed for user root Oct 22 10:45:41 linux-ang0 sudo[22193]: testuser : TTY=pts/1 ; PWD=/home/testuser/maidsafe.org ; USER=root ; COMMAND=/usr/bin/journalctl -xn 90 Oct 22 10:45:41 linux-ang0 sudo[22193]: pam_unix(sudo:session): session opened for user root by testuser(uid=0) Oct 22 10:45:45 linux-ang0 sudo[22193]: pam_unix(sudo:session): session closed for user root Oct 22 10:45:51 linux-ang0 sudo[22201]: testuser : TTY=pts/1 ; PWD=/home/testuser/maidsafe.org ; USER=root ; COMMAND=/usr/bin/journalctl -xn 190 Oct 22 10:45:51 linux-ang0 sudo[22201]: pam_unix(sudo:session): session opened for user root by testuser(uid=0) Oct 22 10:46:12 linux-ang0 sudo[22201]: pam_unix(sudo:session): session closed for user root Oct 22 10:46:15 linux-ang0 sudo[22206]: testuser : TTY=pts/1 ; PWD=/home/testuser/maidsafe.org ; USER=root ; COMMAND=/usr/bin/journalctl -xn 290 Oct 22 10:46:15 linux-ang0 sudo[22206]: pam_unix(sudo:session): session opened for user root by testuser(uid=0) -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

09:31

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c5 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(abittner@opensuse | |.org) --- Comment #5 from Takashi Iwai --- Please give the detailed hardware information, e.g. the output of "hwinfo --all". Does the suspend itself takes time, or does it only resume after suspend taking time? The log looks fairly confusing as if you started resume immediately after suspend. Do one clean boot, go to suspend. Wait for one minute, and resume. Then give dmesg output, and attach again. Also, please avoid pasting too much texts in the form. This worsens the readability of the bug report pretty much. Keep concise (and accurate) as much as possible. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

09:38

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c6 --- Comment #6 from andreas bittner --- Yes I had been confused by the logoutput already yesterday. It always looks the same. But the suspend is pretty much immediate. I issue it as nonroot from a konsole (kde) and then I briefly see the lockscreen and then the system goes down becomes silent, the screen goes to powersave (dpms or whatever) and the disk spinning stops and the cpu fan turns off and the atx power led starts to pulsate. The waking is what takes long. Pressing space or any key does start up the disk again pretty immediately but the cpu fan only into slowly rotating mode and then it stays there for a minute. There is brief activity on disk (after respin) but only very little, no further activity of the disk being heard or being seen of the hdd led. the disk spins normally of course all the time. after a minute or so the display begins to wake (back from dpms or whatever) and then there is some disk activty at that time, and the cpu fan goes back to normal (fuller) rotating speed and the lock screen is seen again. i did log in immediately again and issued that second date command, so there ought to be only like maybe 2-3 seconds delay of that timespan measurement to give you the idea of what delay (1+ minute) we are talking about here. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

09:40

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c7 andreas bittner changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(abittner@opensuse | |.org) | --- Comment #7 from andreas bittner --- Created attachment 652757 --> http://bugzilla.opensuse.org/attachment.cgi?id=652757&action=edit redirected output of: sudo hwinfo --all redirected output of: sudo hwinfo --all sudo hwinfo --all output of the system i am running the suspend and wake -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

09:52

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c8 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(abittner@opensuse | |.org) --- Comment #8 from Takashi Iwai --- And give dmesg output in the procedure I requested. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

09:57

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c9 andreas bittner changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(abittner@opensuse | |.org) | --- Comment #9 from andreas bittner --- I already gave the dmesg output, its still the same. after timestamp 34361..... here are the other lines. Thats all there is, no more output than this in dmesg. [34361.057017] r8169 0000:04:00.0 eth0: link up [39049.566260] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [39049.781016] PM: Syncing filesystems ... done. [39050.335193] PM: Preparing system for mem sleep [39050.572357] Freezing user space processes ... (elapsed 0.002 seconds) done. [39050.574597] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [39050.576071] PM: Entering mem sleep [39050.576104] Suspending console(s) (use no_console_suspend to debug) [39050.577221] sd 0:0:0:0: [sda] Synchronizing SCSI cache [39050.577316] sd 0:0:0:0: [sda] Stopping disk [39050.603800] serial 00:09: disabled [39050.603814] serial 00:09: System wakeup disabled by ACPI [39050.603859] i8042 kbd 00:08: System wakeup enabled by ACPI [39051.435611] PM: suspend of devices complete after 859.482 msecs [39051.436230] PM: late suspend of devices complete after 0.616 msecs [39051.436812] pcieport 0000:00:15.1: System wakeup enabled by ACPI [39051.437168] ohci-pci 0000:00:13.0: System wakeup enabled by ACPI [39051.437170] ehci-pci 0000:00:13.2: System wakeup enabled by ACPI [39051.437186] ehci-pci 0000:00:12.2: System wakeup enabled by ACPI [39051.437188] ohci-pci 0000:00:12.0: System wakeup enabled by ACPI [39051.437342] xhci_hcd 0000:00:10.1: System wakeup enabled by ACPI [39051.437390] xhci_hcd 0000:00:10.0: System wakeup enabled by ACPI [39051.451677] PM: noirq suspend of devices complete after 15.450 msecs [39051.451819] ACPI: Preparing to enter system sleep state S3 [39051.454504] ACPI : EC: EC stopped [39051.454504] PM: Saving platform NVS memory [39051.454516] Disabling non-boot CPUs ... [39051.455902] kvm: disabling virtualization on CPU1 [39051.456183] smpboot: CPU 1 is now offline [39051.457995] kvm: disabling virtualization on CPU2 [39051.458009] smpboot: CPU 2 is now offline [39051.459704] kvm: disabling virtualization on CPU3 [39051.459722] smpboot: CPU 3 is now offline [39051.460392] ACPI: Low-level resume complete [39051.460430] ACPI : EC: EC started [39051.460431] PM: Restoring platform NVS memory [39051.460467] Using NULL legacy PIC [39051.460519] LVT offset 0 assigned for vector 0x400 [39051.460576] [Firmware Bug]: cpu 0, try to use APIC500 (LVT offset 0) for vector 0xf9, but the register is already in use for vector 0x400 on another cpu [39051.460577] [Firmware Bug]: cpu 0, failed to setup threshold interrupt for bank 4, block 0 (MSR00000413=0xc000000001000000) [39051.460578] [Firmware Bug]: cpu 0, try to use APIC500 (LVT offset 0) for vector 0xf9, but the register is already in use for vector 0x400 on another cpu [39051.460579] [Firmware Bug]: cpu 0, failed to setup threshold interrupt for bank 4, block 1 (MSRC0000408=0xc000000001000000) [39051.460592] Enabling non-boot CPUs ... [39051.460647] x86: Booting SMP configuration: [39051.460648] smpboot: Booting Node 0 Processor 1 APIC 0x11 [39051.471669] kvm: enabling virtualization on CPU1 [39051.473877] cache: parent cpu1 should not be sleeping [39051.474114] CPU1 is up [39051.474153] smpboot: Booting Node 0 Processor 2 APIC 0x12 [39051.485121] kvm: enabling virtualization on CPU2 [39051.487284] cache: parent cpu2 should not be sleeping [39051.487526] CPU2 is up [39051.487579] smpboot: Booting Node 0 Processor 3 APIC 0x13 [39051.498546] kvm: enabling virtualization on CPU3 [39051.500796] cache: parent cpu3 should not be sleeping [39051.501044] CPU3 is up [39051.501572] ACPI: Waking up from system sleep state S3 [39051.503140] ohci-pci 0000:00:12.0: System wakeup disabled by ACPI [39051.503141] ohci-pci 0000:00:13.0: System wakeup disabled by ACPI [39051.516125] ehci-pci 0000:00:13.2: System wakeup disabled by ACPI [39051.516193] xhci_hcd 0000:00:10.0: System wakeup disabled by ACPI [39051.516338] ehci-pci 0000:00:12.2: System wakeup disabled by ACPI [39051.516391] xhci_hcd 0000:00:10.1: System wakeup disabled by ACPI [39051.516499] pcieport 0000:00:15.1: System wakeup disabled by ACPI [39051.516545] PM: noirq resume of devices complete after 13.591 msecs [39051.517106] PM: early resume of devices complete after 0.517 msecs [39051.520035] rtc_cmos 00:05: System wakeup disabled by ACPI [39051.520044] usb usb5: root hub lost power or was reset [39051.520047] usb usb6: root hub lost power or was reset [39051.520104] i8042 kbd 00:08: System wakeup disabled by ACPI [39051.521218] serial 00:09: activated [39051.537860] [drm] PCIE GART of 1024M enabled (table at 0x0000000000277000). [39051.537999] radeon 0000:00:01.0: WB enabled [39051.538003] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000030000c00 and cpu addr 0xffff880816b20c00 [39051.538778] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90004035a18 [39051.538781] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000030000c04 and cpu addr 0xffff880816b20c04 [39051.538785] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000030000c08 and cpu addr 0xffff880816b20c08 [39051.538788] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000030000c0c and cpu addr 0xffff880816b20c0c [39051.538792] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000030000c10 and cpu addr 0xffff880816b20c10 [39051.557434] [drm] ring test on 0 succeeded in 1 usecs [39051.557447] [drm] ring test on 3 succeeded in 2 usecs [39051.557455] [drm] ring test on 4 succeeded in 2 usecs [39051.583373] usb usb9: root hub lost power or was reset [39051.583689] sd 0:0:0:0: [sda] Starting disk [39051.603125] [drm] ring test on 5 succeeded in 2 usecs [39051.622970] [drm] UVD initialized successfully. [39051.623499] [drm] ib test on ring 0 succeeded in 0 usecs [39051.624043] [drm] ib test on ring 3 succeeded in 0 usecs [39051.624565] [drm] ib test on ring 4 succeeded in 0 usecs [39051.644940] [drm] ib test on ring 5 succeeded [39051.855718] ata8: SATA link down (SStatus 0 SControl 300) [39051.855779] ata2: SATA link down (SStatus 0 SControl 300) [39051.855820] ata4: SATA link down (SStatus 0 SControl 300) [39051.855843] ata6: SATA link down (SStatus 0 SControl 300) [39051.855865] ata7: SATA link down (SStatus 0 SControl 300) [39051.855887] ata3: SATA link down (SStatus 0 SControl 300) [39051.899783] ata5: SATA link down (SStatus 0 SControl 300) [39052.027712] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [39052.038883] ata1.00: configured for UDMA/133 [39052.155632] usb 9-2: reset low-speed USB device number 2 using ohci-pci [39052.471770] PM: resume of devices complete after 955.171 msecs [39052.472280] PM: Finishing wakeup. [39052.472282] Restarting tasks ... done. [39052.602289] r8169 0000:04:00.0 eth0: link down [39055.456336] r8169 0000:04:00.0 eth0: link up [42525.586110] ppdev: user-space parallel port driver [42525.597306] lp: driver loaded but no devices found [42525.794982] lp: driver loaded but no devices found [42525.848682] st: Version 20101219, fixed bufsize 32768, s/g segs 256 [42525.928649] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

10:02

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c10 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(abittner@opensuse | |.org) --- Comment #10 from Takashi Iwai --- (In reply to andreas bittner from comment #9)

I already gave the dmesg output, its still the same.

It can't be the same. Your previous log shows multiple times of S3. This is utterly confusing. Please give the exactly requested information. (And, again, don't paste too long texts, it just worsens the readability VERY MUCH.) -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

10:11

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c11 --- Comment #11 from andreas bittner --- But what do you mean exactly? Dmesg output is constantly growing. Thats how I understand it. I attached a dmesg.log, that was all until that moment that I had, and then I pasted the rest of the lines that the output grew since then. What do you need exactly? And when should I execute what command if it does make a difference according to your statement? what command exactly as which user and at what moment? -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

10:18

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c12 andreas bittner changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(abittner@opensuse | |.org) | --- Comment #12 from andreas bittner --- Created attachment 652768 --> http://bugzilla.opensuse.org/attachment.cgi?id=652768&action=edit sudo dmesg output after 2days uptime of this system sudo dmesg output after 2days uptime of this system the systemctl suspend and wakings happened on this machine which as 2+ days of uptime at this moment. that is all dmesg output that exists -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

10:42

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c13 --- Comment #13 from Takashi Iwai --- (In reply to andreas bittner from comment #11)

But what do you mean exactly? Dmesg output is constantly growing. Thats how I understand it. I attached a dmesg.log, that was all until that moment that I had, and then I pasted the rest of the lines that the output grew since then.

In comment 5: "Do one clean boot, go to suspend. Wait for one minute, and resume. Then give dmesg output, and attach again." -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

10:47

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c14 --- Comment #14 from andreas bittner --- sudo shutdown Broadcast message from root@linux-ang0 (Thu 2015-10-22 12:47:26 CEST): The system is going down for power-off at Thu 2015-10-22 12:48:26 CEST! (system sill has my firefox and doesnt do anything :( i can still submit these lines in the bugtracker -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

11:13

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c15 --- Comment #15 from andreas bittner --- it took some more seconds until the kde vanished and apparently it was still enough time to submit that message. anyways, here is the system back with fresh uptime. never logged into kde and altf2 console screen with root, and saved the dmesg right after root login, then systemctl suspend the waited a few minutes then pressing space on keyboard then after 1+ minute just the same the altf2 screen came back and i saved dmesg again into second file first dmesg file right after reboot is from: Thu Oct 22 13:03:03 CEST 2015 second dmesg (after wakeup) is from: Thu Oct 22 13:07:56 CEST 2015 both timestamps are in the files. the first file has the timestamp at the end, the second file has the timestamp (twice) at the very beginning. submitting files immediately. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

11:14

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c16 --- Comment #16 from andreas bittner --- Created attachment 652789 --> http://bugzilla.opensuse.org/attachment.cgi?id=652789&action=edit clean boot, dmesg output clean boot, dmesg output -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

11:15

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c17 --- Comment #17 from andreas bittner --- Created attachment 652790 --> http://bugzilla.opensuse.org/attachment.cgi?id=652790&action=edit dmesg output after systemctl suspend (for a few minutes) then wake again dmesg output after systemctl suspend (for a few minutes) then wake again timestamps are in the files (at the beginning of this file) and at the end of the clean boot file. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

15:00

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c18 --- Comment #18 from Takashi Iwai --- Hm, the log doesn't show any delay. [ 117.356037] PM: suspend of devices complete after 476.643 msecs [ 117.357049] PM: late suspend of devices complete after 1.008 msecs At this point the suspend finished. Then it resumes: [ 117.358077] pcieport 0000:00:15.1: System wakeup enabled by ACPI [ 117.358447] ehci-pci 0000:00:13.2: System wakeup enabled by ACPI .... [ 118.397519] Restarting tasks ... done. At this point, user-space is already woken up. So it took less than a second. And, the next (and the last) log shows that the system is up, the Ethernet detected: [ 120.361383] r8169 0000:04:00.0 eth0: link up That said, from the kernel POV, everything looks good. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

16:31

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c19 --- Comment #19 from andreas bittner --- do i need to make a video of the system? it is as i wrote. i cannot help it. i already looked into the logs yesterday and it was odd for me as well. is there any way to enable some more logging of the kernel power functions or some closer to the hardware stuff? -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

16:33

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c20 --- Comment #20 from Takashi Iwai --- (In reply to andreas bittner from comment #19)

do i need to make a video of the system? it is as i wrote. i cannot help it. i already looked into the logs yesterday and it was odd for me as well.

No, it doesn't help. We need the log to analyze what happens at which timing. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

23 Oct 23 Oct

08:51

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c21 --- Comment #21 from andreas bittner --- Ok, so where do we go from here? How can those needed logs be produced? Also: I tried with just a single 8gigabyte ddr dimm, and it is the same with the effective wakeup time. 1+ minute. I had hoped that maybe with less memory the effect would be different, but it is not. So the system does wake up the cpu in some way in a very few second(s) but then until it fully wakes or goes back into that usable state where the cpu fan rotates normally and the pixels are being displayed again takes 1+ minute. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

09:12

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c22 --- Comment #22 from Takashi Iwai --- There are a few ways to go forward. One is to try diet, reduce kernel components as much as possible. For example, disable USB, network, whatever, unload the corresponding kernel drivers, and try S3. Another way to check whether it's a kernel regression. If it did work ago, you can try installing such old kernels on the existing system, retest S3 to confirm that it's a kernel issue. Also you can try no_console_suspend boot option and run S3 from root Linux console (without GUI). This might show something, but I'm not sure about it. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

28 Oct 28 Oct

12:49

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c24 andreas bittner changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(abittner@opensuse | |.org) | --- Comment #24 from andreas bittner --- quick and dirty: i have another machine on that lan where this leap machine resides. i try to ping it all the time to its ipv4 address. during suspend (cpu fan completely off) it doesnt ping reply. when keypress, cpufan spins up and stays spinning slowly. still no ping reply during this time i try to ssh connect or even low-level telnet connect to tcp/22, they all time out. no connection. only when the machine again spins up the cpu fan completely and the pixels wake up again as well, does the ping get replied and can the machine connect to the tcp/22 does this tell anything? i think the wakeup is seriously messed up. this machine is not able to do useful work at all until that minute has passed and until it *really* did wake up to the fullest extent (whatever this means as i am trying to describe what i am witnessing here). -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

12:57

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c25 --- Comment #25 from andreas bittner --- summary: as soon as it pings, it does useful work. as soon as it pings, it also connects via raw telnet port 22 and displays the sshd banner, or via real ssh client and shows handshake and key fingerprint and all. and as soon as the e.g. num-lock on the ps/2 keyboard is reactive the whole system is truly alive again, meaning it isnt fully awake until the keyboard works as well. so i dont know about atx and acpu and s-states and related, but this system is definitely of no use until its fully awake. it does spin up the hdd, it does spin up the cpu fan into slowly rotating mode, but it does not allow the num-lock state to change (e.g. ps/2 keyboard driver stack still nonresponsive) and it does not compute ping packets nor tcp 22 handshake to the sshd during these zombie-wake state of the system. so there must be more to this suspend and waking up. more states more granularity in between or something. i am not an expert with this. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

13:21

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c26 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(abittner@opensuse | |.org) --- Comment #26 from Takashi Iwai --- OK, it means that the resume really takes time. Then try to test suspend/resume on Linux console, not on X, and boot with no_console_suspend option in addition to initcall_debug and ignore_loglevel options. This will show you the resume procedure on your console, and you might see whether it gets stuck. Another interesting test would be to do with kernel-debug instead of kernel-default. Boot with the same debug options and see whether you see something more interesting. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

13:35

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c27 --- Comment #27 from andreas bittner --- do i simply leftshift in grub2 menu and "e" keypress and then add the simple words at the end of the kernel line separated with spaces? so no_console_suspend initcall_debug ignore_loglevel appending to the end of the already existing boot entry in the grub2? -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

13:48

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c28 --- Comment #28 from Takashi Iwai --- Yes, it should work. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

14:10

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c29 --- Comment #29 from andreas bittner --- fresh reboot, went into grub, edited the kernel parameter line dmesg now shows at its beginning: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.1.10-1-default root=UUID=4a103dea-0699-4fce-a2f5-d456b8da39e0 video=1680x1050 resume=/dev/disk/by-id/ata-SAMSUNG_HD 321KJ_S0MQJ1KP116340-part1 splash=silent showopts no_console_suspend initcall_debug ignore_loglevel I created two dmesg log files. X booted up but i switched to alt+f2 and logged in there as root and issued the systemctl suspend. waited a bit and keypressed (space key). still the same, system wakes up fully only after 1+ minute. also: the atx power led pulsates during sleep, and it immediately stops pulsating and becomes fully lit and stays lit right when the cpu fan also starts rotating slowly. it stays lit when the system returns to fully rotating cpu fan and becomes working normally again. atx power led shows that the system does wake up in some way, but not fully. the dmesg shows more lines but as far as I have briefly seen it, it doesnt really hint or add useful lines for that one minute delay. will attach files. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

14:12

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c30 --- Comment #30 from andreas bittner --- Created attachment 653598 --> http://bugzilla.opensuse.org/attachment.cgi?id=653598&action=edit clean boot, addtl grub2 kernel boot parameters, before suspend/wakeup clean boot, addtl grub2 kernel boot parameters, before suspend/wakeup dmesg logged. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

14:12

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c31 andreas bittner changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(abittner@opensuse | |.org) | --- Comment #31 from andreas bittner --- Created attachment 653599 --> http://bugzilla.opensuse.org/attachment.cgi?id=653599&action=edit clean boot, addtl grub2 kernel boot parameters, after suspend/wakeup clean boot, addtl grub2 kernel boot parameters, after suspend/wakeup dmesg logged after the suspend and wakeup -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

14:20

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c32 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(abittner@opensuse | |.org) --- Comment #32 from Takashi Iwai --- The options won't change the boot behavior. The difference is that it'll show more texts while suspending and resuming. What I wanted to know is whether you see anything while the resume stalls. So, judging from your description, you didn't see anything before it starts working, right? If so, it really sounds more like a BIOS or firmware problem, i.e. stalling at the point before switching the control to kernel. Maybe you can try an older kernel (e.g. openSUSE 13.2 kernel) and a newer kernel (openSUSE FACTORY kernel) to compare whether it's a regression. Did it ever work well on your machine in the past? -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

14:30

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c33 --- Comment #33 from andreas bittner --- No, nothing is to be seen ever during this "cpu fan rotating still in slow mode, but hdd powerup is already triggered as the hdd spins up and continues to rotate, can be observed audibly". During this time, there are no pixels (monitor powered down, dpms state or similar, so: not only black screen), the num-lock lamp of the ps/2 keyboard can not be triggered, the network stack (pings) are not replying and nothing can be done with this semi-waked/semi-sleeping system. The atx power led (indicator) is not pulsating any more though. it does pulsate and indicate the real sleep state, when the cpu fan is completely turned off, and so is the hdd powered down at that time. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

14:36

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c34 andreas bittner changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(abittner@opensuse | |.org) | --- Comment #34 from andreas bittner --- I never really tried these sleep/wake functions on linux so far, so no sorry. Is there a simple way to add another kernel (from opensuse) to check? I remember something about KOTD (kernel of the day, or similar). I am not familiar with this procedure. Also I remember from many years back, there was some low level kind of text mode gui where one could set or modify endless number or little parameters and functionality which to include or to remove for customisation of kernel source code compilation. Is there a way for me to compile my own kernel as closely as possible to how the opensuse kernel is being compiled and built? I dont remember this config file method or config files name any more and how this exactly worked. Thanks. P.s. I think I remember this machine having ran microsoft windows 8.1 x64, with the same components, and I think I tried sleeping the system there and it did wake up quickly. I dont remember ever having to have waited for a minute or time spans even close to this. So if I am not completely mistaken this system (bios/board/cpu/memory/gfx) does sleep/wake well with at least windows. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

14:42

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c35 --- Comment #35 from Takashi Iwai --- You can install any kernel easily on top of the existing system. The kernel is supposed to be fairly backward/forward compatible. At least, openSUSE 13.2 kernel should work fine on FACTORY / Leap. Just grab the latest oS 13.2 kernel from OBS Kernel:openSUSE-13.2 repo. Then install it via zypper in --oldpackage kernel-desktop.rpm or rpm -ivh --oldpackage --nodeps kernel-desktop.rpm Ditto for FACTORY or any other, you can try kernel-default (no longer kernel-desktop) from Kernel:stable and Kernel:HEAD repos. I have a bunch of old kernel packages in my OBS home:tiwai:kernel:3.17, home:tiwai:kernel:3.18, ... home:tiwai:kernel:4.0 repos. You can try these if (and only if) S3 on openSUSE 13.2 kernel works and figure out which kernel starts regressing. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

14:49

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c36 --- Comment #36 from andreas bittner --- I am wondering now, as this system came from milestone releases, if maybe weird or old modules (modprobe.d/ or modules-load.d/) might affect the system? how can I really clean up a system to defaults to be sure? or maybe just re-install the current leap from .iso media and select to make it format and forget all from the root partition and only keep the /home partition? -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

15:02

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c37 --- Comment #37 from Takashi Iwai --- Well, there aren't so many things that can make suspend/resume wrong. In doubt, you can try without systemd, i.e. just by echo mem > /sys/power/state This way, only kernel does its job without any extra userland hooks. Hm, this reminds me of another good test: namely, try pm_test. First, try like echo devices > /sys/power/pm_test echo mem > /sys/power/state This simulates the S3, thus this must return quickly. If this takes time, something wrong in device suspend/resume. Similarly, test like echo platform > /sys/power/pm_test echo mem > /sys/power/state and echo processors > /sys/power/pm_test echo mem > /sys/power/state and echo core > /sys/power/pm_test echo mem > /sys/power/state If all these work (return quickly), the problem is really in the lower level. You can find some details in Documentation/power/basic-pm-debugging.txt in Linux kernel source tree. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

1 Nov 1 Nov

17:33

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c38 --- Comment #38 from andreas bittner --- with the real gold 42.1 kernel release 4.1.12 it is the same bug Linux linux-ang0 4.1.12-1-default #1 SMP PREEMPT Thu Oct 29 06:43:42 UTC 2015 (e24bad1) x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

17:41

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c39 --- Comment #39 from andreas bittner --- tried with 4.1.12 echo mem > /sys/power/state (only works as root) same slow wakeup 1+ minute delay until fully usable wake state again -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

17:45

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c40 --- Comment #40 from andreas bittner --- tried: echo platform > /sys/power/pm_test echo mem > /sys/power/state after the second echo it briefly turn off/on the hdd the screen goes black and comes back quickly. the whole operation is completed within maybe about 5 seconds -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

17:48

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c41 --- Comment #41 from andreas bittner --- also the two other variants work quickly (few seconds) echo processors > /sys/power/pm_test echo mem > /sys/power/state and echo core > /sys/power/pm_test echo mem > /sys/power/state both command variants return the system quickly after a keypress hdd is always spun down/up during this process where do we go from here now? bug in lower level, what does this mean now? -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

17:51

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c42 --- Comment #42 from andreas bittner --- update: after these tests I wanted to make the system sleep via kde menu again, but this also now only leads to the brief sleep of a few seconds screen turning off and hdd spinning down and up again and the system is now always returned thereafter to the kde unlock screen. the system cant be made to sleep any more after these commands from the kde start menu. :( -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

17:53

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c43 --- Comment #43 from andreas bittner --- further hint: even a systemctl suspend doesnt sleep the system now any more :( just to make it sure: i am not pressing or moving the mouse any more or any keys on the keyboard. i really want to make the system to go to sleep, so no incidental wakeup or anything. do i need to send some other content or variable via echo to some kernel area to fix this again? -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

2 Nov 2 Nov

08:12

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c44 --- Comment #44 from Takashi Iwai --- I guess you left /sys/power/pm_test modified? This is no one-shot variable. When this is set, all the rest PM would follow this mode. In anyways, your tests with pm_test indicate that the problem lies in the lower level, i.e. BIOS or firmware, not in the kernel itself. There might be some workarounds, but it's unknown. Windows supposedly works by doing some secret; or it's even possible that BIOS checks the OS and changes the behavior. So, sorry, from the kernel POV, there is no many things to fix as of now. You can try to adjust some BIOS setups to see whether it makes any difference. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

6 Nov 6 Nov

08:52

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Leap 42.1 RC1 1 |Leap 42.1 -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

8 Dec 8 Dec

21:16

New subject: [Bug 951548] system takes over a minute to fully wakeup after suspend, hibernate is even faster

http://bugzilla.opensuse.org/show_bug.cgi?id=951548 http://bugzilla.opensuse.org/show_bug.cgi?id=951548#c45 --- Comment #45 from andreas bittner --- still the same with todays 4.1.13 kernel Linux linux-ang0 4.1.13-5-default #1 SMP PREEMPT Thu Nov 26 16:35:17 UTC 2015 (49475c3) x86_64 x86_64 x86_64 GNU/Linux rpm -qi kernel-default Name : kernel-default Version : 4.1.13 Release : 5.1 Architecture: x86_64 Install Date: Tue 08 Dec 2015 09:05:23 PM CET Group : System/Kernel Size : 233679934 License : GPL-2.0 Signature : RSA/SHA256, Fri 27 Nov 2015 05:51:27 PM CET, Key ID b88b2fd43dbdc284 Source RPM : kernel-default-4.1.13-5.1.nosrc.rpm Build Date : Fri 27 Nov 2015 05:45:13 PM CET Build Host : cloud104 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : http://www.kernel.org/ Summary : The Standard Kernel Description : The standard kernel for both uniprocessor and multiprocessor systems. Source Timestamp: 2015-11-26 17:35:17 +0100 GIT Revision: 49475c39bfd2ee30d145707df8a17419822ba804 GIT Branch: users/tiwai/openSUSE-42.1/for-next Distribution: openSUSE Leap 42.1 -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

3068

Age (days ago)

3115

Last active (days ago)

Download

45 comments

1 participants

tags

participants (1)

bugzilla_noreply＠novell.com