Hi there,
Today has been the second time that OpenSuse Leap 15.5 has frozen completely and I had to hit the reset button to get out of it. How can I diagnose the cause of this unpleasant experience?
@Mamunson Hi, you might want to add some additional information, Desktop environment in use (if any), hardware details and what you tasks were running?
You could also look at the bootlog -1 in reverse (last entry backwards) to see if there is any information on what caused the freezeâŚ
journalctl -r -b -1
I get: âSpecifying boot ID or boot offset has no effect, no persistent journal was foundâ when I type: journalctl -r -b -1
I use KDE as my desktop environment. My PC is 11 years old (used only for office applications so no games or video editing and never had issues when I had windows 10 installed on it a couple of months ago). Itâs AMD Dual Core Processor 3.6 GHz, 8 GB DDR3 RAM, Graphics integrated into the CPU, 500 SSD from Intenso (bought a couple of months ago) I was running Brave with eight tabs, VS Studio Code, Gimp, and Signal for Desktop when it crashed.
@Mamunson Ahh, ok, well have a look at this thread about adding if you want a persistent journal https://forums.opensuse.org/t/setting-up-boot-logging-and-pruning-logs/168580
If it does it again, then might be able to catch somethingâŚ
So did you check sensors output, nothing over heating, RAM ok? Iâm guessing you have some swap with 8GB of ram?
1 Like
Any keyboard LED blinking when this happens?
No heating issues as the CPU has large cooler. Mouse and Keyboard are all working fine. I always have 4 GB of unused RAM even when multitasking (according to the system monitor app).
None at all. Keyboard works fine. It just froze and wouldnât react to keyboard and mouse commands.
1 Like
Given that, youâve setup the Kernel with the YaST Kernel setting âactivate the SysRq keysâ â
- Regain control of the Keyboard and Mouse:
[Alt]+[SysRq]+r
- Switch to a VT and dump the current tasks to the Console screen_
[Alt]+[SysRq]+t
Alternatively, after regaining control over the Keyboard and Mouse â
[Ctrl]+[Alt]+[Delete]+[Delete]
Press the [Delete] key twice âŚ
This should kill the Display Manager and, you can then examine the systemd Journals (both System and User) for any indications as to the cause of this issue.
Many thanks to all of you for the support. I shall study the resources you provided.
Typed: sudo zypper refresh sudo zypper list-updates
and got this:
Repository 'openSUSE-Leap-15.5-1' is invalid.
[openSUSE-Leap-15.5-1|hd:/?device=/dev/disk/by-id/dm-name-ventoy] Valid metadata not found at specified URL
History:
- Unknown error reading from 'hd:/?device=/dev/disk/by-id/dm-name-ventoy'
- Empty destination in URI: hd:/?device=/dev/disk/by-id/dm-name-ventoy
Please check if the URIs defined for this repository are pointing to a valid repository.
This is your installation DVD/USB. You need to disable/remove this entry from your repo listâŚ
Thanks for your support, I disabled it from the software repository in Yast.
While Mamunson is working I just wanted to add that I have the same problem.
The system freezes either being left logged out overnight or even just left for an hour or so.
My desktop power management settings have the screen Energy Savings set to switch off after 20 mins but the Activity Power Settings are set with a special behaviour set to Never shut down or let it go to sleep and Pause media players when suspending which is enabled.
Even so the screen does go dark after a while. When I then wake it up I must log in unless I find the system dead in which case I cannot do anything.
Ctrl+SysReq+r does nothing, the only key sequence is the final Ctrl+SysReq+b which forces a re-boot.
Since I now have the logging set up correctly I am forwarding the log file from the command:-
journalctl -r -b -1
https://paste.opensuse.org/2f2b5deb4f60
or
https://susepaste.org/2f2b5deb4f60
1 Like
Further to the above, when the system has frozen I can use my laptop and connect to the frozen machine using ssl but I have am not sure what command to try to wake up the machine. What should I try first?
I would check if you are running out of memory, it would not surprise me running this in parallel. One way to do that is to start the KDE system monitor and then select the âHistoryâ tab, the middel graph should show the memory and usage over time. Keep that visible somewhere on the screen and have a look when the problem happens.
Linux is quite bad in handling memory âoverflowâ in my opinion, high CPU âoverflowâ is never a big problem but too less memory can really hang things.
What I did for my 9 year old PC is have a look at the second hand markt and there I could find some cheap memory modules. Upgraded from 8 to 6 and later even to 32 GB.
1 Like
@marel Hi, Thanks for your input. Attached is a screenshot
@Mamunson If you load the system up, do you see it go over 4GB of usage without swap increasing? The flat line looks suspicious, almost like itâs only using 4GB of RAMâŚ
What does inxi say about the memory, run as root user, you may also need to install dmidecode.
inxi -mxxx
1 Like
First, check whatâs hogging the resources â youâll need to execute âsu --loginâ â
- Execute âtopâ to see whatâs hogging the CPU and memory.
- Execute âiotopâ to see whatâs hogging the I/O resources â you may have to install it â the network is working â logging in via SSH has proved that âŚ
Then, restart the Display Manager â âsystemctl restart display-manager.serviceâ
@Budgie2 Disable all power management stuff and see if that isolates the issue, just turn off the monitor manuallyâŚ
Hi Malcolm,
Thanks for the reply. I rudely butted into this thread thinking it might be relevant to my problem but I see possibly not, so I started a new thread when I could not even log in. Please could I continue in that thread as my problem is not likely to be a memory problem.
I have added some basic data to my other thread.