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.
I don't know why but even Opensuse Leap 15.3 like all the others distros freezes randomly and keyboard doesn't work when this issue occurs. I tried all journalctl commands and i can't get any clues. I think i should tell you guys some important things about my situation:
1- I have installed NVIDIA Proprietary drivers
2- my microcode is at the latest version
3- my hard disk and my RAM are fine
4- I don't have C6 state or Power Idle Supply Control on my BIOS
I mainly use openSUSE 15.3, and I have random freezes too. I have 5.3.18-150300.59.43-default. Graphic hardware is: nVidia GK208B [GeForce GT 710]. Although I have an AMD CPU. When a freeze occurs, after I've rebooted, if I consult /var/log/warn, I see numerous complaints about the X-Window and Plasma environment, leading up to the time of the freeze. Also, I often experience the freeze after some transition in the X-Window/Plasma environment. E.G., if a notification pops up letting me know that there are new patches to apply, sometimes right there, it will freeze.
I've had some problems with some NVidia drivers in the past. But whether I use NVidia drivers or Nouveau, it happens.
That tiny bit of log tells us virtually nothing. You should pastebin the whole dmesg and/or journal -b if you want a shot at someone recognizing a problem. This is easy in most distros. In openSUSE:
Failing RAM, overheating components, and unstable PSU voltage are common causes of random freezing. Use memtest86 for testing RAM. If you don't have another PSU to swap in, you have no PSU tester, and yours isn't young any more, at least check it for obviously deficient electrolytic capacitors' telltale swollen tops or oozing, and for excessive dust buildup causing overheating. A ten year old PC that's never been opened could have pretty hefty dust buildup inside causing component overheating.
7029 of 11988 lines (58.6%) in that dmesg are about NetworkManager and 'set hostname', with 7918 total NetworkManager lines, making NetworkManager suspect of excess demands on system resources.
Do you know why acpi=force is included on the linu line in Grub? If you don't, try booting without it to see if it helps.
Do you know why you're running on the preempt kernel instead of the default? If not, try kernel-default.
blk_update_request: I/O error, dev sr0 messages suggest you may have a bad optical media drive. Failed attempts to read it could tie up system resources. 78 lines address /dev/sr0.
337 lines contain string krita. Have you been trying to use Krita to access files on a CD/DVD/Bluray?
253 mce events are reported, 94 containing string "above threshhold".
243 lines involve tracker, part of the file indexing system for fast local searches. 70 of those lines contain the string failed. If it gets I/O bound it might cause freezing.
597 lines are about plasma-discover, 10% of which contain string "took really long", and most of which contain string "could not find".
162 lines involve PackageKit doing upgrades.
You report having Cinnamon, but this dmesg has a log of Gnome and KDE things showing up in it. Some of these things involve each other, so could be getting tangled by interdependence.
If this was mine, the first thing I would do is disconnect the OM drive, which may be defective. If that didn't help, I'd uninstall PackageKit, to stop the automatic background update processes. I do my own checking for updates when I find appropriate times and am not otherwise busy.
^ TBF, NetworkManager is extremely chatty, it's not necessarily taxing the system too much.
But overall, from mrmazda's summary, I get the impression that you're running a full-blown Plasma desktop on hardware that struggles to keep up.
I'd start by disabling tracker. If you're lucky that is also its systemd service name:
Code:
systemctl stop tracker
If that helps:
Code:
systemctl disable tracker
Just a wild guess, make sure you have the right service.
To explain, file indexing is very expensive. It doesn't tax the CPU so much, but I/O instead.
Plasma-discover is your software manager, it, too appears to be too busy. Consider using a lighter software manager or switch to manual updates completely.
Long-term, a lighter DE might be more suitable for your hardware.
Failed to stop tracker.service: Unit tracker.service not loaded.
When I try to disable it i get this:
Failed to disable unit: Unit file tracker.service does not exist.
During the installation I chose the KDE plasma as my desktop and after this installation I installed the cinnamon which is the desktop that I am always using, but the KDE plasma is still there to be used. Do you think cinnamon may be the culprit? Should I use another desktop?
7029 of 11988 lines (58.6%) in that dmesg are about NetworkManager and 'set hostname', with 7918 total NetworkManager lines, making NetworkManager suspect of excess demands on system resources.
Do you know why acpi=force is included on the linu line in Grub? If you don't, try booting without it to see if it helps.
Do you know why you're running on the preempt kernel instead of the default? If not, try kernel-default.
blk_update_request: I/O error, dev sr0 messages suggest you may have a bad optical media drive. Failed attempts to read it could tie up system resources. 78 lines address /dev/sr0.
337 lines contain string krita. Have you been trying to use Krita to access files on a CD/DVD/Bluray?
253 mce events are reported, 94 containing string "above threshhold".
243 lines involve tracker, part of the file indexing system for fast local searches. 70 of those lines contain the string failed. If it gets I/O bound it might cause freezing.
597 lines are about plasma-discover, 10% of which contain string "took really long", and most of which contain string "could not find".
162 lines involve PackageKit doing upgrades.
You report having Cinnamon, but this dmesg has a log of Gnome and KDE things showing up in it. Some of these things involve each other, so could be getting tangled by interdependence.
If this was mine, the first thing I would do is disconnect the OM drive, which may be defective. If that didn't help, I'd uninstall PackageKit, to stop the automatic background update processes. I do my own checking for updates when I find appropriate times and am not otherwise busy.
What exactly is OM drive? Is it risky to uninstall PackageKit?
What exactly is OM drive? Is it risky to uninstall PackageKit?
Optical Media drive: CD, DVD, Bluray.
I run openSUSE 24/7, plus I have many installations on various extra PCs mainly used for QA and support work, including Debian, Fedora, Mageia & others. On none of them do I have PackageKit installed. openSUSE has Zypper and YaST for package management. It doesn't need PackageKit.
I run openSUSE 24/7, plus I have many installations on various extra PCs mainly used for QA and support work, including Debian, Fedora, Mageia & others. On none of them do I have PackageKit installed. openSUSE has Zypper and YaST for package management. It doesn't need PackageKit.
How do I disconnect OM drive and how do I uninstall PackageKit?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
