Okay, looking at those logs (7 Nov specifically), I don't see some flags. Most of those warnings, aren't worth worrying about. For example, BT gives complaints about 9/10 times in linux (from my experience), but they still work. Theme errors are nothing to worry about, you get them all the time and I vaguely could guess the base dirs are wrong, but my philosophy is "If it ain't broke, don't look into it or your OCD will make you want to fix it". So long as nothing looks broken, lol.
Observations:
0. You should have mentioned you were using anbox and running Android under Hypervisor...
(This is not my area of expertise, so I'm just working with my limited knowledge and what I see in the logs)
1. The module, ashmem_linux is being used instead of an in-kernel version or stable version. I've seen this type of error with other modules, never on my own PC though, so I's not too familiar with this, however it may be worth some ducking.
2. I see Hypervisor warnings and anyone seeing this already knows intel are at it again. Anyway, you may have to randomly screw with some BIOS settings like IOMMU et al. since we're now dealing in virtualisation (I mean physical, hypervisor-style).
3. ACPI errors... Usually those are... Yes. I see those and my thoughts are: Most likely candidate given the above points.
Conclusions:
I guess after some initial exploratory thoughts (which I'm leaving in case anyone here has some useful input regarding them), I have to say that we have a few likely culprits:
- ACPI: This has caused me freezes on a laptop in the past. Try just disabling all power management features and, only if needed, enable them 1 by 1.
- Hyper-V: Okay, so we may have this big issue of security here. Access violations perhaps since you appear to be trying to run an x86 Android on bear metal virtualisation. Intel is notorious for security features that break things. I suggest you try to reproduce the freezes specific to this activity, and when you are reasonably sure it relates, try post a help question on Anbox's forums, Reddit, etc. and while you wait, do some searching on Arch forums or Arch Wiki coz a lot of that info is agnostic or can easily be translated to other distros provided you have a reasonable knowledge of Arch Linux, general Linux, or both. Another consideration on this note is that Hyper-V may be blocking some essential memory ops.
One thing you can do is update the iucode-tools package to the latest (and/or general firmware packages) as this provides micocode updates which may have broken and now may fix Hyper-V and ACPI errors
Other things to do: Maybe try running what you are now on a pure Debian (Ubuntu != Debian) stable and see what happens. Also try Manjaro (not Arch, Manjaro != Arch) since it'll just be a test and you want pure OOTB. You may find it's a bug in the *buntu family. Of course if it is across the board, you might want to look at your hardware more closely and how it's being configured or how you're configuring it.
Hope this turns out to be of use at least narrowing the problem down.
Observations:
0. You should have mentioned you were using anbox and running Android under Hypervisor...
(This is not my area of expertise, so I'm just working with my limited knowledge and what I see in the logs)
1. The module, ashmem_linux is being used instead of an in-kernel version or stable version. I've seen this type of error with other modules, never on my own PC though, so I's not too familiar with this, however it may be worth some ducking.
2. I see Hypervisor warnings and anyone seeing this already knows intel are at it again. Anyway, you may have to randomly screw with some BIOS settings like IOMMU et al. since we're now dealing in virtualisation (I mean physical, hypervisor-style).
3. ACPI errors... Usually those are... Yes. I see those and my thoughts are: Most likely candidate given the above points.
Conclusions:
I guess after some initial exploratory thoughts (which I'm leaving in case anyone here has some useful input regarding them), I have to say that we have a few likely culprits:
- ACPI: This has caused me freezes on a laptop in the past. Try just disabling all power management features and, only if needed, enable them 1 by 1.
- Hyper-V: Okay, so we may have this big issue of security here. Access violations perhaps since you appear to be trying to run an x86 Android on bear metal virtualisation. Intel is notorious for security features that break things. I suggest you try to reproduce the freezes specific to this activity, and when you are reasonably sure it relates, try post a help question on Anbox's forums, Reddit, etc. and while you wait, do some searching on Arch forums or Arch Wiki coz a lot of that info is agnostic or can easily be translated to other distros provided you have a reasonable knowledge of Arch Linux, general Linux, or both. Another consideration on this note is that Hyper-V may be blocking some essential memory ops.
One thing you can do is update the iucode-tools package to the latest (and/or general firmware packages) as this provides micocode updates which may have broken and now may fix Hyper-V and ACPI errors
Other things to do: Maybe try running what you are now on a pure Debian (Ubuntu != Debian) stable and see what happens. Also try Manjaro (not Arch, Manjaro != Arch) since it'll just be a test and you want pure OOTB. You may find it's a bug in the *buntu family. Of course if it is across the board, you might want to look at your hardware more closely and how it's being configured or how you're configuring it.
Hope this turns out to be of use at least narrowing the problem down.
