SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Don't forget post #5. Hardware issues are a common cause of freezing, which here seems all the more likely because different distros misbehave similarly.[/QUOTE]
I didn't because I'm afraid I'll end up ruining the computer because I've never messed with its parts and I don't have a good knowledge
steam and gnome are both running? Yes, 3.7 GB RAM is just insufficient. You might want to add some swap, probably that will help a bit.
What is the result of a simple free -h ?
steam and gnome are both running? Yes, 3.7 GB RAM is just insufficient. You might want to add some swap, probably that will help a bit.
What is the result of a simple free -h ?
Mem
Total 3,7 Gi
Used 1,8 Gi
Free 710 Mi
Shared 266 Mi
Buff/cache 1,2 Gi
Avaiable 1,5 Gi
In my case when freeze issue happens the entire system gets frozen even keyboard and mouse.
Have you ever tried waiting it out?
Maybe 10, 20 minutes?
Have you tried switching to another tty (Ctrl-Alt-F2), execute 'top' or 'htop' to see what's eating resources, and kill that?
Have you ever tried waiting it out?
Maybe 10, 20 minutes?
Have you tried switching to another tty (Ctrl-Alt-F2), execute 'top' or 'htop' to see what's eating resources, and kill that?
Less than 10 minutes, but still I don't think waiting for some more minutes is really necessary. And tty's commands doesn't work when it freezes, only REISUB works
Less than 10 minutes, but still I don't think waiting for some more minutes is really necessary. And tty's commands doesn't work when it freezes, only REISUB works
Waiting more may help to identify if it was a real crash/lockup or just the host was busy with some very important task. Next time you may try to wait an hour or even more (just go to have a lunch or whatever) to see if it can recover. Also you may try to use a smartphone or other pc to connect to it.
Another possible issue could be excessive swapping, or just insufficient memory. I would expect the disk drive light to stay on when this happens if that is the case. If so you might check the output from this command.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.