broken session on resuming after from suspending to RAM

archdub · 2018-03-04 12:24:56

This issue started after I upgraded from kernel 4.14.x to 4.15.x. I had not upgraded for over a week so when I upgraded the kernel I also upgraded a few other dozen packages whose names I don't remember.

The issue I had afterwards was that on resume after suspending to RAM sometimes my session was broken which meant that I went back to the login prompt of the display manager and of course all the programs I had running in my open session (LibreOffice, Firefox, etc) were closed. By “sometimes my session was broken” I mean maybe once out of every 3 or 4 sleeps, though there was no clear pattern, I might have issues in two or three sleeps in a row.

Dmesg showed nothing interesting. Since I have a Nvidia card and there were a number of people in this forum with Nvidia related problems with kernel 4.15.x I thought that might be the reason. I tried to switch display managers but the issue would not go away. Then I took a look at journalctl and I what I saw seemed a bit odd with respect to “systemctl sleep”, which is what I am using in the Openbox menu to put the computer to sleep. So I started using “pm-suspend” (available in pm-utils) instead of “systemctl sleep” to put the computer to sleep and the problem disappeared.

So even though I solved my problem (or more precisely I found a workaround that works reliably) I have no idea what is the root problem, and don't have enough time or knowledge to go debugging systemd, Nvidia proprietary driver or the kernel, whatever is causing this issue. I just thought I would post this here in case it is helpful to other people.

Last edited by archdub (2018-03-21 08:19:08)

archdub · 2018-03-21 07:58:42

Well, it turns out that the problem was not really solved, instead it manifests less often if I use “pm-suspend” than if I use “systemctl sleep”.

This issue is of course annoying and it does not go away as so many issues go! I have no clue what is causing the issue, but my guess is either the 4.15 kernel, nVidia driver or systemd.

Although a number of people in this forum had problems with 4.15 kernel and nVidia driver none seem similar to mine. I also checked the kernel bug list and could not find anything similar.

I have no idea of why is it that I may be the only one having this issue, so I will say a few words about my computer and setup. I have a 4 core i7 CPU, nVidia card, 8 GB of RAM (which is not really enough so I have always swap being used, I need to buy more RAM). On the software side I run Openbox with a few bits and bobs on top (conky in the root window, a few dock apps such as gkrellm, and two instances of lxpanel). I have been using this software environment setup for many years.

When the issue manifests there is always a cascade of errors, which varies a bit from time to time. The log below is fairly typical. dmesg shows me nothing interesting.

['journalctl -b' output]
[suspend to RAM]
[user name was changed to 'myself' in log below]

Mar 20 01:02:57 arch-tornado kernel: EXT4-fs (sda6): re-mounted. Opts: data=ordered,commit=0
Mar 20 01:02:57 arch-tornado kernel: EXT4-fs (sda7): re-mounted. Opts: commit=0
Mar 20 01:02:58 arch-tornado kernel: PM: suspend entry (deep)
Mar 20 01:02:59 arch-tornado kernel: PM: Syncing filesystems ... done.

[wakeup from suspend, a cascade of errors that result in the session being destroyed and control 
returned to the display manager with a login prompt]

Mar 20 08:15:53 arch-tornado kernel: Freezing user space processes ... (elapsed 0.015 seconds) done.
Mar 20 08:16:01 arch-tornado kernel: OOM killer disabled.
Mar 20 08:16:01 arch-tornado kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
Mar 20 08:16:02 arch-tornado kernel: Suspending console(s) (use no_console_suspend to debug)
Mar 20 08:16:02 arch-tornado kernel: parport_pc 00:07: disabled
Mar 20 08:16:02 arch-tornado kernel: serial 00:05: disabled
Mar 20 08:16:02 arch-tornado kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Mar 20 08:16:03 arch-tornado kernel: sd 0:0:0:0: [sda] Stopping disk
Mar 20 08:16:03 arch-tornado kernel: ACPI: Preparing to enter system sleep state S3
Mar 20 08:16:03 arch-tornado kernel: PM: Saving platform NVS memory
Mar 20 08:16:03 arch-tornado kernel: Disabling non-boot CPUs ...
Mar 20 08:16:03 arch-tornado kernel: smpboot: CPU 1 is now offline
Mar 20 08:16:03 arch-tornado kernel: smpboot: CPU 2 is now offline
Mar 20 08:16:03 arch-tornado kernel: smpboot: CPU 3 is now offline
Mar 20 08:16:03 arch-tornado kernel: smpboot: CPU 4 is now offline
Mar 20 08:16:03 arch-tornado kernel: smpboot: CPU 5 is now offline
Mar 20 08:16:03 arch-tornado kernel: smpboot: CPU 6 is now offline
Mar 20 08:16:03 arch-tornado kernel: smpboot: CPU 7 is now offline
Mar 20 08:16:03 arch-tornado kernel: ACPI: Low-level resume complete
Mar 20 08:16:03 arch-tornado kernel: PM: Restoring platform NVS memory
Mar 20 08:16:03 arch-tornado kernel: Enabling non-boot CPUs ...
Mar 20 08:16:03 arch-tornado kernel: x86: Booting SMP configuration:
Mar 20 08:16:03 arch-tornado kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Mar 20 08:16:03 arch-tornado kernel:  cache: parent cpu1 should not be sleeping
Mar 20 08:16:03 arch-tornado kernel: CPU1 is up
Mar 20 08:16:03 arch-tornado kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Mar 20 08:16:03 arch-tornado kernel:  cache: parent cpu2 should not be sleeping
Mar 20 08:16:03 arch-tornado kernel: CPU2 is up
Mar 20 08:16:03 arch-tornado kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Mar 20 08:16:03 arch-tornado kernel:  cache: parent cpu3 should not be sleeping
Mar 20 08:16:03 arch-tornado kernel: CPU3 is up
Mar 20 08:16:03 arch-tornado kernel: smpboot: Booting Node 0 Processor 4 APIC 0x1
Mar 20 08:16:03 arch-tornado kernel:  cache: parent cpu4 should not be sleeping
Mar 20 08:16:03 arch-tornado kernel: CPU4 is up
Mar 20 08:16:03 arch-tornado kernel: smpboot: Booting Node 0 Processor 5 APIC 0x3
Mar 20 08:16:03 arch-tornado kernel:  cache: parent cpu5 should not be sleeping
Mar 20 08:16:03 arch-tornado kernel: CPU5 is up
Mar 20 08:16:03 arch-tornado kernel: smpboot: Booting Node 0 Processor 6 APIC 0x5
Mar 20 08:16:03 arch-tornado kernel:  cache: parent cpu6 should not be sleeping
Mar 20 08:16:03 arch-tornado kernel: CPU6 is up
Mar 20 08:16:03 arch-tornado kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
Mar 20 08:16:03 arch-tornado kernel:  cache: parent cpu7 should not be sleeping
Mar 20 08:16:03 arch-tornado kernel: CPU7 is up
Mar 20 08:16:03 arch-tornado kernel: ACPI: Waking up from system sleep state S3
Mar 20 08:16:03 arch-tornado kernel: serial 00:05: activated
Mar 20 08:16:03 arch-tornado kernel: sd 0:0:0:0: [sda] Starting disk
Mar 20 08:16:03 arch-tornado kernel: parport_pc 00:07: activated
Mar 20 08:16:03 arch-tornado kernel: r8169 0000:03:00.0 enp3s0: link down
Mar 20 08:16:03 arch-tornado kernel: OOM killer enabled.
Mar 20 08:16:03 arch-tornado kernel: Restarting tasks ... 
Mar 20 08:16:03 arch-tornado kernel: pci_bus 0000:05: Allocating resources
Mar 20 08:16:03 arch-tornado kernel: pci 0000:04:00.0: PCI bridge to [bus 05]
Mar 20 08:16:03 arch-tornado kernel: pci 0000:04:00.0:   bridge window [io  0x2000-0x2fff]
Mar 20 08:16:03 arch-tornado kernel: pci 0000:04:00.0:   bridge window [mem 0xe0000000-0xe01fffff]
Mar 20 08:16:03 arch-tornado kernel: pci 0000:04:00.0:   bridge window [mem 0xe0200000-0xe03fffff 64bit pref]
Mar 20 08:16:03 arch-tornado kernel: done.
Mar 20 08:16:03 arch-tornado kernel: PM: suspend exit
Mar 20 08:16:03 arch-tornado kernel: Read-error on swap-device (8:0:274472)
Mar 20 08:16:03 arch-tornado kernel: Read-error on swap-device (8:0:8968)
Mar 20 08:16:03 arch-tornado kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Mar 20 08:16:03 arch-tornado kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
Mar 20 08:16:03 arch-tornado kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT3._GTF, AE_NOT_FOUND (20170831/psparse-550)
Mar 20 08:16:03 arch-tornado kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
Mar 20 08:16:03 arch-tornado kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT3._GTF, AE_NOT_FOUND (20170831/psparse-550)
Mar 20 08:16:03 arch-tornado kernel: ata4.00: configured for UDMA/100
Mar 20 08:16:03 arch-tornado kernel: r8169 0000:03:00.0 enp3s0: link up
Mar 20 08:16:03 arch-tornado kernel: ata1: link is slow to respond, please be patient (ready=0)
Mar 20 08:16:03 arch-tornado kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar 20 08:16:03 arch-tornado kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
Mar 20 08:16:03 arch-tornado kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20170831/psparse-550)
Mar 20 08:16:03 arch-tornado kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
Mar 20 08:16:03 arch-tornado kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20170831/psparse-550)
Mar 20 08:16:03 arch-tornado kernel: ata1.00: configured for UDMA/133
Mar 20 08:16:03 arch-tornado kernel: EXT4-fs (sda6): re-mounted. Opts: data=ordered,commit=0
Mar 20 08:16:03 arch-tornado kernel: EXT4-fs (sda7): re-mounted. Opts: commit=0
Mar 20 08:15:53 arch-tornado /usr/bin/gpm[488]: *** info [mice.c(1990)]:
Mar 20 08:16:03 arch-tornado systemd[1]: Started Process Core Dump (PID 8510/UID 0).
Mar 20 08:15:53 arch-tornado /usr/bin/gpm[488]: imps2: Auto-detected intellimouse PS/2
Mar 20 08:16:11 arch-tornado pulseaudio[832]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Mar 20 08:16:11 arch-tornado pulseaudio[832]:       after 18 requests (6 known processed) with 0 events remaining.
Mar 20 08:16:24 arch-tornado at-spi-bus-launcher[688]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Mar 20 08:16:24 arch-tornado at-spi-bus-launcher[688]:       after 62533 requests (62533 known processed) with 0 events remaining.
Mar 20 08:16:14 arch-tornado su[1078]: pam_unix(su-l:session): session closed for user root
Mar 20 08:16:12 arch-tornado unknown[1302]: xfce4-notifyd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Mar 20 08:16:24 arch-tornado pulseaudio[8600]: W: [pulseaudio] pid.c: Stale PID file, overwriting.
Mar 20 08:16:24 arch-tornado pulseaudio[8600]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.3114" (uid=1000 pid=8600 comm="/usr/bin/pulseaudio --daemonize=no ") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (bus)
Mar 20 08:16:18 arch-tornado rtkit-daemon[702]: Successfully made thread 8600 of process 8600 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Mar 20 08:16:13 arch-tornado systemd[602]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
Mar 20 08:16:18 arch-tornado rtkit-daemon[702]: Supervising 1 threads of 1 processes of 1 users.
Mar 20 08:16:13 arch-tornado systemd[602]: xfce4-notifyd.service: Failed with result 'exit-code'.
Mar 20 08:16:22 arch-tornado lightdm[8607]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 892 (lightdm) with signal SIGTERM.
Mar 20 08:16:22 arch-tornado lightdm[892]: pam_unix(lightdm:session): session closed for user myself
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 902 (gnome-keyring-d) with signal SIGTERM.
Mar 20 08:16:22 arch-tornado rtkit-daemon[702]: Supervising 1 threads of 1 processes of 1 users.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 905 (openbox) with signal SIGTERM.
Mar 20 08:16:22 arch-tornado rtkit-daemon[702]: Successfully made thread 8612 of process 8600 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 922 (nm-applet) with signal SIGTERM.
Mar 20 08:16:22 arch-tornado rtkit-daemon[702]: Supervising 2 threads of 1 processes of 1 users.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 928 (sh) with signal SIGTERM.
Mar 20 08:16:22 arch-tornado rtkit-daemon[702]: Supervising 2 threads of 1 processes of 1 users.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 930 (sh) with signal SIGTERM.
Mar 20 08:16:22 arch-tornado rtkit-daemon[702]: Successfully made thread 8614 of process 8600 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 931 (sh) with signal SIGTERM.
Mar 20 08:16:22 arch-tornado rtkit-daemon[702]: Supervising 3 threads of 1 processes of 1 users.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 933 (sh) with signal SIGTERM.
Mar 20 08:16:22 arch-tornado dbus-daemon[484]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.3114" (uid=1000 pid=8600 comm="/usr/bin/pulseaudio --daemonize=no ") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (bus)
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 934 (sh) with signal SIGTERM.
Mar 20 08:16:23 arch-tornado systemd[8613]: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0)
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 937 (sh) with signal SIGTERM.
Mar 20 08:16:26 arch-tornado dbus-daemon[8626]: [session uid=620 pid=8626] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=620 pid=8624 comm="/usr/bin/lightdm-gtk-greeter ")
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 1024 (wmCalClock) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 1025 (wmtimer) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 1026 (thunar) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 1027 (xfce4-terminal) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 1034 (bash) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 1038 (conky) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 1039 (lxterminal) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 1040 (bash) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 1045 (gkrellm) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 1077 (xscreensaver) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 1078 (su) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 1079 (bash) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 1144 (leafpad) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 3603 (firefox) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 3686 (Web Content) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 3815 (Web Content) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 3865 (Web Content) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 3887 (Web Content) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 4849 (skypeforlinux) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 4852 (skypeforlinux) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 4889 (skypeforlinux) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 13623 (chrome) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 13628 (cat) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 13629 (cat) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 13631 (chrome-sandbox) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 13632 (chrome) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 13634 (chrome-sandbox) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 13635 (nacl_helper) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 13637 (chrome) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 13728 (chrome) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 13767 (chrome) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 13884 (chrome) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 13909 (chrome) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 13942 (chrome) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 13967 (chrome) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 13985 (chrome) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 14023 (chrome) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 14045 (chrome) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 14062 (chrome) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 14099 (chrome) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 14120 (chrome) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 14151 (chrome) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 14177 (chrome) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 14188 (chrome) with signal SIGTERM.
Mar 20 08:16:26 arch-tornado dbus-daemon[8626]: [session uid=620 pid=8626] Successfully activated service 'org.a11y.Bus'
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 14228 (chrome) with signal SIGTERM.
Mar 20 08:16:27 arch-tornado at-spi-bus-launcher[8627]: dbus-daemon[8632]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=620 pid=8624 comm="/usr/bin/lightdm-gtk-greeter ")
Mar 20 08:16:27 arch-tornado at-spi-bus-launcher[8627]: dbus-daemon[8632]: Successfully activated service 'org.a11y.atspi.Registry'
Mar 20 08:16:26 arch-tornado dbus-daemon[8626]: [session uid=620 pid=8626] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.5' (uid=620 pid=8624 comm="/usr/bin/lightdm-gtk-greeter ")
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 14247 (chrome) with signal SIGTERM.
Mar 20 08:16:27 arch-tornado at-spi-bus-launcher[8627]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 14267 (chrome) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 28671 (sh) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 28673 (lxpanel) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 28690 (menu-cached) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 30538 (chromium) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 30540 (chrome-sandbox) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 30541 (chromium) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 30543 (chromium) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 30624 (chromium) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 30627 (chromium) with signal SIGTERM.
Mar 20 08:16:27 arch-tornado dbus-daemon[8626]: [session uid=620 pid=8626] Successfully activated service 'org.gtk.vfs.Daemon'
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 30659 (chromium) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 30776 (chromium) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 30799 (chromium) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 30821 (chromium) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 30854 (chromium) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 30867 (chromium) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 30894 (chromium) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 30924 (chromium) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 30927 (chromium) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 30987 (chromium) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 31004 (chromium) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 31037 (chromium) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 31077 (chromium) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: session-c4.scope: Killing process 31099 (chromium) with signal SIGTERM.
Mar 20 08:16:13 arch-tornado systemd[1]: Stopping Session c4 of user myself.
Mar 20 08:16:14 arch-tornado systemd[602]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE
Mar 20 08:16:15 arch-tornado systemd[602]: pulseaudio.service: Failed with result 'exit-code'.
Mar 20 08:16:15 arch-tornado systemd[602]: pulseaudio.service: Service hold-off time over, scheduling restart.
Mar 20 08:16:15 arch-tornado systemd[602]: pulseaudio.service: Scheduled restart job, restart counter is at 2.
Mar 20 08:16:15 arch-tornado systemd[602]: Stopped Sound Service.
Mar 20 08:16:15 arch-tornado systemd[602]: Starting Sound Service...
Mar 20 08:16:20 arch-tornado lightdm[500]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Mar 20 08:16:21 arch-tornado lightdm[8607]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Mar 20 08:16:22 arch-tornado systemd[1]: Created slice User Slice of lightdm.
Mar 20 08:16:22 arch-tornado systemd[1]: Starting User Manager for UID 620...
Mar 20 08:16:22 arch-tornado systemd-logind[485]: New session c5 of user lightdm.
Mar 20 08:16:22 arch-tornado systemd[1]: Started Session c5 of user lightdm.
Mar 20 08:16:23 arch-tornado systemd[602]: Started Sound Service.
Mar 20 08:16:24 arch-tornado systemd-coredump[8581]: Process 838 (Xorg) of user 0 dumped core.
                                                     
                                                     Stack trace of thread 838:
                                                     #0  0x00007f7b57c1f2d0 _ULx86_64_init_local (libunwind.so.8)
                                                     #1  0x0000557b59a00f13 xorg_backtrace (Xorg)
                                                     #2  0x0000557b59a04d89 n/a (Xorg)
                                                     #3  0x00007f7b56533dd0 __restore_rt (libpthread.so.0)
                                                     #4  0x00007f7b508de280 n/a (nvidia_drv.so)
                                                     #5  0x00007f7b4f98e363 wfbBlt (libwfb.so)
                                                     #6  0x00007f7b4f991b6c wfbCopyNtoN (libwfb.so)
                                                     #7  0x0000557b599e20bc miCopyRegion (Xorg)
                                                     #8  0x0000557b599e27de miDoCopy (Xorg)
                                                     #9  0x00007f7b4f99234d wfbCopyArea (libwfb.so)
                                                     #10 0x00007f7b50e223b0 n/a (nvidia_drv.so)
Mar 20 08:16:24 arch-tornado systemd[8613]: Starting D-Bus User Message Bus Socket.
Mar 20 08:16:24 arch-tornado systemd[8613]: Listening on GnuPG network certificate management daemon.
Mar 20 08:16:24 arch-tornado systemd[8613]: Listening on GnuPG cryptographic agent and passphrase cache.
Mar 20 08:16:24 arch-tornado systemd[8613]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Mar 20 08:16:24 arch-tornado systemd[8613]: Listening on Sound System.
Mar 20 08:16:24 arch-tornado systemd[8613]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 20 08:16:24 arch-tornado systemd[8613]: Reached target Paths.
Mar 20 08:16:24 arch-tornado systemd[8613]: Reached target Timers.
Mar 20 08:16:24 arch-tornado systemd[8613]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Mar 20 08:16:24 arch-tornado systemd[8613]: Listening on D-Bus User Message Bus Socket.
Mar 20 08:16:24 arch-tornado systemd[8613]: Reached target Sockets.
Mar 20 08:16:24 arch-tornado systemd[8613]: Reached target Basic System.
Mar 20 08:16:24 arch-tornado systemd[8613]: Reached target Default.
Mar 20 08:16:24 arch-tornado systemd[8613]: Startup finished in 722ms.
Mar 20 08:16:24 arch-tornado systemd[1]: Started User Manager for UID 620.
Mar 20 08:16:24 arch-tornado systemd[1]: Stopped Session c4 of user myself.
Mar 20 08:16:24 arch-tornado systemd-logind[485]: Removed session c4.
Mar 20 08:16:24 arch-tornado systemd[8613]: Started D-Bus User Message Bus.
Mar 20 08:16:26 arch-tornado systemd[8613]: Starting Accessibility services bus...
Mar 20 08:16:26 arch-tornado systemd[8613]: Started Accessibility services bus.
Mar 20 08:16:26 arch-tornado systemd[8613]: Starting Virtual filesystem service...
Mar 20 08:16:27 arch-tornado systemd[8613]: Started Virtual filesystem service.
Mar 20 08:16:31 arch-tornado lightdm[8657]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Mar 20 08:16:31 arch-tornado systemd[1]: session-c5.scope: Killing process 8607 (lightdm) with signal SIGTERM.
Mar 20 08:16:31 arch-tornado systemd[1]: session-c5.scope: Killing process 8624 (lightdm-gtk-gre) with signal SIGTERM.
Mar 20 08:16:31 arch-tornado systemd[1]: Stopping Session c5 of user lightdm.
Mar 20 08:16:31 arch-tornado lightdm[8607]: pam_unix(lightdm-greeter:session): session closed for user lightdm
Mar 20 08:16:31 arch-tornado systemd[1]: Stopped Session c5 of user lightdm.
Mar 20 08:16:31 arch-tornado lightdm[500]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Mar 20 08:16:31 arch-tornado systemd-logind[485]: Removed session c5.
Mar 20 08:16:31 arch-tornado lightdm[8657]: pam_unix(lightdm:session): session opened for user myself by (uid=0)
Mar 20 08:16:31 arch-tornado systemd[1]: Stopping User Manager for UID 620...
Mar 20 08:16:31 arch-tornado systemd-logind[485]: New session c6 of user myself.
Mar 20 08:16:31 arch-tornado systemd[1]: Started Session c6 of user myself.
Mar 20 08:16:31 arch-tornado systemd[8613]: Stopped target Default.
Mar 20 08:16:31 arch-tornado systemd[8613]: Stopping Virtual filesystem service...
Mar 20 08:16:31 arch-tornado systemd[8613]: Stopping D-Bus User Message Bus...
Mar 20 08:16:31 arch-tornado systemd[8613]: Stopping Accessibility services bus...
Mar 20 08:16:31 arch-tornado systemd[8613]: Stopped Accessibility services bus.
Mar 20 08:16:31 arch-tornado systemd[8613]: Stopped D-Bus User Message Bus.
Mar 20 08:16:31 arch-tornado systemd[8613]: Stopped Virtual filesystem service.
Mar 20 08:16:31 arch-tornado systemd[8613]: Stopped target Basic System.
Mar 20 08:16:31 arch-tornado systemd[8613]: Stopped target Sockets.
Mar 20 08:16:31 arch-tornado systemd[8613]: Closed GnuPG network certificate management daemon.
Mar 20 08:16:31 arch-tornado systemd[8613]: Closed Sound System.
Mar 20 08:16:31 arch-tornado systemd[8613]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Mar 20 08:16:31 arch-tornado systemd[8613]: Closed GnuPG cryptographic agent and passphrase cache.
Mar 20 08:16:31 arch-tornado systemd[8613]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Mar 20 08:16:31 arch-tornado systemd[8613]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 20 08:16:31 arch-tornado systemd[8613]: Stopped target Paths.
Mar 20 08:16:31 arch-tornado systemd[8613]: Stopped target Timers.
Mar 20 08:16:31 arch-tornado systemd[8613]: Closed D-Bus User Message Bus Socket.
Mar 20 08:16:31 arch-tornado systemd[8613]: Reached target Shutdown.
Mar 20 08:16:31 arch-tornado systemd[8613]: Starting Exit the Session...
Mar 20 08:16:31 arch-tornado systemd[8616]: pam_unix(systemd-user:session): session closed for user lightdm
Mar 20 08:16:31 arch-tornado systemd[8613]: Received SIGRTMIN+24 from PID 8665 (kill).
Mar 20 08:16:31 arch-tornado systemd[1]: Stopped User Manager for UID 620.
Mar 20 08:16:31 arch-tornado systemd[1]: Removed slice User Slice of lightdm.
Mar 20 08:16:33 arch-tornado at-spi-bus-launcher[688]: dbus-daemon[693]: Activating service name='org.a11y.atspi.Registry' requested by ':1.8259' (uid=1000 pid=8710 comm="nm-applet ")
Mar 20 08:16:34 arch-tornado at-spi-bus-launcher[688]: dbus-daemon[693]: Successfully activated service 'org.a11y.atspi.Registry'
Mar 20 08:16:34 arch-tornado at-spi-bus-launcher[688]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Mar 20 08:16:34 arch-tornado zeitgeist-daemon[675]: [08:16:34.780486 WARNING] zeitgeist-daemon.vala:127: Unable to parse version info!
Mar 20 08:16:34 arch-tornado zeitgeist-daemon[675]: [08:16:34.844190 WARNING] zeitgeist-daemon.vala:127: Unable to parse version info!
Mar 20 08:16:37 arch-tornado dbus-daemon[484]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.3124' (uid=1000 pid=8713 comm="python /usr/bin/blueman-applet ")
Mar 20 08:16:37 arch-tornado dbus-daemon[484]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Mar 20 08:16:50 arch-tornado su[8864]: (to root) myself on pts/0
Mar 20 08:16:50 arch-tornado su[8864]: pam_unix(su-l:session): session opened for user root by (uid=1000)
Mar 20 08:17:34 arch-tornado dbus-daemon[484]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.3125' (uid=1000 pid=8912 comm="/usr/share/skypeforlinux/skypeforlinux --executed-")
Mar 20 08:17:34 arch-tornado dbus-daemon[484]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Mar 20 08:17:40 arch-tornado dbus-daemon[623]: [session uid=1000 pid=623] Activating service name='org.freedesktop.secrets' requested by ':1.16766' (uid=1000 pid=8912 comm="/usr/share/skypeforlinux/skypeforlinux --executed-")
Mar 20 08:17:40 arch-tornado dbus-daemon[623]: [session uid=1000 pid=623] Successfully activated service 'org.freedesktop.secrets'
Mar 20 08:17:42 arch-tornado gnome-keyring-daemon[8668]: asked to register item /org/freedesktop/secrets/collection/login/5, but it's already registered
Mar 20 08:17:43 arch-tornado gnome-keyring-daemon[8668]: asked to register item /org/freedesktop/secrets/collection/login/4, but it's already registered

Any ideas of what could be causing this issue?

archdub · 2018-03-26 19:02:20

I couldn't figure out what was causing the issue however someone in this forum in another thread recommended using linux-lts with nVidia, I did that and have had no problem since.

City-busz · 2018-03-27 08:08:56

I experienced the same problem with Intel Graphics after I updated my system to linux 4.15. I had to downgrade to 4.14. I have no idea what causes it, but something related to the kernel.

archdub · 2018-03-31 11:10:08

Interesting. I thought it was just for nVidia.

This issue really annoyed me. I am glad that with linux-lts the problem stopped.

Last edited by archdub (2018-04-02 20:32:16)

sourcejedi · 2018-04-04 10:28:37

Hi, fellow users of the cursed kernel v4.15 .

Some Fedora Linux users are also suffering from this kernel bug. We have reported it to Fedora.

Current main bug: https://bugzilla.redhat.com/show_bug.cgi?id=1553979

My duplicate report with my exhausting notes: https://bugzilla.redhat.com/show_bug.cgi?id=1557682

The above are so far still assigned to Xwayland. On Fedora, we first saw this as the graphical session dying due to an unusual SIGBUS in Xwayland. There's hundreds of the automatic Fedora crash reports. However the unusual SIGBUS is also reported against native Xorg. (One unfortunate reporter had switched to Xorg, hoping it would stop their Xwayland crashes; it did not .

Thanks everyone for writing up your results.

Magnesium · 2018-04-11 15:12:37

I have this issue but I dont have NVIDIA, using radeon HD5450.
The session is broken but some processes survives - for instance tmux-server.
Dmesg is showing this error msg and I wonder if it is related to the "broken session error after resume"
A workaround is to use hybrid sleep instead suspend - the system will recover from hibernation if needed.

[19599.436965] Corrupted low memory at 000000008ee7978c (9ce0 phys) = a000000000000000
[19599.436969] Corrupted low memory at 00000000d43ed837 (9ce8 phys) = 0b030038

sourcejedi · 2018-04-11 16:34:53

Hmm. I didn't see that message. I was wondering about it though - I was among the reporting users who caused that message and check to be implemented .

The only reason the kernel is able to print that message, is it reserves an area of physical ram that many buggy bioses scribble on. (Suspend/resume was one such event when the bios behaved this way). So the damaged bytes that this message *detected*, does not cause any problem, because the kernel was already making sure not to use that memory.

The stackexchange answer says the Linux default is to reserve the first 64K, but it suggests Windows might be reserving the first megabyte...

The Linux docs confuse me a bit. Looking across the current source, I think if you're concerned that your bios might also be scribbling beyond the first 64k, you're supposed to test by adding the options `reservelow=640K memory_corruption_check_size=640K memory_corruption_check=1`. (The area 640K - 1M is already reserved, it is never used as RAM. If you pass 1M to reservelow= it will limit it back to 640K .

Once you know your bios is buggy, you can run with `reservelow=640K`. (And report to the kernel people that you have discovered an even more evil bios. So they could introduce a new blacklist of the super-evil bioses, or increase the default reservation...).

I wonder if you built your own kernel. Linux eventually enabled the 64K reservation on all machines. I think the corruption *test* code was intended to be for testing/debugging only. So I'm not sure that distro kernels are really intended to enable the build-time option, X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK, which makes `memory_corruption_check=1` the default. The Fedora kernel I'm using doesn't.

---

For the moment I wrote a `trace-cmd` (ftrace) script. I'm hoping it will capture enough to narrow down further, the next time I hit this suspend problem... I'm struggling to guess what change might have caused it, though I'm keeping an eye out for this one, relating to scsi suspend/resume.

Magnesium · 2018-04-11 17:51:18

thank you for explanation about corrupted low memory error. Unfortunately there are no further BIOS updates for this model from ASUS, since 2012. No I didnt build my own kernel, my arch linux was installed accordingly to official guide.

City-busz · 2018-04-21 05:45:29

Still happens for me with linux 4.16.3. Now I see the following error message in kernel log when it happens:

[14581.070018] Read-error on swap-device (8:0:1066251)

archdub · 2018-04-22 08:27:41

Since I started using linux-lts (which is 4.14.x) the issue has not manifested even once.

When I was still using the regular kernel (4.15.x) the end result of this issue was that the display manager session was closed and all my programs were closed and the login prompt appeared, however what happened between putting the PC to sleep and the login prompt appearing varied. There was always a cascade of errors but there was more than one type of cascade and consequently the time between waking up the PC and the login prompt appearing varied from about 1 minute to about 5 minutes.

At times I had error messages about swap. At various times I thought the problem was in X, Nvidia driver, display manager, systemd, swap. Clearly since the problem stopped manifesting when I switched back to kernel 4.14 the kernel is involved in this issue in some way or other.

The other odd thing that I saw is messages about systemd goint to sleep with the timestamp being after the PC had been woken up. Not sure about the reason, maybe the systemd messages went into a buffer that was written to disk (and time-stamped) only after waking up.

Last edited by archdub (2018-04-22 13:55:08)

Magnesium · 2018-04-22 14:56:43

archdub wrote:

all my programs were closed and the login prompt appeared, however what happened between putting the PC to sleep and the login prompt appearing varied.

here my tmux process survives the pseudo crash. Could be a clue.

Seems another consequence of the broken sessions is the fact of my hdd file system becoming dirty - EXT4 and BTRFS too. Recently had a unrecoverable error on btrfs and reinstalled the system.

But this time Im trying a new swap partition size of RAM size + 2GiB, as recommended. Always used a swap partition size equaling to memory ram size, without errors in suspend/hibernate until some months ago. I remember a session that lasted more than 40 days when I had to reboot to kernel upgrade.

Last edited by Magnesium (2018-04-22 14:57:26)

archdub · 2018-04-22 15:23:41

A few times after this happened fsck fixed a few things but I don't think I lost any data.

The other puzzling thing is why few people get this error. At work one of my PCs runs Arch. This issue did not manifest. However there are several differences between by my home PC that has problems and my work PC.

Home PC with problem:
- older (4 years old)
- Nvidia graphics
- 8GB RAM (swap partition often in use due to low amount of RAM)
- openbox
- MSDOS partitioning

Work PC (no problem):
- newer (one year old)
- embedded Intel graphics
- 16GB RAM (swap partition generally not used as there is enough RAM for my the programs I normally use)
- LXDE
- GPT partitioning

I am mentioning the partitioning and RAM figures in case this problem is somehow caused by a swap related bug.

I am mentioning the age in case this problem is caused by microcode issues introduced to solve Spectre/Meltdown.

Magnesium · 2018-04-22 17:45:30

I forgot to mention my system related to this problem:

age - about 8 years
6GB RAM
radeon HD5420
asus sabertooth x58 - BIOS, not UEFI
HDD 1TB with GPT table - with a BIOS GRUB partition of about 2MB in size to be seen by BIOS
intel i7 950

Magnesium · 2018-04-23 21:21:03

well, I reinstalled arch in april 21 with some differences to prior installation and for 1d and 22hours of normal usage, suspending and hibernating, the problem didnt occur!
as said in my other message,
1 --> always used swap size partition = RAMsize; This time I configured a swap partition of RAM size plus 2GiB. I have 6GiB so, swap size = 8GiB;
2 --> always using swappiness value of 1; this time configured to 10 - i thinks this is irrelevant for the problem but... who knows.

1d and 22 hours seems to little time to tell but I had this problem for almost every single day when using suspend. This time, for a whole day (the first day) the suspending/resuming seems working pretty well.

Magnesium · 2018-04-25 12:05:40

suspended/resumed around 19 times and the session age about 3 days and 13 hours and the problem seems gone.
I think increasing size of SWAP partition did the trick, as related above.

archdub · 2018-04-26 18:47:48

My swap partition is big (slightly more than 3 times the RAM size) so that is not what was causing me problems.

loqs · 2018-04-26 19:02:59

Has anyone still affected tried https://git.kernel.org/pub/scm/linux/ke … 8a9068f428
Edit:
spelling affected not affect

Last edited by loqs (2018-04-26 19:03:26)

Magnesium · 2018-04-26 19:36:32

loqs wrote:

Has anyone still affected tried https://git.kernel.org/pub/scm/linux/ke … 8a9068f428
Edit:
spelling affected not affect

this is what I get but as said, seems Im not affected anymore...

[root@sun i3]# dd if=/dev/sda of=/dev/null iflag=direct & \
> while killall -SIGUSR1 dd; do sleep 0.1; done & \
> echo mem > /sys/power/state ; \
> sleep 5; killall dd
[1] 21902
[2] 21903
1+0 records in
0+0 records out
0 bytes copied, 0.0169636 s, 0.0 kB/s
880+0 records in
879+0 records out
450048 bytes (450 kB, 440 KiB) copied, 0.119295 s, 3.8 MB/s
1814+0 records in
1813+0 records out
928256 bytes (928 kB, 906 KiB) copied, 0.479636 s, 1.9 MB/s
2148+0 records in
2147+0 records out
1099264 bytes (1.1 MB, 1.0 MiB) copied, 0.552495 s, 2.0 MB/s
2405+0 records in
2404+0 records out
1230848 bytes (1.2 MB, 1.2 MiB) copied, 0.669359 s, 1.8 MB/s
3160+0 records in
3159+0 records out
1617408 bytes (1.6 MB, 1.5 MiB) copied, 0.778175 s, 2.1 MB/s
4103+0 records in
4102+0 records out
2100224 bytes (2.1 MB, 2.0 MiB) copied, 0.881831 s, 2.4 MB/s
4604+0 records in
4603+0 records out
2356736 bytes (2.4 MB, 2.2 MiB) copied, 0.988077 s, 2.4 MB/s
dd: error reading '/dev/sda': Input/output error
4922+0 records in
4922+0 records out
2520064 bytes (2.5 MB, 2.4 MiB) copied, 3.60571 s, 699 kB/s
4922+0 records in
4922+0 records out
2520064 bytes (2.5 MB, 2.4 MiB) copied, 3.60574 s, 699 kB/s
dd: no process found
[1]- Exit 1 dd if=/dev/sda of=/dev/null iflag=direct
[2]+ Done while killall -SIGUSR1 dd; do
sleep 0.1;
done
dd: no process found

Last edited by Magnesium (2018-04-27 04:25:02)

Magnesium · 2018-05-04 19:56:14

unfortunately after about two weeks this issue happened again - read error on swap device and crash of session;
so, increasing swap partition size: no deal.

but the fact from occurring every single day to once in two weeks is encouraging

archdub · 2018-05-04 21:53:49

That post by loqs is interesting, though I have not had time to give it a try as I have been extremely busy.

Which kernel are you using at the moment? Like I said before since I started using linux-lts (which is 4.14.x) the issue has not manifested even once. Maybe give it a try?

Magnesium · 2018-05-05 14:36:49

I'm using 4.16.6-1, always using the newest. Thanks for the idea of using lts but for now I'll wait a solution until getting really annoyed

loqs · 2018-05-05 14:47:55

The fix for the issue I linked is in 4.16.7-1 currently in testing you could download that package (as well as headers and other kernel modules if needed)
to test without using the rest of testing as userspace and kernelspace are separate.

Magnesium · 2018-05-06 17:11:02

loqs wrote:

The fix for the issue I linked is in 4.16.7-1 currently in testing you could download that package (as well as headers and other kernel modules if needed)
to test without using the rest of testing as userspace and kernelspace are separate.

wonderful!
thank you

Arch Linux

#1 2018-03-04 12:24:56

broken session on resuming after from suspending to RAM

#2 2018-03-21 07:58:42

Re: broken session on resuming after from suspending to RAM

#3 2018-03-26 19:02:20

Re: broken session on resuming after from suspending to RAM

#4 2018-03-27 08:08:56

Re: broken session on resuming after from suspending to RAM

#5 2018-03-31 11:10:08

Re: broken session on resuming after from suspending to RAM

#6 2018-04-04 10:28:37

Re: broken session on resuming after from suspending to RAM

#7 2018-04-11 15:12:37

Re: broken session on resuming after from suspending to RAM

#8 2018-04-11 16:34:53

Re: broken session on resuming after from suspending to RAM

#9 2018-04-11 17:51:18

Re: broken session on resuming after from suspending to RAM

#10 2018-04-21 05:45:29

Re: broken session on resuming after from suspending to RAM

#11 2018-04-22 08:27:41

Re: broken session on resuming after from suspending to RAM

#12 2018-04-22 14:56:43

Re: broken session on resuming after from suspending to RAM

#13 2018-04-22 15:23:41

Re: broken session on resuming after from suspending to RAM

#14 2018-04-22 17:45:30

Re: broken session on resuming after from suspending to RAM

#15 2018-04-23 21:21:03

Re: broken session on resuming after from suspending to RAM

#16 2018-04-25 12:05:40

Re: broken session on resuming after from suspending to RAM

#17 2018-04-26 18:47:48

Re: broken session on resuming after from suspending to RAM

#18 2018-04-26 19:02:59

Re: broken session on resuming after from suspending to RAM

#19 2018-04-26 19:36:32

Re: broken session on resuming after from suspending to RAM

#20 2018-05-04 19:56:14

Re: broken session on resuming after from suspending to RAM

#21 2018-05-04 21:53:49

Re: broken session on resuming after from suspending to RAM

#22 2018-05-05 14:36:49

Re: broken session on resuming after from suspending to RAM

#23 2018-05-05 14:47:55

Re: broken session on resuming after from suspending to RAM

#24 2018-05-06 17:11:02

Re: broken session on resuming after from suspending to RAM

Board footer