Linux Mint 21.3 Repeated lockups after upgrade from 21.2

[yjo-jo]

Hi I had an initial post because I had a similarity to another user, but of course my hardware would not be a match (as was pointed out to me). So the result might seem similar but don't know if it is the same problem.

Based on that, I tried to gather information in a similar manner to that post, which I will add below. I have been using for a long time, but 100% since 2020. Since the recent update (21.3) I have a hard crash about every 2 days. I always leave my computer running (and always have... it does stuff for me when I'm not at home!). I mostly notice these lockups when I come back to it, in the evening or first thing in the morning. I am describing a lockup as the screen remaining black when I return to it... I do not have my computer sleep, but I do have my monitor sleep, so generally when I return, I tap the keyboard and the monitor comes to life. In these lockup cases, the screen does not. The capslock key performs no function (capslock light stays off). The motherboard has a visible diagnostic code, but according to that code, there is no error... it is the same code listed as when it is running fine. I have tried to ping the machine from a different one on my network, and there is no ping response. That's my definition of lockup in this scenario.

Even when the computer is running, I notice that the mouse regularly stutters across my screen. Then later, the mouse will be normal. I've tried to catch active processes with the System Monitor while the mouse is stuttering, but the highest ranking process is generally Cinnamon, but many things are jumping around of course.

I only have one display.

As mentioned, I tried to review other similar troubles, so here is some of the output I have captured.

My xsession-errors only seemed to have data from my "startup after the lockup" (now, before posting). So let's start with my xsession-errors.old Today is "Mar 14", and this log is all from "Mar 13" based on higher up in the file.

Code: Select all

mint-common (WARN): runtime/org.freedesktop.Sdk/x86_64/20.08 is end-of-life (EOL) (org.freedesktop.Platform 20.08 is no longer receiving fixes and security updates. Please update to a supported runtime version.)
Gjs-Message: 16:22:32.767: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Gjs-Message: 16:37:33.684: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Gjs-Message: 16:52:34.759: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Gjs-Message: 17:07:35.842: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Gjs-Message: 17:22:37.261: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Gjs-Message: 17:37:38.993: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Gjs-Message: 17:52:40.710: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Gjs-Message: 18:07:41.957: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
mint-common (WARN): runtime/org.freedesktop.Sdk/x86_64/20.08 is end-of-life (EOL) (org.freedesktop.Platform 20.08 is no longer receiving fixes and security updates. Please update to a supported runtime version.)
Gjs-Message: 18:22:42.913: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Gjs-Message: 18:37:45.103: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Gjs-Message: 18:52:47.080: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Gjs-Message: 19:07:48.230: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Gjs-Message: 19:22:49.343: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Gjs-Message: 19:37:50.530: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Gjs-Message: 19:52:51.830: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Gjs-Message: 20:07:53.014: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
cinnamon-session[2419]: WARNING: t+86987.99896s: Detected that screensaver has left the bus
mint-common (WARN): runtime/org.freedesktop.Sdk/x86_64/20.08 is end-of-life (EOL) (org.freedesktop.Platform 20.08 is no longer receiving fixes and security updates. Please update to a supported runtime version.)
Gjs-Message: 20:22:55.738: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Gjs-Message: 20:37:56.977: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00003
Gjs-Message: 20:52:57.756: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Gjs-Message: 21:07:58.568: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
cinnamon-session[2419]: WARNING: t+90657.85069s: Detected that screensaver has appeared on the bus
Gjs-Message: 21:22:59.363: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Gjs-Message: 21:38:01.980: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Gjs-Message: 21:53:03.895: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
Gjs-Message: 22:08:05.076: JS LOG: [LookingGlass/info] [weather@mockturtl#14:Info]: Weather Information refreshed
mint-common (WARN): runtime/org.freedesktop.Sdk/x86_64/20.08 is end-of-life (EOL) (org.freedesktop.Platform 20.08 is no longer receiving fixes and security updates. Please update to a supported runtime version.)

Doesn't look great, maybe I can get rid of that end-of-life thing, unless that is generally expected to show up. Also, I notice that "screensaver has left the bus". I don't know what that means, but maybe screensaver is a problem?

I captured

Code: Select all

journalctl -b -1 -p warning --no-pager

... that results in this, also note from Mar 13:

Code: Select all

Mar 12 20:04:48 XXXXXXX kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
Mar 12 20:04:48 XXXXXXX kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
Mar 12 20:04:48 XXXXXXX kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
Mar 12 20:04:48 XXXXXXX kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
Mar 12 20:04:48 XXXXXXX kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
Mar 12 20:04:48 XXXXXXX kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
Mar 12 20:04:48 XXXXXXX kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
Mar 12 20:04:48 XXXXXXX kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
Mar 12 20:04:48 XXXXXXX kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
Mar 12 20:04:48 XXXXXXX kernel: usb: port power management may be unreliable
Mar 12 20:04:48 XXXXXXX kernel: ata1.00: supports DRM functions and may not be fully accessible
Mar 12 20:04:48 XXXXXXX kernel: ata3.00: supports DRM functions and may not be fully accessible
Mar 12 20:04:48 XXXXXXX kernel: ata3.00: supports DRM functions and may not be fully accessible
Mar 12 20:04:48 XXXXXXX kernel: ata1.00: supports DRM functions and may not be fully accessible
Mar 12 20:04:48 XXXXXXX kernel: nvidia: loading out-of-tree module taints kernel.
Mar 12 20:04:48 XXXXXXX kernel: nvidia: module license 'NVIDIA' taints kernel.
Mar 12 20:04:48 XXXXXXX kernel: Disabling lock debugging due to kernel taint
Mar 12 20:04:48 XXXXXXX kernel: 
Mar 12 20:04:48 XXXXXXX kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  550.54.14  Thu Feb 22 01:44:30 UTC 2024
Mar 12 20:04:48 XXXXXXX kernel: nvidia-gpu 0000:0a:00.3: i2c timeout error e0000000
Mar 12 20:04:48 XXXXXXX kernel: ucsi_ccg 2-0008: i2c_transfer failed -110
Mar 12 20:04:48 XXXXXXX kernel: ucsi_ccg 2-0008: ucsi_ccg_init failed - -110
Mar 12 20:04:48 XXXXXXX kernel: ucsi_ccg: probe of 2-0008 failed with error -110
Mar 12 20:04:48 XXXXXXX kernel: sr 5:0:0:0: Power-on or device reset occurred
Mar 12 20:04:48 XXXXXXX kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20210730/utaddress-204)
Mar 12 20:04:48 XXXXXXX systemd[1]: ureadahead.service: Failed with result 'exit-code'.
Mar 12 20:04:48 XXXXXXX kernel: nvidia_uvm: module uses symbols from proprietary module nvidia, inheriting taint.
Mar 12 20:04:48 XXXXXXX kernel: iwlwifi 0000:04:00.0: api flags index 2 larger than supported by driver
Mar 12 20:04:48 XXXXXXX kernel: kvm: disabled by bios
Mar 12 20:04:48 XXXXXXX kernel: thermal thermal_zone0: failed to read out thermal zone (-61)
Mar 12 20:04:48 XXXXXXX kernel: Bluetooth: hci0: MSFT filter_enable is already on
Mar 12 20:04:48 XXXXXXX kernel: kvm: disabled by bios
Mar 12 20:04:49 XXXXXXX lightdm[1501]: Seat type 'xlocal' is deprecated, use 'type=local' instead
Mar 12 20:04:49 XXXXXXX bluetoothd[1348]: Failed to set mode: Blocked through rfkill (0x12)
Mar 12 20:04:49 XXXXXXX udisksd[1385]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Mar 12 20:04:49 XXXXXXX udisksd[1385]: Failed to load the 'mdraid' libblockdev plugin
Mar 12 20:04:49 XXXXXXX systemd-udevd[903]: vboxdrv: /etc/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME="vboxdrv".
Mar 12 20:04:49 XXXXXXX systemd-udevd[767]: vboxdrvu: /etc/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME="vboxdrvu".
Mar 12 20:04:49 XXXXXXX kernel: VBoxNetFlt: Successfully started.
Mar 12 20:04:49 XXXXXXX systemd-udevd[903]: vboxnetctl: /etc/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME="vboxnetctl".
Mar 12 20:04:49 XXXXXXX kernel: VBoxNetAdp: Successfully started.
Mar 12 20:04:49 XXXXXXX systemd[1]: apache2.service: Failed with result 'exit-code'.
Mar 12 20:04:49 XXXXXXX systemd[1]: Failed to start The Apache HTTP Server.
Mar 12 20:04:50 XXXXXXX libvirtd[1457]: Unable to open /dev/kvm: No such file or directory
Mar 12 20:04:50 XXXXXXX systemd-xdg-autostart-generator[1950]: Not generating service for XDG autostart app-polkit\x2dmate\x2dauthentication\x2dagent\x2d1@autostart.service, error parsing Exec= line: No such file or directory
Mar 12 20:04:50 XXXXXXX systemd-xdg-autostart-generator[1950]: Not generating service for XDG autostart app-mate\x2dsettings\x2ddaemon@autostart.service, error parsing Exec= line: No such file or directory
Mar 12 20:04:50 XXXXXXX systemd-xdg-autostart-generator[1950]: Not generating service for XDG autostart app-mate\x2dscreensaver@autostart.service, error parsing Exec= line: No such file or directory
Mar 12 20:04:50 XXXXXXX systemd-xdg-autostart-generator[1950]: Not generating service for XDG autostart app-mate\x2dpower\x2dmanager@autostart.service, error parsing Exec= line: No such file or directory
Mar 12 20:04:50 XXXXXXX systemd-xdg-autostart-generator[1950]: Not generating service for XDG autostart app-mate\x2dvolume\x2dcontrol\x2dstatus\x2dicon@autostart.service, error parsing Exec= line: No such file or directory
Mar 12 20:04:50 XXXXXXX systemd-xdg-autostart-generator[1950]: Not generating service for XDG autostart app-org.kde.kdeconnect.daemon@autostart.service, error parsing Exec= line: No such file or directory
Mar 12 20:04:54 XXXXXXX upowerd[2006]: treated changed event as add on /sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:07:00.1/usb1/1-1/1-1:1.2/0003:046D:C52B.0003/0003:046D:4013.0005/power_supply/hidpp_battery_0
Mar 12 20:04:55 XXXXXXX systemd[1]: kerneloops.service: Found left-over process 2151 (kerneloops) in control group while starting unit. Ignoring.
Mar 12 20:04:55 XXXXXXX systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 12 20:04:55 XXXXXXX kernel: kauditd_printk_skb: 20 callbacks suppressed
Mar 12 20:04:55 XXXXXXX systemd[1]: casper-md5check.service: Failed with result 'exit-code'.
Mar 12 20:04:55 XXXXXXX systemd[1]: Failed to start casper-md5check Verify Live ISO checksums.
Mar 12 20:05:00 XXXXXXX lightdm[2018]: gkr-pam: unable to locate daemon control file
Mar 12 20:05:00 XXXXXXX pulseaudio[1954]: Error opening PCM device hdmi:0: No such file or directory
Mar 12 20:05:00 XXXXXXX pulseaudio[1954]: Error opening PCM device front:1: No such file or directory
Mar 12 20:05:00 XXXXXXX pulseaudio[1954]: Error opening PCM device hw:2: No such file or directory
Mar 12 20:05:00 XXXXXXX systemd-xdg-autostart-generator[2402]: /home/user_name_here/.config/autostart/audio-recorder.desktop:51: Unknown key name 'Actions' in section 'Desktop Entry', ignoring.
Mar 12 20:05:00 XXXXXXX systemd-xdg-autostart-generator[2402]: /home/user_name_here/.config/autostart/audio-recorder.desktop:53: Unknown section 'Desktop Action StartRecording'. Ignoring.
Mar 12 20:05:00 XXXXXXX systemd-xdg-autostart-generator[2402]: /home/user_name_here/.config/autostart/audio-recorder.desktop:60: Unknown section 'Desktop Action StopRecording'. Ignoring.
Mar 12 20:05:00 XXXXXXX systemd-xdg-autostart-generator[2402]: /home/user_name_here/.config/autostart/audio-recorder.desktop:67: Unknown section 'Desktop Action PauseRecording'. Ignoring.
Mar 12 20:05:00 XXXXXXX systemd-xdg-autostart-generator[2402]: /home/user_name_here/.config/autostart/audio-recorder.desktop:74: Unknown section 'Desktop Action ShowWindow'. Ignoring.
Mar 12 20:05:00 XXXXXXX systemd-xdg-autostart-generator[2402]: Not generating service for XDG autostart app-mate\x2dscreensaver@autostart.service, error parsing Exec= line: No such file or directory
Mar 12 20:05:00 XXXXXXX systemd-xdg-autostart-generator[2402]: Not generating service for XDG autostart app-mate\x2dsettings\x2ddaemon@autostart.service, error parsing Exec= line: No such file or directory
Mar 12 20:05:00 XXXXXXX systemd-xdg-autostart-generator[2402]: Not generating service for XDG autostart app-org.kde.kdeconnect.daemon@autostart.service, error parsing Exec= line: No such file or directory
Mar 12 20:05:00 XXXXXXX systemd-xdg-autostart-generator[2402]: Not generating service for XDG autostart app-mate\x2dpower\x2dmanager@autostart.service, error parsing Exec= line: No such file or directory
Mar 12 20:05:00 XXXXXXX systemd-xdg-autostart-generator[2402]: Not generating service for XDG autostart app-polkit\x2dmate\x2dauthentication\x2dagent\x2d1@autostart.service, error parsing Exec= line: No such file or directory
Mar 12 20:05:00 XXXXXXX systemd-xdg-autostart-generator[2402]: Not generating service for XDG autostart app-mate\x2dvolume\x2dcontrol\x2dstatus\x2dicon@autostart.service, error parsing Exec= line: No such file or directory
Mar 12 20:05:00 XXXXXXX cinnamon-session[2419]: WARNING: t+0.02201s: Could not read /etc/xdg/autostart/mate-power-manager.desktop: Could not parse desktop file mate-power-manager.desktop or it references a not found TryExec binary
Mar 12 20:05:00 XXXXXXX cinnamon-session[2419]: WARNING: t+0.02417s: Could not read /etc/xdg/autostart/mate-volume-control-status-icon.desktop: Could not parse desktop file mate-volume-control-status-icon.desktop or it references a not found TryExec binary
Mar 12 20:05:00 XXXXXXX cinnamon-session[2419]: WARNING: t+0.02503s: Could not read /etc/xdg/autostart/org.kde.kdeconnect.daemon.desktop: Could not parse desktop file org.kde.kdeconnect.daemon.desktop or it references a not found TryExec binary
Mar 12 20:05:00 XXXXXXX cinnamon-session[2419]: WARNING: t+0.02525s: Could not read /etc/xdg/autostart/mate-settings-daemon.desktop: Could not parse desktop file mate-settings-daemon.desktop or it references a not found TryExec binary
Mar 12 20:05:00 XXXXXXX cinnamon-session[2419]: WARNING: t+0.02546s: Could not read /etc/xdg/autostart/polkit-mate-authentication-agent-1.desktop: Could not parse desktop file polkit-mate-authentication-agent-1.desktop or it references a not found TryExec binary
Mar 12 20:05:03 XXXXXXX org.Cinnamon.Slideshow[2771]: /usr/share/cinnamon/cinnamon-slideshow/cinnamon-slideshow.py:4: DeprecationWarning: Importing dbus.glib to use the GLib main loop with dbus-python is deprecated.
Mar 12 20:05:03 XXXXXXX org.Cinnamon.Slideshow[2771]: Instead, use this sequence:
Mar 12 20:05:03 XXXXXXX org.Cinnamon.Slideshow[2771]:     from dbus.mainloop.glib import DBusGMainLoop
Mar 12 20:05:03 XXXXXXX org.Cinnamon.Slideshow[2771]:     DBusGMainLoop(set_as_default=True)
Mar 12 20:05:03 XXXXXXX org.Cinnamon.Slideshow[2771]:   import dbus, dbus.service, dbus.glib
Mar 12 20:05:04 XXXXXXX cinnamon-session[2419]: WARNING: t+3.87507s: Detected that screensaver has appeared on the bus
Mar 12 20:05:35 XXXXXXX cinnamon-session[2419]: WARNING: t+35.14720s: Detected that screensaver has left the bus
Mar 12 20:06:56 XXXXXXX systemd-resolved[1284]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server xxx.xxx.xxx.xxx.
Mar 12 20:28:11 XXXXXXX cinnamon-session[2419]: WARNING: t+1390.89503s: Detected that screensaver has appeared on the bus
Mar 13 03:05:16 XXXXXXX systemd-resolved[1284]: Using degraded feature set TCP instead of UDP for DNS server xxx.xxx.xxx.xxx.
Mar 13 07:52:27 XXXXXXX gnome-keyring-daemon[2414]: asked to register item /org/freedesktop/secrets/collection/login/13, but it's already registered
Mar 13 07:52:27 XXXXXXX gnome-keyring-daemon[2414]: asked to register item /org/freedesktop/secrets/collection/login/12, but it's already registered
Mar 13 11:25:01 XXXXXXX systemd-resolved[1284]: Using degraded feature set UDP instead of TCP for DNS server xxx.xxx.xxx.xxx.
Mar 13 19:52:26 XXXXXXX gnome-keyring-daemon[2414]: asked to register item /org/freedesktop/secrets/collection/login/13, but it's already registered
Mar 13 19:52:26 XXXXXXX gnome-keyring-daemon[2414]: asked to register item /org/freedesktop/secrets/collection/login/12, but it's already registered
Mar 13 20:10:20 XXXXXXX systemd-resolved[1284]: Using degraded feature set TCP instead of UDP for DNS server xxx.xxx.xxx.xxx.
Mar 13 20:14:18 XXXXXXX cinnamon-screensaver-pam-helper[28768]: pam_ecryptfs: seteuid error
Mar 13 20:14:48 XXXXXXX cinnamon-session[2419]: WARNING: t+86987.99896s: Detected that screensaver has left the bus
Mar 13 20:14:48 XXXXXXX org.cinnamon.ScreenSaver[5465]: Error in sys.excepthook:
Mar 13 20:14:48 XXXXXXX org.cinnamon.ScreenSaver[5465]: Original exception was:
Mar 13 20:14:48 XXXXXXX org.cinnamon.ScreenSaver[5465]: Error in sys.excepthook:
Mar 13 20:14:48 XXXXXXX org.cinnamon.ScreenSaver[5465]: Original exception was:
Mar 13 20:14:48 XXXXXXX org.cinnamon.ScreenSaver[5465]: Error in sys.excepthook:
Mar 13 20:14:48 XXXXXXX org.cinnamon.ScreenSaver[5465]: Original exception was:
Mar 13 20:16:25 XXXXXXX systemd-resolved[1284]: Using degraded feature set UDP instead of TCP for DNS server xxx.xxx.xxx.xxx.
Mar 13 20:22:44 XXXXXXX systemd-resolved[1284]: Using degraded feature set TCP instead of UDP for DNS server xxx.xxx.xxx.xxx.
Mar 13 20:26:32 XXXXXXX systemd-resolved[1284]: Using degraded feature set UDP instead of TCP for DNS server xxx.xxx.xxx.xxx.
Mar 13 20:31:45 XXXXXXX systemd-resolved[1284]: Using degraded feature set TCP instead of UDP for DNS server xxx.xxx.xxx.xxx.
Mar 13 21:15:58 XXXXXXX cinnamon-session[2419]: WARNING: t+90657.85069s: Detected that screensaver has appeared on the bus

I scrubbed a few things with xxxx. There is stuff about Mate in there, but I have not used LM with Mate since 2021... then I reverted to Cinnamon ever since... do I need to purge all/any thing from Mate? My understanding was they could sort of both be present and toggle when you want, but I never use Mate anymore, so maybe I should wipe it out.

Thanks for any ideas you might have. If you are curious about the post were I got started, it is this one:
viewtopic.php?t=412498

[yjo-jo]

Oops, I wanted to add this one

Code: Select all

System:
  Kernel: 5.15.0-100-generic x86_64 bits: 64 compiler: gcc v: 11.4.0
    Desktop: Cinnamon 6.0.4 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
    Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-E GAMING v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 5003
    date: 10/07/2023
CPU:
  Info: 16-core model: AMD Ryzen 9 3950X bits: 64 type: MT MCP smt: enabled
    arch: Zen 2 rev: 0 cache: L1: 1024 KiB L2: 8 MiB L3: 64 MiB
  Speed (MHz): avg: 2227 high: 3608 min/max: 2200/3500 boost: enabled
    cores: 1: 2204 2: 2195 3: 2190 4: 2192 5: 2195 6: 2197 7: 2195 8: 2195
    9: 2133 10: 2056 11: 2502 12: 2011 13: 2195 14: 2204 15: 2194 16: 2194
    17: 2195 18: 2196 19: 2194 20: 2195 21: 2196 22: 2196 23: 2196 24: 2196
    25: 2129 26: 2053 27: 3608 28: 2100 29: 2195 30: 2196 31: 2196 32: 2195
    bogomips: 223567
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA TU116 [GeForce GTX 1660] vendor: ZOTAC driver: nvidia
    v: 550.54.14 pcie: speed: 5 GT/s lanes: 16 bus-ID: 0a:00.0
    chip-ID: 10de:2184 class-ID: 0300
  Device-2: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 3-2:2 chip-ID: 046d:0825 class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia
    gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 108 s-size: 602x342mm (23.7x13.5")
    s-diag: 692mm (27.3")
  Monitor-1: DP-0 res: 2560x1440 hz: 60 dpi: 109
    size: 597x336mm (23.5x13.2") diag: 685mm (27")
  OpenGL: renderer: NVIDIA GeForce GTX 1660/PCIe/SSE2
    v: 4.6.0 NVIDIA 550.54.14 direct render: Yes

[SMG]

Since the recent update (21.3) I have a hard crash about every 2 days. I always leave my computer running (and always have... it does stuff for me when I'm not at home!). I mostly notice these lockups when I come back to it, in the evening or first thing in the morning. I am describing a lockup as the screen remaining black when I return to it... I do not have my computer sleep, but I do have my monitor sleep, so generally when I return, I tap the keyboard and the monitor comes to life. In these lockup cases, the screen does not. The capslock key performs no function (capslock light stays off). The motherboard has a visible diagnostic code, but according to that code, there is no error... it is the same code listed as when it is running fine. I have tried to ping the machine from a different one on my network, and there is no ping response. That's my definition of lockup in this scenario.

Have you tried using the 6.5 kernel available in Update Manager?

From where did you obtain the Nvidia-550 driver you have installed?

mint-common (WARN): runtime/org.freedesktop.Sdk/x86_64/20.08 is end-of-life (EOL) (org.freedesktop.Platform 20.08 is no longer receiving fixes and security updates. Please update to a supported runtime version.)

Please see [SOLVED] flatpak: org.freedesktop.Platform.GL.default//20.08 is end-of-life

Also, I notice that "screensaver has left the bus". I don't know what that means, but maybe screensaver is a problem?

That is a normal message.

Please post your complete system information. You only posted the first few sections.

[yjo-jo]

Hi SMG, thank you for your help. I think we met in that other post.

If I look at Update Manager, I don't see any kernel updates available. Is there anything I have to do to get those to show up? I could provide a list of what it shows if it helps. Or I'm comfortable with apt if we have to go around Update Manager.

In that other post, I think you told the person to get the latest Nvidia driver, so before I made this post, I had tried to do that to. I went to the Nvidia site and got their "run" package, and ran it. I had prev. made a TimeShift so I was ready for failure, but it seemed as if there were no problems. To be clear, I had the problem (and found that other post) prior to the latest Nvidia, so I was hoping that was the issue for me and that is how I got the 550 version.

Can you refresh me on the complete system info? I think I got this from the command you had given the other user... it is the inxi -SMCGxxxz command. Would different flags get more details that you need? Thank you again!!

[SMG]

If I look at Update Manager, I don't see any kernel updates available. Is there anything I have to do to get those to show up? I could provide a list of what it shows if it helps. Or I'm comfortable with apt if we have to go around Update Manager.

Instructions for upgrading to the 6.5 kernel:

• Open Update Manager.
• Select View > Linux Kernels and click Continue.
• Make sure 6.5 is selected on the left panel and then click the top-most option on the right panel. An "Install" button will appear.
• Install the kernel and then reboot for it to become active.

In that other post, I think you told the person to get the latest Nvidia driver, so before I made this post, I had tried to do that to. I went to the Nvidia site and got their "run" package, and ran it.

We do not recommend using the driver from the Nvidia website. We recommend using the driver in Driver Manager.

The Nvidia-550 driver is a beta driver. I suggest you run the Nvidia uninstall script to remove the driver you installed from the website. You will cause problems on your system if you try mixing different methods of installing Nvidia drivers. The driver methods do not work with each other and you can end up with two different drivers on your system which causes problems.

Can you refresh me on the complete system info?

It's the same information listed in How to get help (the section in pink right above your topic title). I have copied it below:

Open the System Reports app and click the System Information tab on the left. Your computer's information should come up in the right pane. Then click the Copy button in the lower right and paste the results into a reply window here so we can see how Linux Mint views your hardware.

[yjo-jo]

OK, thank you. I totally misunderstood from the other post... so I have uninstalled the Nvidia driver and I went to the Driver Manager. I had the options of 525, 535, and 545, however it told me that 535 was "recommended"... so I went with that one. I can go up to the 545 if you think that would be better.

I upgraded my kernel to 6.5. Thanks for pointing me to that... in never really browsed around in Update Manager and usually just take what it lists, so that was a new thing for me, thanks!

Here is the result of my system report AFTER the mods I just described above.

Code: Select all

System:
  Kernel: 6.5.0-25-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 6.0.4 tk: GTK 3.24.33
    wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-E GAMING v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 5003 date: 10/07/2023
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M525 serial: <filter>
    charge: 100% (should be ignored) rechargeable: yes status: Discharging
CPU:
  Info: 16-core model: AMD Ryzen 9 3950X bits: 64 type: MT MCP smt: enabled arch: Zen 2 rev: 0
    cache: L1: 1024 KiB L2: 8 MiB L3: 64 MiB
  Speed (MHz): avg: 2488 high: 4242 min/max: 2200/4761 boost: enabled cores: 1: 2196 2: 2200
    3: 2200 4: 2196 5: 2195 6: 2200 7: 2196 8: 2196 9: 2200 10: 2121 11: 4241 12: 4235 13: 2200
    14: 2200 15: 2200 16: 3500 17: 2200 18: 2196 19: 2195 20: 2200 21: 2200 22: 2196 23: 2200
    24: 2196 25: 2121 26: 2200 27: 2200 28: 4212 29: 2200 30: 2200 31: 2200 32: 4242
    bogomips: 223585
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA TU116 [GeForce GTX 1660] vendor: ZOTAC driver: nvidia v: 535.161.07 pcie:
    speed: 2.5 GT/s lanes: 16 ports: active: none off: DP-1 empty: DP-2,DP-3,HDMI-A-1
    bus-ID: 0a:00.0 chip-ID: 10de:2184 class-ID: 0300
  Device-2: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 3-2:2
    chip-ID: 046d:0825 class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia gpu: nvidia display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 108 s-size: 602x342mm (23.7x13.5") s-diag: 692mm (27.3")
  Monitor-1: DP-0 res: 2560x1440 hz: 60 dpi: 109 size: 597x336mm (23.5x13.2") diag: 685mm (27")
  OpenGL: renderer: NVIDIA GeForce GTX 1660/PCIe/SSE2 v: 4.6.0 NVIDIA 535.161.07
    direct render: Yes
Audio:
  Device-1: NVIDIA TU116 High Definition Audio vendor: ZOTAC driver: snd_hda_intel v: kernel pcie:
    speed: 8 GT/s lanes: 16 bus-ID: 0a:00.1 chip-ID: 10de:1aeb class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
    speed: 16 GT/s lanes: 16 bus-ID: 0c:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 3-2:2
    chip-ID: 046d:0825 class-ID: 0102 serial: <filter>
  Sound Server-1: ALSA v: k6.5.0-25-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: speed: 5 GT/s lanes: 1
    bus-ID: 04:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp4s0 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel pcie: speed: 5 GT/s
    lanes: 1 port: e000 bus-ID: 05:00.0 chip-ID: 10ec:8125 class-ID: 0200
  IF: enp5s0 state: down mac: <filter>
  Device-3: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel pcie:
    speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 06:00.0 chip-ID: 8086:1539 class-ID: 0200
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-6:5 chip-ID: 8087:0029
    class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block:
    hardware: no software: yes address: <filter>
Drives:
  Local Storage: total: 7.28 TiB used: 3.95 TiB (54.2%)
  ID-1: /dev/nvme0n1 vendor: Sabrent model: Rocket 4.0 1TB size: 931.51 GiB speed: 63.2 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: RKT401.1 temp: 39.9 C scheme: GPT
  ID-2: /dev/sda vendor: Samsung model: SSD 860 QVO 2TB size: 1.82 TiB speed: 6.0 Gb/s type: SSD
    serial: <filter> rev: 1B6Q
  ID-3: /dev/sdb vendor: Samsung model: SSD 860 QVO 2TB size: 1.82 TiB speed: 6.0 Gb/s type: SSD
    serial: <filter> rev: 1B6Q scheme: MBR
  ID-4: /dev/sdc type: USB vendor: Toshiba model: DT01ACA300 size: 2.73 TiB type: HDD rpm: 7200
    serial: <filter> scheme: GPT
Partition:
  ID-1: / size: 915.32 GiB used: 245.26 GiB (26.8%) fs: ext4 dev: /dev/nvme0n1p3
  ID-2: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/nvme0n1p1
  ID-3: /home size: 1.79 TiB used: 473.34 GiB (25.8%) fs: ext4 dev: /dev/sda
Swap:
  ID-1: swap-1 type: file size: 5.86 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-1:2 info: Logitech Unifying Receiver type: Keyboard,Mouse,HID
    driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s power: 98mA
    chip-ID: 046d:c52b class-ID: 0300
  Device-2: 1-3:3 info: Holtek Keyboard LKS02 type: Keyboard,HID driver: hid-generic,usbhid
    interfaces: 2 rev: 1.1 speed: 1.5 Mb/s power: 100mA chip-ID: 04d9:1702 class-ID: 0300
  Hub-2: 1-5:4 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
    chip-ID: 05e3:0610 class-ID: 0900
  Device-1: 1-6:5 info: Intel AX200 Bluetooth type: Bluetooth driver: btusb interfaces: 2
    rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 8087:0029 class-ID: e001
  Hub-3: 2-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-4: 3-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 3-2:2 info: Logitech Webcam C270 type: Video,Audio driver: snd-usb-audio,uvcvideo
    interfaces: 4 rev: 2.0 speed: 480 Mb/s power: 500mA chip-ID: 046d:0825 class-ID: 0102
    serial: <filter>
  Device-2: 3-4:3 info: ASUSTek AURA LED Controller type: HID driver: hid-generic,usbhid
    interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 16mA chip-ID: 0b05:18f3 class-ID: 0300
    serial: <filter>
  Hub-5: 4-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-6: 5-0:1 info: Hi-speed hub with single TT ports: 2 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-7: 6-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-8: 7-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 7-1:2 info: PLX (formerly Oxford ) USB2.0 & 1394 eSATA combo Drive
    type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s chip-ID: 0928:000a
    class-ID: 0806 serial: <filter>
  Device-2: 7-3:3 info: MediaTek Slim Portable DVD Writer type: Mass Storage driver: usb-storage
    interfaces: 1 rev: 2.0 speed: 480 Mb/s power: 500mA chip-ID: 0e8d:1887 class-ID: 0802
    serial: <filter>
  Hub-9: 8-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 50.0 C mobo: 29.0 C gpu: nvidia temp: 33 C
  Fan Speeds (RPM): fan-1: 1004 fan-2: 696 fan-3: 0 fan-4: 0 fan-5: 0 fan-6: 0 gpu: nvidia
    fan: 38%
Repos:
  Packages: 4052 apt: 4026 flatpak: 26
  No active apt repos in: /etc/apt/sources.list
  No active apt repos in: /etc/apt/sources.list.d/audio-recorder-ppa-focal.list
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //packages.linuxmint.com virginia main upstream import backport
    2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  No active apt repos in: /etc/apt/sources.list.d/ondrej-php-focal.list
  No active apt repos in: /etc/apt/sources.list.d/opera-stable.list
  Active apt repos in: /etc/apt/sources.list.d/skype-stable.list
    1: deb [arch=amd64] https: //repo.skype.com/deb stable main
  No active apt repos in: /etc/apt/sources.list.d/strukturag-libde265-focal.list
  No active apt repos in: /etc/apt/sources.list.d/vscode.list
Info:
  Processes: 576 Uptime: 0m wakeups: 6 Memory: 31.24 GiB used: 3.91 GiB (12.5%) Init: systemd
  v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12/7/9 Client: Unknown python3.10 client
  inxi: 3.3.13

Now I will wait to see if you have other suggestions or questions, or if I get another "lockup", I will try to get a good capture of logs. Once again, thank you for your help!

[SMG]

Now I will wait to see if you have other suggestions or questions, or if I get another "lockup", I will try to get a good capture of logs.

No other suggestions at this time.

If it does lock up, give it some time to see if it is just a resource freeze which eventually resolves itself. If you are "unfreezing" it by restarting it, then please run

Code: Select all

journalctl -b -1 | tail -n 100

after you restart the computer.That lists the last 100 lines of the previous boot cycle.

[yjo-jo]

Well, that was quicker than I expected.. although it is sort of fitting the 48 hour pattern. According to the journalctl... the last thing that happened is at 18:20... I was grilling dinner so I didn't know it. When I came back, it was in lockup mode. It was 18:50 (6:50p) at that time. So I went to do something else, but then I needed to get stuff done on my computer so at 19:20 (half hour later) I checked... it was still in the same state... monitor remain black... capslock does not toggle the light... numlock does not toggle the light... I did a hard reset and then ran the journalctl command... I have some substitutes ("MyComputer", "MyUsername", "MyBashfile"). The big repeater in there are the 2 bash files that I run, but I've been running them for at least two years, so I don't know that they would all-of-a-sudden break my computer at the same time that I did the 21.3 upgrade. I don't see anything else that is jumping out. Maybe you can see something?

Code: Select all

Mar 16 17:25:01 MyComputer CRON[13421]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 17:25:01 MyComputer CRON[13422]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 17:25:01 MyComputer CRON[13426]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile1.bash)
Mar 16 17:25:01 MyComputer CRON[13427]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile2.bash)
Mar 16 17:25:01 MyComputer CRON[13422]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 17:25:01 MyComputer CRON[13421]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 17:30:01 MyComputer CRON[13448]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 16 17:30:01 MyComputer CRON[13452]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Mar 16 17:30:01 MyComputer CRON[13450]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 17:30:01 MyComputer CRON[13449]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 17:30:01 MyComputer CRON[13448]: pam_unix(cron:session): session closed for user root
Mar 16 17:30:01 MyComputer CRON[13455]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile2.bash)
Mar 16 17:30:01 MyComputer CRON[13456]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile1.bash)
Mar 16 17:30:01 MyComputer CRON[13449]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 17:30:01 MyComputer CRON[13450]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 17:32:02 MyComputer systemd[1]: Started Run anacron jobs.
Mar 16 17:32:02 MyComputer anacron[13475]: Anacron 2.3 started on 2024-03-16
Mar 16 17:32:02 MyComputer anacron[13475]: Normal exit (0 jobs run)
Mar 16 17:32:02 MyComputer systemd[1]: anacron.service: Deactivated successfully.
Mar 16 17:35:01 MyComputer CRON[13486]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 17:35:01 MyComputer CRON[13487]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 17:35:01 MyComputer CRON[13491]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile1.bash)
Mar 16 17:35:01 MyComputer CRON[13492]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile2.bash)
Mar 16 17:35:01 MyComputer CRON[13487]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 17:35:01 MyComputer CRON[13486]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 17:39:01 MyComputer CRON[13509]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 16 17:39:01 MyComputer CRON[13510]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Mar 16 17:39:01 MyComputer CRON[13509]: pam_unix(cron:session): session closed for user root
Mar 16 17:39:01 MyComputer systemd[1]: Starting Clean php session files...
Mar 16 17:39:01 MyComputer systemd[1]: phpsessionclean.service: Deactivated successfully.
Mar 16 17:39:01 MyComputer systemd[1]: Finished Clean php session files.
Mar 16 17:40:01 MyComputer CRON[13591]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 17:40:01 MyComputer CRON[13592]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 17:40:01 MyComputer CRON[13596]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile2.bash)
Mar 16 17:40:01 MyComputer CRON[13597]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile1.bash)
Mar 16 17:40:01 MyComputer CRON[13591]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 17:40:01 MyComputer CRON[13592]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 17:45:01 MyComputer CRON[13617]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 17:45:01 MyComputer CRON[13618]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 17:45:01 MyComputer CRON[13623]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile2.bash)
Mar 16 17:45:01 MyComputer CRON[13622]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile1.bash)
Mar 16 17:45:01 MyComputer CRON[13617]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 17:45:01 MyComputer CRON[13618]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 17:50:01 MyComputer CRON[13665]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 17:50:01 MyComputer CRON[13666]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 17:50:01 MyComputer CRON[13670]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile1.bash)
Mar 16 17:50:01 MyComputer CRON[13671]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile2.bash)
Mar 16 17:50:01 MyComputer CRON[13666]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 17:50:01 MyComputer CRON[13665]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 17:55:01 MyComputer CRON[13703]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 17:55:01 MyComputer CRON[13704]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 17:55:01 MyComputer CRON[13708]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile2.bash)
Mar 16 17:55:01 MyComputer CRON[13710]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile1.bash)
Mar 16 17:55:01 MyComputer CRON[13703]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 17:55:01 MyComputer CRON[13704]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 18:00:01 MyComputer CRON[13735]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 16 18:00:01 MyComputer CRON[13739]: (root) CMD (timeshift --check --scripted)
Mar 16 18:00:01 MyComputer CRON[13737]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 18:00:01 MyComputer CRON[13736]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 18:00:01 MyComputer CRON[13742]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile2.bash)
Mar 16 18:00:01 MyComputer CRON[13744]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile1.bash)
Mar 16 18:00:01 MyComputer CRON[13736]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 18:00:01 MyComputer CRON[13737]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 18:00:02 MyComputer crontab[13778]: (root) LIST (root)
Mar 16 18:00:02 MyComputer crontab[13779]: (root) LIST (root)
Mar 16 18:00:02 MyComputer systemd[1]: run-timeshift-13739-backup.mount: Deactivated successfully.
Mar 16 18:00:02 MyComputer CRON[13735]: pam_unix(cron:session): session closed for user root
Mar 16 18:05:01 MyComputer CRON[13794]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 18:05:01 MyComputer CRON[13795]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 18:05:01 MyComputer CRON[13798]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile1.bash)
Mar 16 18:05:01 MyComputer CRON[13799]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile2.bash)
Mar 16 18:05:01 MyComputer CRON[13794]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 18:05:01 MyComputer CRON[13795]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 18:09:01 MyComputer CRON[13815]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 16 18:09:01 MyComputer CRON[13816]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Mar 16 18:09:01 MyComputer CRON[13815]: pam_unix(cron:session): session closed for user root
Mar 16 18:09:01 MyComputer systemd[1]: Starting Clean php session files...
Mar 16 18:09:01 MyComputer systemd[1]: phpsessionclean.service: Deactivated successfully.
Mar 16 18:09:01 MyComputer systemd[1]: Finished Clean php session files.
Mar 16 18:10:01 MyComputer CRON[13876]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 18:10:01 MyComputer CRON[13877]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 18:10:01 MyComputer CRON[13880]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile2.bash)
Mar 16 18:10:01 MyComputer CRON[13881]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile1.bash)
Mar 16 18:10:01 MyComputer CRON[13877]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 18:10:01 MyComputer CRON[13876]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 18:15:01 MyComputer CRON[13905]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 18:15:01 MyComputer CRON[13906]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 18:15:01 MyComputer CRON[13909]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile2.bash)
Mar 16 18:15:01 MyComputer CRON[13910]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile1.bash)
Mar 16 18:15:01 MyComputer CRON[13905]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 18:15:01 MyComputer CRON[13906]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 18:17:01 MyComputer CRON[13918]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 16 18:17:01 MyComputer CRON[13919]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Mar 16 18:17:01 MyComputer CRON[13918]: pam_unix(cron:session): session closed for user root
Mar 16 18:20:01 MyComputer CRON[13931]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 18:20:01 MyComputer CRON[13932]: pam_unix(cron:session): session opened for user MyUsername(uid=1000) by (uid=0)
Mar 16 18:20:01 MyComputer CRON[13935]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile1.bash)
Mar 16 18:20:01 MyComputer CRON[13936]: (MyUsername) CMD (/home/MyUsername/Projects/bash/MyBashfile2.bash)
Mar 16 18:20:01 MyComputer CRON[13932]: pam_unix(cron:session): session closed for user MyUsername
Mar 16 18:20:01 MyComputer CRON[13931]: pam_unix(cron:session): session closed for user MyUsername

[SMG]

The big repeater in there are the 2 bash files that I run, but I've been running them for at least two years, so I don't know that they would all-of-a-sudden break my computer at the same time that I did the 21.3 upgrade.

Are those bash files doing any type of network file access? Something which might be done every 48 hours (which seems to be when you notice the problem happening)? I ask that because of what the person in this post discovered.

Maybe you can see something?

My guess would be it is something related to your bash files.

[yjo-jo]

I could certainly try disabling them.
. . .
// Note: update 3/20/24 - I edited this because it describes the scripts which have no impact on the issue nor help in the troubleshooting effort.
// Summary -- scripts do stuff every 5 minutes and are kicked off by a cron job.
// The scripts could trigger events for the cloud service... and from there, I hypothesized...

... Maybe their driver is out of sync with the latest update?

In the meantime, I will disable those scripts and see if the problem continues. Thanks for the new ideas!

[SMG]

... and my cloud service is never out of storage space for me.

Do they do any type of maintenance every 48 hours? Or anything that might happen differently on that (or similar) schedule? Maybe a re-login is necessary?

I don't use cloud services so I cannot offer any specific suggestions.

[yjo-jo]

Do they do any type of maintenance every 48 hours? Or anything that might happen differently on that (or similar) schedule? Maybe a re-login is necessary?

Not that I am aware of. I know *any* change in the directory triggers the service... in my scenario, any time I put a file in a folder-of-the-service from my phone, my computer is alerted... any time I put one in from my computer, my phone is alerted. But my lockup doesn't seem to coincide with any of those events. For now, the scripts are disabled, so it should be easy to see if the lockup continues. I saw that there were 6.5 kernel updates, so I updated and rebooted/re-logins... so now I will wait and report back in a while.

[yjo-jo]

I'm back! You probably were expecting me.

I did the journalctl again. Here you'll see that my bash scripts have not been running. But I don't see anything else that is suspicious other than it seems something ran itself as sudo under my behalf... I wasn't home at the time, so that was curious to me... I didn't know that was a thing.

Also interesting... last time the failure occurred (at least according to the timestamps on journalctl) at 18:20-ish... this time at 18:00... so it's not an exact 48 hours, but it seems to be in that ballpark.

I don't really want to, but I'm starting to think I need to back up all my stuff, wipe the drive and do a fresh install... it has the feeling of one of these things is happening:
1) There is something wrong with this version 21.3, or at least, there is something with it conflicting with something on my system that never occurred before. If this is the case then a fresh-install would still result in the current lockups that I am seeing.
2) There is some carry-over (as I did an "upgrade" from 21.2) from 21.2 that isn't working properly with 21.3. I fresh install in this case should result in things running good again (unless #1 above is true).
3) Perhaps wiping the drive and doing a fresh install of 21.2 is my happiest result. Or, now that I check, it appears my timeshift still has my last 21.2, so maybe just a capture of my existing files and a rollback to 21.2 is a fast and safe plan.

What are your thoughts or ideas, SMG?

Code: Select all

Mar 18 15:39:01 MyComputer systemd[1]: Starting Clean php session files...
Mar 18 15:39:01 MyComputer systemd[1]: phpsessionclean.service: Deactivated successfully.
Mar 18 15:39:01 MyComputer systemd[1]: Finished Clean php session files.
Mar 18 15:39:01 MyComputer CRON[93273]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 18 15:39:01 MyComputer CRON[93274]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Mar 18 15:39:01 MyComputer CRON[93273]: pam_unix(cron:session): session closed for user root
Mar 18 16:00:01 MyComputer CRON[93347]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 18 16:00:01 MyComputer CRON[93348]: (root) CMD (timeshift --check --scripted)
Mar 18 16:00:02 MyComputer crontab[93377]: (root) LIST (root)
Mar 18 16:00:02 MyComputer crontab[93378]: (root) LIST (root)
Mar 18 16:00:02 MyComputer systemd[1]: run-timeshift-93348-backup.mount: Deactivated successfully.
Mar 18 16:00:02 MyComputer CRON[93347]: pam_unix(cron:session): session closed for user root
Mar 18 16:09:01 MyComputer CRON[93455]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 18 16:09:01 MyComputer CRON[93456]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Mar 18 16:09:01 MyComputer CRON[93455]: pam_unix(cron:session): session closed for user root
Mar 18 16:09:29 MyComputer systemd[1]: Starting Clean php session files...
Mar 18 16:09:29 MyComputer systemd[1]: phpsessionclean.service: Deactivated successfully.
Mar 18 16:09:29 MyComputer systemd[1]: Finished Clean php session files.
Mar 18 16:17:01 MyComputer CRON[93529]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 18 16:17:01 MyComputer CRON[93530]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Mar 18 16:17:01 MyComputer CRON[93529]: pam_unix(cron:session): session closed for user root
Mar 18 16:30:01 MyComputer CRON[93614]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 18 16:30:01 MyComputer CRON[93615]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Mar 18 16:30:01 MyComputer CRON[93614]: pam_unix(cron:session): session closed for user root
Mar 18 16:30:29 MyComputer systemd[1]: Started Run anacron jobs.
Mar 18 16:30:29 MyComputer anacron[93620]: Anacron 2.3 started on 2024-03-18
Mar 18 16:30:29 MyComputer anacron[93620]: Normal exit (0 jobs run)
Mar 18 16:30:29 MyComputer systemd[1]: anacron.service: Deactivated successfully.
Mar 18 16:39:01 MyComputer CRON[93664]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 18 16:39:01 MyComputer CRON[93665]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Mar 18 16:39:01 MyComputer CRON[93664]: pam_unix(cron:session): session closed for user root
Mar 18 16:39:29 MyComputer systemd[1]: Starting Clean php session files...
Mar 18 16:39:29 MyComputer systemd[1]: phpsessionclean.service: Deactivated successfully.
Mar 18 16:39:29 MyComputer systemd[1]: Finished Clean php session files.
Mar 18 17:00:01 MyComputer CRON[93809]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 18 17:00:01 MyComputer CRON[93810]: (root) CMD (timeshift --check --scripted)
Mar 18 17:00:01 MyComputer crontab[93839]: (root) LIST (root)
Mar 18 17:00:01 MyComputer crontab[93840]: (root) LIST (root)
Mar 18 17:00:01 MyComputer systemd[1]: run-timeshift-93810-backup.mount: Deactivated successfully.
Mar 18 17:00:01 MyComputer CRON[93809]: pam_unix(cron:session): session closed for user root
Mar 18 17:09:01 MyComputer CRON[93915]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 18 17:09:01 MyComputer CRON[93916]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Mar 18 17:09:01 MyComputer CRON[93915]: pam_unix(cron:session): session closed for user root
Mar 18 17:09:29 MyComputer systemd[1]: Starting Clean php session files...
Mar 18 17:09:29 MyComputer systemd[1]: phpsessionclean.service: Deactivated successfully.
Mar 18 17:09:29 MyComputer systemd[1]: Finished Clean php session files.
Mar 18 17:12:31 MyComputer sudo[93978]: userName : PWD=/home/userName ; USER=root ; COMMAND=/usr/lib/linuxmint/mintUpdate/dpkg_lock_check.sh
Mar 18 17:12:31 MyComputer sudo[93978]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Mar 18 17:12:31 MyComputer sudo[93978]: pam_unix(sudo:session): session closed for user root
Mar 18 17:12:31 MyComputer sudo[93981]: userName : PWD=/home/userName ; USER=root ; COMMAND=/usr/bin/mint-refresh-cache
Mar 18 17:12:31 MyComputer sudo[93981]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Mar 18 17:12:31 MyComputer systemd[1]: Starting Update APT News...
Mar 18 17:12:31 MyComputer systemd[1]: Starting Update the local ESM caches...
Mar 18 17:12:31 MyComputer systemd[1]: esm-cache.service: Deactivated successfully.
Mar 18 17:12:31 MyComputer systemd[1]: Finished Update the local ESM caches.
Mar 18 17:12:31 MyComputer systemd[1]: apt-news.service: Deactivated successfully.
Mar 18 17:12:31 MyComputer systemd[1]: Finished Update APT News.
Mar 18 17:12:36 MyComputer systemd-resolved[1172]: Using degraded feature set UDP instead of TCP for DNS server xx.xx.xx.xx.
Mar 18 17:12:51 MyComputer sudo[93981]: pam_unix(sudo:session): session closed for user root
Mar 18 17:12:51 MyComputer dbus-daemon[1240]: [system] Activating via systemd: service name='org.freedesktop.Flatpak.SystemHelper' unit='flatpak-system-helper.service' requested by ':1.894' (uid=1000 pid=94622 comm="flatpak-update-worker                             " label="unconfined")
Mar 18 17:12:52 MyComputer systemd[1]: Starting flatpak system helper...
Mar 18 17:12:52 MyComputer dbus-daemon[1240]: [system] Successfully activated service 'org.freedesktop.Flatpak.SystemHelper'
Mar 18 17:12:52 MyComputer systemd[1]: Started flatpak system helper.
Mar 18 17:12:55 MyComputer pdate-worker[94622]: libostree pull from 'flathub' for appstream2/x86_64 complete
                                                 security: GPG: summary+commit 
                                                 security: SIGN: disabled http: TLS
                                                 delta: parts: 1 loose: 4
                                                 transfer: secs: 0 size: 7.6 MB
Mar 18 17:12:55 MyComputer pdate-worker[94622]: /var/tmp/flatpak-cache-H9UUK2/repo-wliIzd: Pulled appstream2/x86_64 from flathub
Mar 18 17:12:55 MyComputer flatpak-system-helper[94626]: system: Pulled appstream2/x86_64 from /var/tmp/flatpak-cache-H9UUK2/repo-wliIzd
Mar 18 17:13:00 MyComputer dbus-daemon[1240]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.898' (uid=1000 pid=94697 comm="flatpak-update-worker                             " label="unconfined")
Mar 18 17:13:00 MyComputer systemd[1]: Starting Locale Service...
Mar 18 17:13:00 MyComputer dbus-daemon[1240]: [system] Successfully activated service 'org.freedesktop.locale1'
Mar 18 17:13:00 MyComputer systemd[1]: Started Locale Service.
Mar 18 17:13:30 MyComputer systemd[1]: systemd-localed.service: Deactivated successfully.
Mar 18 17:17:01 MyComputer CRON[94732]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 18 17:17:01 MyComputer CRON[94733]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Mar 18 17:17:01 MyComputer CRON[94732]: pam_unix(cron:session): session closed for user root
Mar 18 17:22:55 MyComputer systemd[1]: flatpak-system-helper.service: Deactivated successfully.
Mar 18 17:22:55 MyComputer systemd[1]: flatpak-system-helper.service: Consumed 2.195s CPU time.
Mar 18 17:30:01 MyComputer CRON[94811]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 18 17:30:01 MyComputer CRON[94812]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Mar 18 17:30:01 MyComputer CRON[94811]: pam_unix(cron:session): session closed for user root
Mar 18 17:30:29 MyComputer systemd[1]: Started Run anacron jobs.
Mar 18 17:30:29 MyComputer anacron[94815]: Anacron 2.3 started on 2024-03-18
Mar 18 17:30:29 MyComputer anacron[94815]: Normal exit (0 jobs run)
Mar 18 17:30:29 MyComputer systemd[1]: anacron.service: Deactivated successfully.
Mar 18 17:39:01 MyComputer CRON[94872]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 18 17:39:01 MyComputer CRON[94873]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Mar 18 17:39:01 MyComputer CRON[94872]: pam_unix(cron:session): session closed for user root
Mar 18 17:39:01 MyComputer systemd[1]: Starting Clean php session files...
Mar 18 17:39:01 MyComputer systemd[1]: phpsessionclean.service: Deactivated successfully.
Mar 18 17:39:01 MyComputer systemd[1]: Finished Clean php session files.
Mar 18 17:55:01 MyComputer kernel: perf: interrupt took too long (2539 > 2500), lowering kernel.perf_event_max_sample_rate to 78750
Mar 18 18:00:01 MyComputer CRON[95001]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 18 18:00:01 MyComputer CRON[95002]: (root) CMD (timeshift --check --scripted)
Mar 18 18:00:01 MyComputer crontab[95031]: (root) LIST (root)
Mar 18 18:00:01 MyComputer crontab[95032]: (root) LIST (root)
Mar 18 18:00:01 MyComputer systemd[1]: run-timeshift-95002-backup.mount: Deactivated successfully.
Mar 18 18:00:01 MyComputer CRON[95001]: pam_unix(cron:session): session closed for user root

[SMG]

I did the journalctl again. Here you'll see that my bash scripts have not been running. But I don't see anything else that is suspicious other than it seems something ran itself as sudo under my behalf... I wasn't home at the time, so that was curious to me... I didn't know that was a thing.

Timeshift (to check and see if it should do a snapshot) and Update Manager (to check for updates) are two apps which come to mind that might do that. From the log you posted, it appears it was Timeshift.

Also interesting... last time the failure occurred (at least according to the timestamps on journalctl) at 18:20-ish... this time at 18:00... so it's not an exact 48 hours, but it seems to be in that ballpark.

That is quite curious at how close the timing is.

I don't really want to, but I'm starting to think I need to back up all my stuff, wipe the drive and do a fresh install... it has the feeling of one of these things is happening:
1) There is something wrong with this version 21.3, or at least, there is something with it conflicting with something on my system that never occurred before. If this is the case then a fresh-install would still result in the current lockups that I am seeing.
2) There is some carry-over (as I did an "upgrade" from 21.2) from 21.2 that isn't working properly with 21.3. I fresh install in this case should result in things running good again (unless #1 above is true).
3) Perhaps wiping the drive and doing a fresh install of 21.2 is my happiest result. Or, now that I check, it appears my timeshift still has my last 21.2, so maybe just a capture of my existing files and a rollback to 21.2 is a fast and safe plan.

What are your thoughts or ideas, SMG?

If it was working before the upgrade from LM21.2 to LM21.3 and you have a snapshot prior to your upgrade, I'd roll back to that snapshot as the first option. Then if that does not work, we'll know something else is happening (maybe a subsequent package update of some type that applies to all versions of LM21) may be the issue.

[yjo-jo]

Once again, thank you for your tips and suggestions. Something you said made me think I should have had a #4 to my previous list:
4) Maybe there is a hardware failure that just happened to start going bad at the same time as my 21.3 upgrade. I'd think the timing here is pretty unusual, but you never know. If this is the case, then a rollback (#3) would show the problem still happening.

I think I will do #3, but probably not today... maybe by this weekend and then I can report on if the problem is gone or not.

Thanks again!

[Reddog1]

Maybe I'm reading this wrong, or missed something, but if everything was working in 21.2, why did you feel the need to upgrade to 21.3?

Both 21.2 and 21.3 are supported for the same amount of time. Both versions will go end of life at the exact same time. Upgrades complicate things which don't need complications.

If you have a timeshift, shift back to what worked and ignore the update to 21.3. If stuff is working, there is absolutely zero reason to update. The only way I would use 21.3 is if I was doing a clean install on a new system, and even then I'd think about it long and hard because 21.2 is working perfectly on my systems, now, and I trust it. I haven't upgraded from 20.2 to 21 on 2 of my machines, and won't until 20 goes EOL, either. If it works--don't fix it......

This 'upgrade' thing seems to me to be a thing for refugees from Windows. If a system is supported, and all the hardware is working, upgrading to the latest and greatest just doesn't make any sense at all. But that's me......

Unhelpful, I know, but Rant over.......

[yjo-jo]

there is absolutely zero reason to update

Any time you deal in absolutes, you're setting yourself up for failure. Also, you know nothing of me or what I do. I'm a software developer and I like to have my hands on the latest things... so there's a reason to update. Yes, I understand the risks. But I like to understand and see the latest things that are being worked on by people in my field.

Unhelpful, I know.......

At least you weren't entirely wrong.

[Reddog1]

Well? Did a roll-back fix it? Or did you reinstall, and if so, did that fix it? If the latter, did you clean-install 21.3?

[yjo-jo]

Unfortunately, I didn't make it that far yet.... I think I need a block of uninterrupted time, and don't know if I'll see that until the weekend. On a sidenote, it has locked up once since the last lockup (above), so it makes me want to get it done soon.

I wanted to just do the roll-back idea, but as I mentioned I use Timeshift, so I lose all items that I've changed since the 21.2. I was just going to use "find" and grab a list of what's changed, pull it to the side, rollback, and then take the sideline items and put back in place... but "find" tells me 44,000 items have changed since my 21.2 snapshot Of course, I didn't directly make all those changes, but there are enough "changed" items, that I don't know what ones are important and which ones aren't.

Decisions decisions!!!

[yjo-jo]

Just to update, I'm rolled back to my 2/28 LM 21.2. So now let's see if I'm back in 2 days with any new lockup reports. If I am, then I think it is starting to look like a hardware problem, although, very odd that the timing would be that it started happening right after my 21.3 install. I guess I'll find out. If not, then I have inconclusive evidence of what the conflict was within my setup and 21.3... and I'm not likely to go back!