Oh wow. there is a bug in journalctl. it used to be able to do that just a few days ago… 
So do it manually: redirect to a text file and cut the superfluous information.
How about:
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)
OK, I can’t help you any further then… My apologies, solution removed to attract other experts.
Meeeen!! this random freezes are killing me!! Totally killing! Anyone, kindly assist. About to give up on the whole Manjaro Journey.
@Fabby is there anyone from the Manjaro team that you can direct them this way concerning my issue? Have just experienced 2 consecutive freezes and its really killing my productivity and work flow!
Please read this:
But read the last section first and If you’re still interested, read the other sections as well.
@Fabby was going through some logs of journalctl and come across this few lines:
[kevinm@datanav ~]$ journalctl --system --boot=-1
-- Journal begins at Sat 2021-05-29 13:34:14 EAT, ends at Sat 2021-05-29 18:07:22 EAT. --
May 29 17:01:06 datanav kernel: Linux version 5.12.2-1-MANJARO (builduser@LEGION) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.36.1) >
May 29 17:01:06 datanav kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.12-x86_64 root=UUID=a0c5af53-286a-45ad-8051-6f58a977fb4c r>
May 29 17:01:06 datanav kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
May 29 17:01:06 datanav kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
May 29 17:01:06 datanav kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
May 29 17:01:06 datanav kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
May 29 17:01:06 datanav kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
May 29 17:01:06 datanav kernel: BIOS-provided physical RAM map:
May 29 17:01:06 datanav kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
May 29 17:01:06 datanav kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
May 29 17:01:06 datanav kernel: BIOS-e820: [mem 0x0000000000059000-0x0000000000097fff] usable
May 29 17:01:06 datanav kernel: BIOS-e820: [mem 0x0000000000098000-0x000000000009ffff] reserved
May 29 17:01:06 datanav kernel: BIOS-e820: [mem 0x0000000000100000-0x000000008ab7efff] usable
May 29 17:01:06 datanav kernel: BIOS-e820: [mem 0x000000008ab7f000-0x000000008b27efff] type 20
May 29 17:01:06 datanav kernel: BIOS-e820: [mem 0x000000008b27f000-0x000000008be7efff] reserved
May 29 17:01:06 datanav kernel: BIOS-e820: [mem 0x000000008be7f000-0x000000008bf7efff] ACPI NVS
May 29 17:01:06 datanav kernel: BIOS-e820: [mem 0x000000008bf7f000-0x000000008bffefff] ACPI data
May 29 17:01:06 datanav kernel: BIOS-e820: [mem 0x000000008bfff000-0x000000008bffffff] usable
May 29 17:01:06 datanav kernel: BIOS-e820: [mem 0x00000000e00f8000-0x00000000e00f8fff] reserved
May 29 17:01:06 datanav kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
May 29 17:01:06 datanav kernel: BIOS-e820: [mem 0x00000000ff650000-0x00000000ff66efff] reserved
May 29 17:01:06 datanav kernel: BIOS-e820: [mem 0x0000000100000000-0x000000044fdfffff] usable
May 29 17:01:06 datanav kernel: DMAR: DRHD base: 0x000000fed91000 flags: 0x1
May 29 17:01:06 datanav kernel: DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c20660462 ecap f010da
May 29 17:01:06 datanav kernel: DMAR: RMRR base: 0x0000008be1f000 end: 0x0000008be3efff
May 29 17:01:06 datanav kernel: DMAR: RMRR base: 0x0000008e000000 end: 0x000000ae1fffff
May 29 17:01:06 datanav kernel: DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000008e000000-0x0000000>
May 29 17:01:06 datanav kernel: APIC: Switch to symmetric I/O mode setup
May 29 17:01:06 datanav kernel: DMAR: Host address width 39
May 29 17:01:06 datanav kernel: DMAR: DRHD base: 0x000000fed90000 flags: 0x0
May 29 17:01:06 datanav kernel: DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap c0000020660462 ecap f0101a
May 29 17:01:06 datanav kernel: DMAR: DRHD base: 0x000000fed91000 flags: 0x1
May 29 17:01:06 datanav kernel: DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c20660462 ecap f010da
May 29 17:01:06 datanav kernel: DMAR: RMRR base: 0x0000008be1f000 end: 0x0000008be3efff
May 29 17:01:06 datanav kernel: DMAR: RMRR base: 0x0000008e000000 end: 0x000000ae1fffff
May 29 17:01:06 datanav kernel: DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000008e000000-0x0000000>
May 29 17:01:06 datanav kernel: DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR [0x000000008e000000-0x00000000ae1fffff]
BIOS vendor: Hewlett-Packard; Ver: M85 Ver. 01.50; Product Version: A3009DD10303
May 29 17:01:06 datanav kernel: DMAR-IR: IOAPIC id 0 under DRHD base 0xfed91000 IOMMU 1
May 29 17:01:06 datanav kernel: DMAR-IR: HPET id 0 under DRHD base 0xfed91000
May 29 17:01:06 datanav kernel: DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit.
May 29 17:01:06 datanav kernel: DMAR-IR: Use 'intremap=no_x2apic_optout' to override the BIOS setting.
May 29 17:01:06 datanav kernel: DMAR-IR: Enabled IRQ remapping in xapic mode
May 29 17:01:06 datanav kernel: x2apic: IRQ remapping doesn't support X2APIC mode
ay 29 17:01:06 datanav kernel: rcu: Hierarchical SRCU implementation.
May 29 17:01:06 datanav kernel: NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
May 29 17:01:06 datanav kernel: smp: Bringing up secondary CPUs ...
May 29 17:01:06 datanav kernel: x86: Booting SMP configuration:
May 29 17:01:06 datanav kernel: .... node #0, CPUs: #1
May 29 17:01:06 datanav kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admi>
May 29 17:01:06 datanav kernel: #2 #3
May 29 17:01:06 datanav kernel: smp: Brought up 1 node, 4 CPUs
May 29 17:01:06 datanav kernel: smpboot: Max logical packages: 2
May 29 17:01:06 datanav kernel: smpboot: Total of 4 processors activated (21558.75 BogoMIPS)
May 29 17:01:06 datanav kernel: devtmpfs: initialized
May 29 17:01:06 datanav kernel: x86/mm: Memory block size: 128MB
May 29 17:01:06 datanav kernel: PM: Registering ACPI NVS region [mem 0x8be7f000-0x8bf7efff] (1048576 bytes)
May 29 17:01:06 datanav kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370867519511994 ns
May 29 17:01:06 datanav kernel: futex hash table entries: 2048 (order: 5, 131072 bytes, linear) ```
See the CPU and data leakage errors?Upgrade your UEFI firmware…
Problem is…There is no firmware to update!
@Fabby i just had another freeze, see below output of journalctl --system --boot=-1
I pressed the power key to reboot the laptop at 14:28:35
May 30 13:46:19 datanav audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 30 13:46:29 datanav systemd[1]: NetworkManager-dispatcher.service: Succeeded.
May 30 13:46:29 datanav audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 30 13:46:29 datanav kernel: audit: type=1131 audit(1622371589.175:105): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 30 13:47:23 datanav dbus-daemon[347]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.32' (uid=1000 pid=1282 comm="/usr/lib/org_kde_powerdevil ") (using servicehelper)
May 30 13:47:23 datanav dbus-daemon[347]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
May 30 13:55:32 datanav dbus-daemon[347]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.32' (uid=1000 pid=1282 comm="/usr/lib/org_kde_powerdevil ") (using servicehelper)
May 30 13:55:32 datanav dbus-daemon[347]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
May 30 14:01:01 datanav CROND[4370]: (root) CMD (run-parts /etc/cron.hourly)
May 30 14:01:01 datanav CROND[4369]: (root) CMDEND (run-parts /etc/cron.hourly)
May 30 14:06:26 datanav dbus-daemon[347]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.32' (uid=1000 pid=1282 comm="/usr/lib/org_kde_powerdevil ") (using servicehelper)
May 30 14:06:26 datanav dbus-daemon[347]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
May 30 14:28:35 datanav systemd-logind[358]: Power key pressed.Could my problem be attributed to the power devil thing?
-
Doesn’t provide any meaningful info info.
Please provide a journalctl --priority=3 --boot=-1 | tail --lines=50 -
Probably not…
Output of journalctl --priority=3 --boot=-1 | tail --lines=50
May 30 14:29:18 datanav kernel: DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000008e000000-0x00000000ae1fffff], contact BIOS vendor for fixes
May 30 14:29:19 datanav kernel: Bluetooth: hci0: unexpected event for opcode 0xfc2f
Also had another Freeze yesterday
See below output of journalctl --system --boot=-1
May 30 14:44:36 datanav kernel: audit: type=1131 audit(1622375076.268:96): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 30 15:01:02 datanav CROND[3311]: (root) CMD (run-parts /etc/cron.hourly)
May 30 15:01:02 datanav CROND[3310]: (root) CMDEND (run-parts /etc/cron.hourly)
May 30 15:03:59 datanav dbus-daemon[300]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.31' (uid=1000 pid=986 comm="/usr/lib/org_kde_powerdevil ") (using servicehelper)
May 30 15:03:59 datanav dbus-daemon[300]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
May 30 15:10:11 datanav dbus-daemon[300]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.31' (uid=1000 pid=986 comm="/usr/lib/org_kde_powerdevil ") (using servicehelper)
May 30 15:10:11 datanav dbus-daemon[300]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
May 30 15:11:26 datanav dbus-daemon[300]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.31' (uid=1000 pid=986 comm="/usr/lib/org_kde_powerdevil ") (using servicehelper)
May 30 15:11:26 datanav dbus-daemon[300]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
May 30 15:12:38 datanav dbus-daemon[300]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.31' (uid=1000 pid=986 comm="/usr/lib/org_kde_powerdevil ") (using servicehelper)
May 30 15:12:38 datanav dbus-daemon[300]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
May 30 15:12:43 datanav audit[3680]: USER_AUTH pid=3680 uid=1000 auid=1000 ses=2 subj==unconfined msg='op=PAM:unix_chkpwd acct="kevinm" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
May 30 15:12:43 datanav kernel: audit: type=1100 audit(1622376763.281:97): pid=3680 uid=1000 auid=1000 ses=2 subj==unconfined msg='op=PAM:unix_chkpwd acct="kevinm" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
May 30 15:14:24 datanav systemd-logind[314]: Power key pressed.
May 30 15:14:26 datanav systemd-logind[314]: Power key pressed.
May 30 15:14:27 datanav systemd-logind[314]: Power key pressed.
May 30 15:14:30 datanav systemd-logind[314]: Power key pressed.
May 30 15:14:30 datanav systemd-logind[314]: Power key pressed.
Again it happened just as when the backlight devil was being activated… 
I don’t know what the backlight devil is, so I can’t help you there…
And you were my only hope… 
I don't know what the backlight devil is, so I can't help you there...
It is a KDE service for adjusting the monitor backlight on laptops. (just learnt of this)
Yeah, but there is no coredump going on, so like I said:
I’m no subject matter expert, but from the symptoms above, it sounds like you need to pass an acpi parameter to your kernel.
See below:
Hope that helps!
Thanks for info, just followed the tutorial and added the command. Shall monitor and provide feedback. Had initially done the acpi_osi=Windows 2020 and my mouse frooze but adding the line acpi_osi=! i regained mouse control. All is left is to monitor the solution and see if it works.
Also just to add, i add deleted some services related to backlight inside of the systemd options, this solutions seemed to work for a while but then again the backlight helper showed itself up out of nowhere.
Will keep you posted.
Ok, sounds good.
If the acpi kernel parameters don’t help, it may be one of your devices is malfunctioning and causing the freeze-ups. You’ll have to dig further into the journal/kernel ring buffer in that case.
Don’t forget to mark this as solved if the above does the trick. 
