Manjaro randomly freezing

Lately, my desktop has been freezing randomly and I'm not sure what is causing it. I must be using a UEFI boot because memtest+ isn't in my grub menu. I have no problems from $systemctl --failed, but I get the following output from journalctl:


$ journalctl -p 3 -xb
-- Logs begin at Wed 2019-02-13 10:57:48 EST, end at Tue 2019-09-10 17:29:15 EDT. --
Sep 10 17:27:13 username-pc kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Sep 10 17:27:13 username-pc kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-514)
Sep 10 17:27:13 username-pc kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Sep 10 17:27:13 username-pc kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-514)
Sep 10 17:27:13 username-pc systemd-udevd[374]: Specified group 'plugdev' unknown
Sep 10 17:27:14 username-pc nmbd[626]: [2019/09/10 17:27:14.446504,  0] ../../lib/util/become_daemon.c:147(daemon_status)
Sep 10 17:27:14 username-pc nmbd[626]:   daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
Sep 10 17:27:14 username-pc nmbd[626]: [2019/09/10 17:27:14.446826,  0] ../../source3/nmbd/nmbd_subnetdb.c:253(create_subnets)
Sep 10 17:27:14 username-pc nmbd[626]:   NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
Sep 10 17:27:40 username-pc NetworkManager[613]: <error> [1568150860.3483] sup-iface[0x562e7fe0e920,wlp10s0]: error adding interface: Timeout was reached
Sep 10 17:28:35 username-pc kwin_x11[842]: kwin_core: Compositing is not possible
Sep 10 17:28:39 username-pc nmbd[626]: [2019/09/10 17:28:39.451982,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
Sep 10 17:28:39 username-pc nmbd[626]:   daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
Sep 10 17:28:39 username-pc smbd[1008]: [2019/09/10 17:28:39.554247,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
Sep 10 17:28:39 username-pc smbd[1008]:   daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
Sep 10 17:28:39 username-pc nmbd[626]: [2019/09/10 17:28:39.677945,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 10 17:28:39 username-pc nmbd[626]:   query_name_response: Multiple (2) responses received for a query on subnet MyIp for name WORKGROUP<1d>.
Sep 10 17:28:39 username-pc nmbd[626]:   This response was from IP MyIp reporting an IP address of MyIp.

Could one of these errors help in identifying the source of the freezes, or are there any errors I should be concerned about? I'm happy to provide additional output.

Update your BIOS.

Try a different kernel like 5.2 or an older like 4.9 or 4.14

1 Like

I just updated the BIOS and am getting the following errors:

 journalctl -p 3 -xb
-- Logs begin at Wed 2019-02-13 10:57:48 EST, end at Tue 2019-09-10 20:19:51 EDT. --
Sep 10 20:18:10 username-pc kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Sep 10 20:18:10 username-pc kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-514)
Sep 10 20:18:10 username-pc kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Sep 10 20:18:10 username-pc kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-514)
Sep 10 20:18:10 username-pc systemd-udevd[370]: Specified group 'plugdev' unknown
Sep 10 20:18:11 username-pc kernel: kvm: disabled by bios
Sep 10 20:18:11 username-pc kernel: kvm: disabled by bios
Sep 10 20:18:11 username-pc kernel: kvm: disabled by bios
Sep 10 20:18:11 username-pc kernel: kvm: disabled by bios
Sep 10 20:18:11 username-pc kernel: kvm: disabled by bios
Sep 10 20:18:11 username-pc kernel: kvm: disabled by bios
Sep 10 20:18:11 username-pc kernel: kvm: disabled by bios
Sep 10 20:18:11 username-pc kernel: kvm: disabled by bios
Sep 10 20:18:12 username-pc nmbd[628]: [2019/09/10 20:18:12.284860,  0] ../../lib/util/become_daemon.c:147(daemon_status)
Sep 10 20:18:12 username-pc nmbd[628]:   daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
Sep 10 20:18:12 username-pc nmbd[628]: [2019/09/10 20:18:12.285303,  0] ../../source3/nmbd/nmbd_subnetdb.c:253(create_subnets)
Sep 10 20:18:12 username-pc nmbd[628]:   NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
Sep 10 20:18:25 username-pc kwin_x11[834]: kwin_core: Compositing is not possible
Sep 10 20:18:32 username-pc nmbd[628]: [2019/09/10 20:18:32.286225,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
Sep 10 20:18:32 username-pc nmbd[628]:   daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
Sep 10 20:18:32 username-pc smbd[1008]: [2019/09/10 20:18:32.379782,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
Sep 10 20:18:32 username-pc smbd[1008]:   daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
Sep 10 20:18:32 username-pc nmbd[628]: [2019/09/10 20:18:32.465518,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 10 20:18:32 username-pc nmbd[628]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.50.67 for name WORKGROUP<1d>.
Sep 10 20:18:32 username-pc nmbd[628]:   This response was from IP ~~my_ip~~, reporting an IP address of ~~my_ip~~.

I'll report back if I continue to get freezes.

1 Like

These are BIOS bugs the mobo maker hasn't bothered to fix and it's unlikely they ever will.
Nothing you can do about it as far as I know.
Though something is going on with the ACPI. Might want to search the forum for that reference.

Sep 10 20:18:10 username-pc kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Sep 10 20:18:10 username-pc kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-514)
Sep 10 20:18:10 username-pc kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Sep 10 20:18:10 username-pc kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-514)

This is just letting you know that Virtualization is turned off in BIOS. So VirtualBox and other VM software won't run at it's optimal performance.
Easily fixed by going into the BIOS and enabling it if you need it. Not an error. :wink:

Sep 10 20:18:11 username-pc kernel: kvm: disabled by bios
Sep 10 20:18:11 username-pc kernel: kvm: disabled by bios
Sep 10 20:18:11 username-pc kernel: kvm: disabled by bios
Sep 10 20:18:11 username-pc kernel: kvm: disabled by bios
Sep 10 20:18:11 username-pc kernel: kvm: disabled by bios
Sep 10 20:18:11 username-pc kernel: kvm: disabled by bios
Sep 10 20:18:11 username-pc kernel: kvm: disabled by bios

Apparently you don't have a plugdev group according to this message.

Sep 10 20:18:10 username-pc systemd-udevd[370]: Specified group 'plugdev' unknown

I have no idea if that's important or not. i thought it was part of the udev thing and needed but someone with more knowledge will have to chime in.

These are just system ready services. No error as far as I can tell.

Sep 10 20:18:12 username-pc nmbd[628]: [2019/09/10 20:18:12.284860,  0] ../../lib/util/become_daemon.c:147(daemon_status)
Sep 10 20:18:12 username-pc nmbd[628]:   daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
Sep 10 20:18:12 username-pc nmbd[628]: [2019/09/10 20:18:12.285303,  0] ../../source3/nmbd/nmbd_subnetdb.c:253(create_subnets)
Sep 10 20:18:12 username-pc nmbd[628]:   NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
Sep 10 20:18:25 username-pc kwin_x11[834]: kwin_core: Compositing is not possible
Sep 10 20:18:32 username-pc nmbd[628]: [2019/09/10 20:18:32.286225,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
Sep 10 20:18:32 username-pc nmbd[628]:   daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
Sep 10 20:18:32 username-pc smbd[1008]: [2019/09/10 20:18:32.379782,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
Sep 10 20:18:32 username-pc smbd[1008]:   daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
Sep 10 20:18:32 username-pc nmbd[628]: [2019/09/10 20:18:32.465518,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 10 20:18:32 username-pc nmbd[628]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.50.67 for name WORKGROUP<1d>.
Sep 10 20:18:32 username-pc nmbd[628]:   This response was from IP ~~my_ip~~, reporting an IP address of ~~my_ip~~.

...well, one thing would be nmbd/smbd ... both of which changed to smb and nmb
[no more 'd']
How you are noticing it just now (a year after the change) .. I do not know.

Also this is somewhat concerning, unless it is only due to timing
(as in its too early to work ... do you have compositing while using the desktop?)

(oops, sorry sinister, I meant to reply to OP)

1 Like

That means you did not update the system in quite some time. 4.19.69 is the latest in the stable branch.

Any particular reason why using the legacy drivers ?

1 Like

You are linking to your inxi output which is from 2017! It suggests that you are still running kernel 4.19.24. Is that true? Please confirm that your system is up to date. This is also true for your nvidia driver.

Update:
Just saw that @bogdancovaciu made the same point.

3 Likes

@mbod @bogdancovaciu

My apologies, everyone!!! I should have posted an updated inxi output - that's my fault and I have now updated it

I am running the latest LTS Recommended kernel and I believe my GPU drivers are up to date:

Kernel: 4.19.69-1-MANJARO x86_64
NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: Gigabyte driver: nvidia v: 390.129

@cscs
I don't think I am using compositing? I'm just using the KDE environment, nothing fancy. Pardon my ignorance.
Edit: I'm dumb - yes, I am using compositing

You are. it's how you get many of the effects with the windows. Transparency, etc....

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by