Skip to main content ↑ ↓
Topic: uninvited lockup or WTF (Read 387 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

uninvited lockup or WTF

I don't know what to call this but it is predictable. I had a hunch when I left my desktop running Artix after a reboot to find info for my other posting about signatures and integrity-checks. Sure enough, when I just returned to the desktop it was locked up.

Box: AMD 8-core in Asus Crosshair-IV Formula, 16gb.

The mouse and keyboard are dead, upon touching some key or mouse button I did hear the fans starting up again but that is all. I see no other way out other than a hard reset.

This could be some sleep or suspend state or other similar crap that should never be on by default, I cannot tell but am pretty sure that a hard reset will result in the mounted but otherwise unused data drive needing a journal replay and THAT is possibly the first step in debugging a very old and long Artix and journal issues history which has seen a barely used WD-Blue spinner unnecessarily replacing and older one.

Who, has loved us more?

Re: uninvited lockup or WTF

Reply #2 –
Quote from: tintin – on
Which graphics processor?
Which Linux kernel?

At the moment I'm booted into Tumbleweed
 
openSUSE Tumbleweed , Kernel=6.5.9-1-default on x86_64,
DM=sddm, DE=KDE, ST=x11,grub2, GPT, BIOS-boot

tha card _was_ nvidia,  swapped out for a Polaris 20XL [Radeon RTX 580 2048SP]

I'm onto something but far from nailing it.  When my latest Artix (kde) installation goes to suspend or sleep (or whatever it is that is default) I cannot recover from it. When rebooted the data drive which is NOT is use but merely mounted in fstab for possible use needs a journal replay. All files on that data drive belong to a user and a group not yet defined in Artix (that comes after tweaking) and writable by them. I cannot state that the behavior is limited to Artix. For a while I thougt the disk was high-time (11k hours) so I swapped that out too for an identical 2tb WD-Blue spinner with only 200 hours. No joy.
 
 
Who, has loved us more?

Re: uninvited lockup or WTF

Reply #3 –
Arch wiki:
"File systems based on copy-on-write (also known as write-anywhere), such as Reiser4, Btrfs, Bcachefs and ZFS, have no need to use traditional journal to protect metadata, because they are never updated in-place. Although Btrfs still has a journal-like log tree, it is only used to speed-up fdatasync/fsync."
That's why I usually use BTRFS over EXT where possible, as it's far more inherently resistant to unplanned shutdowns as the data is always in a consistent state.

There are probably some settings related to power management in the desktop settings, and also in the hardware's BIOS (EFI) menu. Some suspend options need a large swap partition to be set up and working, the size will vary according to the amount of your installed RAM.
 

Re: uninvited lockup or WTF

Reply #4 –
There currently seems to be an issue with KDE/SDDM and resuming suspended systems.

artist