should I move this into Bug reports?
Hi all,
after some update that changed something in my system, my Port 5.0 x86-64 XFCE 4.16 system crashed when trying to suspend every one or two days, and usually not even REISUB is helping and I need to do a hard reset (pressing the power button for 10 seconds).
My system:
Code: Select all
root@porteus:~# cat /etc/porteus/*
001-core.xzm:20221006
002-xorg.xzm:20221006
002-xtra.xzm:20220630
003-xfce.xzm:20220925
initrd.xz:20220928
For now I checked if not going online makes a difference ( theory was: maybe some nasty stuff got behind the more on the easy side of things rc.Fireall ) but no, the crash still happened.
Thee one program I updated recently was palemoon, but palemoon is not running during suspend because it occupies too much RAM (I only have 4 GB) so PM is very unlikely the culprit.
I realized after the newest core updates that starting X takes seemingly longer (I boot in mode 3 to initialize the above "[HOWTO] save log files" and manually start X by a guest virtual console login and using
Code: Select all
startx
What are you suggesting I try changing first?
002-xtra.xzm is from 20220630 and thus cannot be the issue.
Should I exchange only one of these modules for the older one:
001-core.xzm:20221006
002-xorg.xzm:20221006
003-xfce.xzm:20220925
and see if that gets me to the core of the issue?
And which order would you suggest changing a module?
I think only exchanging one module at a time makes more sense than exchanging 2 or even all three.
Not loading any additional modules makes no sense since then having the system turned on serves no purpose, I need my interlink for emails and palemoon for the net.
The saved log /var/log/messages never tells me anything helpful.
These are the last 2 crashes.
This is the most recent crash, the one where I did not go online:
Code: Select all
Nov 16 07:45:26 porteus NetworkManager[1603]: <info> [1668581126.0748] manager: sleep: sleep requested (sleeping: no enabled: yes)
Nov 16 07:45:26 porteus NetworkManager[1603]: <info> [1668581126.0749] device (eth0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov 16 07:45:26 porteus ModemManager[1647]: <info> [sleep-monitor] system is about to suspend
●● sleeping 10 seconds for loginctl suspend to background-suspend. ●●
Nov 16 07:45:26 porteus NetworkManager[1603]: <info> [1668581126.0907] manager: NetworkManager state is now ASLEEP
Nov 16 07:45:26 porteus elogind-daemon[1275]: Suspending system...
Nov 16 07:45:26 porteus kernel: PM: suspend entry (deep)
Nov 16 07:45:26 porteus kernel: Filesystems sync: 0.001 seconds
And the one crash before that:
Code: Select all
●● sleeping 10 seconds for loginctl suspend to background-suspend. ●●
Nov 15 14:02:57 porteus NetworkManager[1622]: <info> [1668517377.0868] manager:
sleep: sleep requested (sleeping: no enabled: yes)
Nov 15 14:02:57 porteus NetworkManager[1622]: <info> [1668517377.1026] device (
eth0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-stat
e: 'managed')
Nov 15 14:02:57 porteus ModemManager[1669]: <info> [sleep-monitor] system is ab
out to suspend
Nov 15 14:02:57 porteus NetworkManager[1622]: <info> [1668517377.1205] manager:
NetworkManager state is now ASLEEP
Nov 15 14:02:57 porteus elogind-daemon[1112]: Suspending system...
Nov 15 14:02:57 porteus kernel: PM: suspend entry (deep)
Nov 15 14:02:57 porteus kernel: Filesystems sync: 0.056 seconds
Nov 15 14:03:18 porteus kernel: Freezing user space processes ...
Nov 15 14:03:18 porteus kernel: Xorg D 0 1796 1795 0x00400004
Nov 15 14:03:18 porteus kernel: OOM killer enabled.
Nov 15 14:03:18 porteus kernel: Restarting tasks ... done.
Nov 15 14:03:18 porteus kernel: video LNXVIDEO:01: Restoring backlight state
●●●●● loginctl suspend took 00:00:25 … ●●●●●●●●●●●●●●●
●●●●● after suspend-s3b2 ●●●●●●●●●●●●●●●
Nov 15 14:03:18 porteus kernel: PM: suspend exit
Nov 15 14:03:18 porteus kernel: PM: suspend entry (s2idle)
Nov 15 14:03:18 porteus acpid: client 1796[0:100] has disconnected
Nov 15 14:03:18 porteus last message buffered 1 times
Nov 15 14:03:18 porteus acpid: client connected from 1796[0:100]
Nov 15 14:03:18 porteus acpid: 1 client rule loaded
15.11.2022 14:03:18 ____________________________________________________________
total used free shared buff/cache available
Mem: 3873 1291 707 64 1875 2086
Swap: 4917 102 4815
________________________________________________________________________________
Filename Type Size Used Priority
/dev/sda6 partition 4607 0 1
/dev/zram0 partition 309 102 100
Nov 15 14:03:18 porteus kernel: Filesystems sync: 0.392 seconds
Nov 15 14:03:19 porteus acpid: client connected from 1796[0:100]
Nov 15 14:03:19 porteus acpid: 1 client rule loaded
Again some extra info is added by my suspend script like the free -m and /proc/swaps stuff.
actually I use this function for the swap info:
Code: Select all
sx ()
{
read firstLine;
echo "$firstLine";
while read f t s u p; do
let "s2 = $s / 1024";
let "u2 = $u / 1024";
printf '%-40s%-16s%-8s%-8s%-8s\n' $f $t $s2 $u2 $p;
done
} < /proc/swaps
And another crash, again it went into suspend, according to the /var/log/messages it took 22 seconds, but it crashed nonetheless during its return from loginctl suspend:
Code: Select all
Nov 17 09:44:09 porteus NetworkManager[1563]: <info> [1668674649.2820] manager: sleep: sleep requested (sleeping: no enabled: yes)
Nov 17 09:44:09 porteus NetworkManager[1563]: <info> [1668674649.2821] manager: NetworkManager state is now ASLEEP
Nov 17 09:44:09 porteus NetworkManager[1563]: <info> [1668674649.2824] device (eth0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
●● sleeping 10 seconds for loginctl suspend to background-suspend. ●●
Nov 17 09:44:09 porteus ModemManager[1610]: <info> [sleep-monitor] system is about to suspend
Nov 17 09:44:09 porteus dbus-daemon[772]: [system] Activating service name='org.freedesktop.nm_dispatcher' requested by ':1.3' (uid=0 pid=1563 comm="/usr/sbin/NetworkManager ") (using servicehelper)
Nov 17 09:44:09 porteus dbus-daemon[772]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 17 09:44:09 porteus NetworkManager[1563]: <info> [1668674649.3732] device (eth0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Nov 17 09:44:09 porteus NetworkManager[1563]: <info> [1668674649.38d34] policy: set-hostname: current hostname was changed outside NetworkManager: 'porteus.example.net'
Nov 17 09:44:09 porteus NetworkManager[1563]: <info> [1668674649.3847] policy: set-hostname: current hostname was changed outside NetworkManager: 'porteus.example.net'
Nov 17 09:44:09 porteus NetworkManager[1563]: <info> [1668674649.3857] device (eth0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov 17 09:44:09 porteus kernel: r8169 0000:02:00.0 eth0: Link is Down
Nov 17 09:44:09 porteus elogind-daemon[1169]: Suspending system...
Nov 17 09:44:09 porteus kernel: PM: suspend entry (deep)
Nov 17 09:44:09 porteus kernel: Filesystems sync: 0.061 seconds
Nov 17 09:44:30 porteus kernel: Freezing user space processes ...
Nov 17 09:44:30 porteus kernel: tee D 0 1718 1712 0x00004004
Nov 17 09:44:30 porteus kernel: OOM killer enabled.
Nov 17 09:44:30 porteus kernel: Restarting tasks ... done.
Nov 17 09:44:30 porteus kernel: video LNXVIDEO:01: Restoring backlight state
●●●●● loginctl suspend took 00:00:22 … ●●●●●●●●●●●●●●●
●●●●● after suspend-s0b2 ●●●●●●●●●●●●●●●
Nov 17 09:44:30 porteus kernel: PM: suspend exit
Nov 17 09:44:30 porteus kernel: PM: suspend entry (s2idle)
Nov 17 09:44:30 porteus acpid: client 1767[0:100] has disconnected
Nov 17 09:44:30 porteus last message buffered 1 times
Nov 17 09:44:30 porteus acpid: client connected from 1767[0:100]
Nov 17 09:44:30 porteus acpid: 1 client rule loaded
17.11.2022 09:44:30 ____________________________________________________________
total used free shared buff/cache available
Mem: 3873 1399 1237 85 1236 1966
Swap: 4917 57 4860
________________________________________________________________________________
Filename Type Size Used Priorityd
/dev/sda6 partition 4607 0 1
/dev/zram0 partition 309 57 100
Nov 17 09:44:30 porteus kernel: Filesystems sync: 0.499 seconds
Nov 17 09:44:30 porteus acpid: client connected from 1767[0:100]
Nov 17 09:44:30 porteus acpid: 1 client rule loaded
When any of these crashes happens, the machine is kept on but the screen turns dark - but not switches off.
And only when I press any key, only then the screen switches off due of not getting any black image from the OS any more, for whatever weird reasons.
Does this behaviour on crash rings any bells with any of you?