9
Lock up problem (lemmy.world)
submitted 7 months ago by to c/linux4noobs@lemmy.world
18 comments fedilink hide all child comments
 

Hi guys, been having a problem for a week now in fedora 43.

After half an hour of light use, my kde keyboard starts crashing at regular intervals, the taskbar is unresponsive, and the shutdown greeter will crash if i try to restart or shut down. I have to power cycle the system to turn it off, not the best.

Looking for anyone also experiencing the problem has not yielded any hits, so I'm posting here πŸ˜…

Thus far i have tried: -Restarting -Disabling Firefox video decoding (closest fix i could find in searches) -Rolling back to my previous Friday backups

The issue persists πŸ˜“

I don't know enough about Linux to troubleshoot the problem effectively πŸ˜…

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 7 months ago* (last edited 7 months ago) (10 children)

What does β€œjournalctl -b -1 -e | less” say when you run it after a crash? Like the last 20 lines.

Also when it crashes can you get to a different tty by pressing ctrl-alt-F2 or is the system completely locked?

  • permalink
  • fedilink
  • source
  • hideshow 10 child comments
    •
  • [–] [S] 1 point 7 months ago (8 children)

    Here's what I got from that command. Everything below the "Shutting down" command. Lookint through what it provided... there is a LOT in that search that I don't understand. It looks like it recorded it from last night (when I had not experienced the issue) instead of just now.

    results

    Mar 26 11:50:45 fedora systemd[1]: Stopping systemd-zram-setup@zram0.service - Create swap on /dev/zram0...
Mar 26 11:50:45 fedora kernel: zram0: detected capacity change from 16777216 to 0
Mar 26 11:50:45 fedora systemd[1]: boot.mount: Deactivated successfully.
Mar 26 11:50:45 fedora systemd[1]: Unmounted boot.mount - /boot.
Mar 26 11:50:45 fedora systemd[1]: Reached target umount.target - Unmount All Filesystems.
Mar 26 11:50:45 fedora systemd[1]: systemd-fsck@dev-disk-by\x2duuid-48c1277e\x2d11b4\x2d4960\x2da835\x2d0cfa06b830e2.service: Deactivated successfully.
Mar 26 11:50:45 fedora systemd[1]: Stopped systemd-fsck@dev-disk-by\x2duuid-48c1277e\x2d11b4\x2d4960\x2da835\x2d0cfa06b830e2.service - File System Check on /dev/disk/by-uuid/48c1277e-11b4-4960-a835-0cfa06b830e2.
Mar 26 11:50:45 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck@dev-disk-by\x2duuid-48c1277e\x2d11b4\x2d4960\x2da835\x2d0cfa06b830e2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora systemd[1]: Removed slice system-systemd\x2dfsck.slice - Slice /system/systemd-fsck.
Mar 26 11:50:45 fedora systemd[1]: Stopped target local-fs-pre.target - Preparation for Local File Systems.
Mar 26 11:50:45 fedora kernel: audit: type=1131 audit(1774551045.097:273): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck@dev-disk-by\x2duuid-48c1277e\x2d11b4\x2d4960\x2da835\x2d0cfa06b830e2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora systemd[1]: Stopping lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Mar 26 11:50:45 fedora systemd[1]: systemd-remount-fs.service: Deactivated successfully.
Mar 26 11:50:45 fedora systemd[1]: Stopped systemd-remount-fs.service - Remount Root and Kernel File Systems.
Mar 26 11:50:45 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully.
Mar 26 11:50:45 fedora systemd[1]: Stopped systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev.
Mar 26 11:50:45 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora systemd[1]: systemd-tmpfiles-setup-dev-early.service: Deactivated successfully.
Mar 26 11:50:45 fedora systemd[1]: Stopped systemd-tmpfiles-setup-dev-early.service - Create Static Device Nodes in /dev gracefully.
Mar 26 11:50:45 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev-early comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora kernel: audit: type=1131 audit(1774551045.098:274): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora kernel: audit: type=1131 audit(1774551045.098:275): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora kernel: audit: type=1131 audit(1774551045.098:276): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev-early comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora systemd[1]: systemd-zram-setup@zram0.service: Deactivated successfully.
Mar 26 11:50:45 fedora systemd[1]: Stopped systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Mar 26 11:50:45 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-zram-setup@zram0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora kernel: audit: type=1131 audit(1774551045.120:277): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-zram-setup@zram0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora systemd[1]: Removed slice system-systemd\x2dzram\x2dsetup.slice - Slice /system/systemd-zram-setup.
Mar 26 11:50:45 fedora systemd[1]: lvm2-monitor.service: Deactivated successfully.
Mar 26 11:50:45 fedora systemd[1]: Stopped lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Mar 26 11:50:45 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora systemd[1]: Reached target shutdown.target - System Shutdown.
Mar 26 11:50:45 fedora systemd[1]: Reached target final.target - Late Shutdown Services.
Mar 26 11:50:45 fedora systemd[1]: systemd-poweroff.service: Deactivated successfully.
Mar 26 11:50:45 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-poweroff comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-poweroff comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora systemd[1]: Finished systemd-poweroff.service - System Power Off.
Mar 26 11:50:45 fedora systemd[1]: Reached target poweroff.target - System Power Off.
Mar 26 11:50:45 fedora systemd[1]: Shutting down.
Mar 26 11:50:45 fedora audit: BPF prog-id=60 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=59 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=52 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=51 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=55 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=54 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=69 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=68 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=45 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=47 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=46 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=73 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=72 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=48 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=50 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=49 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=67 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=66 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=41 op=UNLOAD
Mar 26 11:50:45 fedora systemd-shutdown[1]: Syncing filesystems and block devices.
Mar 26 11:50:45 fedora systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Mar 26 11:50:45 fedora systemd-udevd[676]: Failed to remove file descriptor "config-serialization" from the store, ignoring: Connection refused
Mar 26 11:50:45 fedora systemd-journald[637]: Received SIGTERM from PID 1 (systemd-shutdow).
Mar 26 11:50:45 fedora systemd-journald[637]: Journal stopped
(END)

    πŸ˜… sorry if I grabbed too much

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 1 point 7 months ago* (7 children)

    The command needs to be run after you crash. It's showing the logs of the last time you boot (That's the "-b -1") which is why you're seeing yesterday's log.

    I don't see anything crazy in this output.

    You can change the options to trawl the logs if you like. type in "man journalctl" and you'll get a man page entry explaining what each of the options and how to use them.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] [S] 1 point 7 months ago* (last edited 7 months ago) (6 children)

    Well, it's not a hard crash. I lose functionality on my taskbar, and can't run any programs πŸ˜“

    Can't even shut down πŸ˜…

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 1 point 7 months ago (5 children)

    When it happens can you swap to a different tty by pressing CTRL-ALT-F2 after things stop responding? If you get a terminal with a login screen then that means your desktop environment is hanging, not your computer.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] [S] 1 point 7 months ago (4 children)

    Nothing happens. I thought i might have had the wrong hotkeys and had to double check

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 7 months ago* (3 children)

    Then I would check the ram to make sure it's ok. Download memtest86+ load it on a thumbdrive and boot from that. Then run the memtests. It will tell you if your memory modules are fucked or not.

    The tests may take some time to run so go grab a beer while you wait.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] [S] 1 point 7 months ago (1 child)

    Memtest just finished. Everything is fine

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 7 months ago

    My next test would be trying to a live installation in order to see if it's hardware related or software.

    Boot into a live cd (I would use one that is the same distro as you already have) and do what you normally do. See if the machine locks up. If it doesn't then you've probably got some broken setting or program crashing your machine. If it does crash then some other hardware is causing the issue. You'd have to start taking out each piece of hardware out of the system to see if your crash is still there or not.

  • permalink
  • fedilink
  • source
  • parent