Hi there, have a fresh installation of manjaro KDE and have experienced random freezes where the system is completely unresponsive and am forced to reboot.I run windows on the same disk and it does not experience any issue.
System info:
Operating System: Manjaro Linux
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2
Kernel Version: 5.10.34-1-MANJARO
OS Type: 64-bit
Graphics Platform: X11
Processors: 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz
Memory: 15.1 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4400
Journal:
-- Journal begins at Sun 2021-05-09 20:52:22 EAT, ends at Sun 2021-05-09 23:52:21 EAT. --
May 09 21:00:49 datanav kernel: MDS CPU bug present and SMT on, data leak possible.
May 09 21:00:49 datanav kernel: #2 #3
May 09 21:00:49 datanav kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
May 09 21:00:49 datanav kernel: mtrr: your CPUs had inconsistent variable MTRR settings
May 09 21:00:49 datanav kernel: ata2.00: supports DRM functions and may not be fully accessible
May 09 21:00:49 datanav kernel: ata2.00: NCQ Send/Recv Log not supported
May 09 21:00:49 datanav kernel: ata2.00: supports DRM functions and may not be fully accessible
May 09 21:00:49 datanav kernel: ata2.00: NCQ Send/Recv Log not supported
May 09 21:00:49 datanav kernel: usb: port power management may be unreliable
May 09 21:00:50 datanav systemd[1]: logrotate.timer: Not using persistent file timestamp Sun 2021-05-09 23:22:09 EAT as it is in th>
May 09 21:00:50 datanav systemd[1]: man-db.timer: Not using persistent file timestamp Sun 2021-05-09 23:22:09 EAT as it is in the f>
May 09 21:00:50 datanav systemd[1]: pamac-cleancache.timer: Not using persistent file timestamp Sun 2021-05-09 23:22:09 EAT as it i>
May 09 21:00:50 datanav systemd[1]: pamac-mirrorlist.timer: Not using persistent file timestamp Sun 2021-05-09 23:22:09 EAT as it i>
May 09 21:00:50 datanav systemd[1]: pkgfile-update.timer: Not using persistent file timestamp Sun 2021-05-09 23:22:09 EAT as it is >
May 09 21:00:50 datanav systemd[1]: shadow.timer: Not using persistent file timestamp Sun 2021-05-09 23:22:09 EAT as it is in the f>
May 09 21:00:50 datanav kernel: resource sanity check: requesting [mem 0xfed10000-0xfed15fff], which spans more than Reserved [mem >
May 09 21:00:50 datanav kernel: caller snb_uncore_imc_init_box+0x82/0xd0 [intel_uncore] mapping multiple BARs
May 09 21:00:51 datanav kernel: at24 0-0050: supply vcc not found, using dummy regulator
May 09 21:00:52 datanav kernel: Bluetooth: hci0: unexpected event for opcode 0xfc2f
May 09 21:00:52 datanav NetworkManager[300]: <warn> [1620583252.5167] sup-iface[7354b6d667cba506,0,wlo1]: call-p2p-cancel: failed >
May 09 21:00:53 datanav systemd-xdg-autostart-generator[793]: Configuration file /etc/xdg/autostart/msm_kde_notifier.desktop is mar>
May 09 21:00:54 datanav systemd[787]: -.slice: Failed to migrate controller cgroups from /user.slice/user-965.slice/user@965.servic>
May 09 21:00:54 datanav sddm-greeter[797]: QFont::fromString: Invalid description '(empty)'
May 09 21:00:54 datanav sddm-greeter[797]: QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x7fff8d61a450), parent's thread is QThread(0x55b030ba0dd0), >
May 09 21:00:54 datanav sddm-greeter[797]: QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x7fff8d61a450), parent's thread is QThread(0x55b030ba0dd0), >
May 09 21:00:54 datanav sddm-greeter[797]: QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x7fff8d61a450), parent's thread is QThread(0x55b030ba0dd0), >
lines 1-30
In the future, when providing code/output, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text so that the output looks like this:
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
instead of like this:
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.`
(as that makes both our lives much easier)
No need to do anything right now as I’m an editor here on this site and have fixed it for you already. However, in the future I might not see your post so review my edits by pushing the orange pencil above the post I just fixed.
As you’re on kernel 5.10 and have an AMDintegrated graphics card, have you tried 5.4 LTS already? (and 5.12 would be my next choice)
If upgrading the kernel to 5.12 wouldn’t help neither, please try to create a new user and log in there and see if you have the issue there as well. (E.G. couch2)
Created a new user and haven’t experienced any freeze so far. Is there any reason as to why the freeze is happening on the original account and not on the second one?
If that worked and you had no errors, remove the documents from your old user:
rm --recursive /home/couch/Documents/*
repeat for:
Pictures
Videos
Music
.thunderbird
.mozilla/firefox/
Templates, and everything else that is important to you.
Linux games like Battle of Wesnoth have their game data stored under ~/.local/share/ E.G. ~/.local/share/wesnoth/
After everything has been copied over, disable the old user so you cannot accidentally log on:
usermod --lock couch
If you would have theming going on, don’t do everything in one day but do this at the rate of 1 application / theme / whatever per day and if the same issue crops up again, roll back your last change
in 1 month delete the entire home directory of your old user, but don’t delete the user itself so that in 6 months time files still owned by that user will still show up under its username.
If you ever migrate to a new machine, just don’t migrate the old user: only the new one.
From now on, start making backups so you can roll back and never have to do this again:
Fabby, the funny thing is that this was a new installation. Practically new, nothing saved in all those directories and no special programs installed, so migrating to this new account will be easy. Below is the outcome of groups command
wheel lp sys network power kevin
[mbugua@Datanav ~]$ groups mbugua
audio lp optical video sys network scanner power mbugua
[mbugua@Datanav ~]$
kevin is the old user and it seems he had far much less rights than the new account. Tried issuing the wheel rights to the new account but was met with an access denied error or do i need to switch to the old account and issue the rights from there?
I can humbly confirm that the system is fine now with no freezes at all! Creating a new user and upgrading the kernel to version 5.12.1-2 solved the issue. Thank you fabby!
Well it froze again, completely unusable until a hard reboot had to be done.
The freeze started by inter changing the mouse button functions, then went completely ice, even the backlight keyboard lights would not go off. They stayed on until the reboot. Then even after rebooting the same thing happened all over again!
Its was the internal touchpad and not an external mouse. And nop i dont have any new Bios update for my PC…also been trying to do a REISUB but nop it does not work either. If i hold ALT key and press the buttons, it just highlights the usual ALT shortcuts on the browser. Also noticed with the current form of freeze, i can restart the PC by pressing the power button and choosing “restart”. Apparently only the DE(plus the apps already opened) is freezing. And it has happened thrice in 5 minutes so far. Would it be due to the updates that were pushed early on this week?
Also i have no clue how to export the journal data to a text file(novice human being here)