Random Cancelable Logouts

Hello, I'm new to Linux as a primary driver OS, and occasionally the system will start to logout. This is cancelable and looking around on the arch forums, can't seem to find an analogous situation (much of what I can find is immediate logouts, freezes or crashes, which my machine isn't doing). The advice there had me sticking my nose into some logs but I can't understand much of what's there, so I figure I'll ask here.

╰─λ garuda-inxi
System:
Kernel: 6.0.1-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=8a427227-28ba-444a-8f0a-217559488779 rw rootflags=subvol=@
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
loglevel=3
Desktop: KDE Plasma v: 5.26.0 tk: Qt v: 5.15.6 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: ASUS product: All Series v: N/A
serial: <superuser required>
Mobo: ASUSTeK model: H87M-E v: Rev X.0x serial: <superuser required>
UEFI: American Megatrends v: 0401 date: 04/10/2013
Battery:
Device-1: hidpp_battery_0 model: Logitech Marathon Mouse/Performance Plus
M705 serial: <filter> charge: 10% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: Intel Core i5-4570 bits: 64 type: MCP arch: Haswell
gen: core 4 level: v3 note: check built: 2013-15 process: Intel 22nm
family: 6 model-id: 0x3C (60) stepping: 3 microcode: 0x28
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB
desc: 1x6 MiB
Speed (MHz): avg: 3498 high: 3600 min/max: 800/3600 scaling:
driver: intel_cpufreq governor: performance cores: 1: 3600 2: 3193 3: 3600
4: 3600 bogomips: 25542
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
disabled
Type: mds mitigation: Clear CPU buffers; SMT disabled
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Unknown: No mitigations
Type: retbleed status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
STIBP: disabled, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] vendor: Tul /
PowerColor driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: HDMI-A-1 empty: DP-1,DP-2,DP-3 bus-ID: 03:00.0
chip-ID: 1002:73ff class-ID: 0300
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.3
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1440x900 s-dpi: 96 s-size: 381x238mm (15.00x9.37")
s-diag: 449mm (17.69")
Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: Dell E1911 serial: <filter>
built: 2012 res: 1440x900 hz: 60 dpi: 90 gamma: 1.2
size: 408x255mm (16.06x10.04") diag: 481mm (18.9") ratio: 16:10 modes:
max: 1440x900 min: 720x400
OpenGL: renderer: AMD Radeon RX 6600 (navi23 LLVM 14.0.6 DRM 3.48
6.0.1-zen2-1-zen) v: 4.6 Mesa 22.2.1 direct render: Yes
Audio:
Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 3-10:6 chip-ID: 1130:1620
bus-ID: 00:1b.0 chip-ID: 8086:8c20 class-ID: 0300 class-ID: 0403
Device-2: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel
pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-3: Tenx USB AUDIO type: USB
driver: hid-generic,snd-usb-audio,usbhid
Device-4: Samson GoMic compact condenser microphone type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 3-9:4 chip-ID: 17a0:0302
class-ID: 0300
Sound API: ALSA v: k6.0.1-zen2-1-zen running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.59 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK H81M-C driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: d000 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp5s0 state: down mac: <filter>
Device-2: Qualcomm Atheros AR93xx Wireless Network Adapter driver: ath9k
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 06:00.0
chip-ID: 168c:0030 class-ID: 0280
IF: wlp6s0 state: up mac: <filter>
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB
driver: btusb v: 0.8 bus-ID: 3-4.4.3:9 chip-ID: 0a12:0001 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: <filter>
Drives:
Local Storage: total: 6.37 TiB used: 61.5 GiB (0.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD60EZAZ-00SF3B0 size: 5.46 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
rev: 0A80 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 2B6Q scheme: GPT
Partition:
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 61.5 GiB
(6.6%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 608 KiB
(0.2%) fs: vfat dev: /dev/sdb1 maj-min: 8:17
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 61.5
GiB (6.6%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 61.5
GiB (6.6%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 61.5
GiB (6.6%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 7.7 GiB used: 1.5 MiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 42.0 C mobo: N/A gpu: amdgpu temp: 35.0 C
mem: 32.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Info:
Processes: 239 Uptime: 3m wakeups: 10 Memory: 7.7 GiB used: 2.43 GiB
(31.6%) Init: systemd v: 251 default: graphical tool: systemctl
Compilers: gcc: 12.2.0 Packages: pm: pacman pkgs: 1923 libs: 546
tools: octopi,paru Shell: fish v: 3.5.1 default: Bash v: 5.1.16
running-in: konsole inxi: 3.3.22
Garuda (2.6.8-1):
System install date:     2022-10-14
Last full system update: 2022-10-14
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       No/Undetected
Snapshots:               Timeshift
Failed units:

Whilest I can't be the one to help, I can say that more information is needed about the problem. What are you doing when that logout "popup" comes around? amongst other details.

Typically I am interacting with the system in some way. Writing the above post had the system attempt to log out 5 times with no real rhyme or reason (moving the mousewheel, typing text, left clicking on links) but the time between that post and this one has seen 0, as I was not doing anything. Further I have some games I play, and while playing the game a system logout has not been attempted.

But outside of that I don't know what information I need to provide because I have no idea what information is useful as I've only been running the system for maybe 10-14 hours over the last 4 days (which is when I installed the os).

updating MIGHT be a good place to start. if you go into the Garuda Welcome app and select Garuda Assistant on the maintenance tab(one that opens by default) and click system update, you won't need to touch the terminal(except to enter your password). if you feel more comfortable in a terminal window simply try running update

Updating did not address the issue.

Any chance to find something newer?
At a very quick search I saw this one:
https://www.asus.com/us/SupportOnly/H87M-E/HelpDesk_BIOS/

2 Likes

So, an update. I haven't tried flashing the motherboard bios, since that's apparently very risky, but in cleaning up processes that were active but not doing anything I pulled Conky from the startup sequence, as it was broken and not rendering what it was supposed to, and then rebooted. This solved the issue, as the machine has been in use for the past 3 days without a single random logout attempted.

This suggests that something may have been wrong with the conky setup. If you wish this to be a subject of troubleshooting, I would need package info (version etc) and posting of the conky script. At the same time, any wishes for your resultant conky might be achievable as well. Your machine - your way, of course :grin:

3 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.