[Solved] Very slow system

Akadius · 2022-09-25 10:48:40

I have done multiple updates since last week and firefox was one of them, I experienced slow downs using firefox, thunderbird, electron apps and games.

I didn't pay much attention since I though it was firefox having a bad update again and would be corrected swiftly, but since yesterday I tried to solve the issue.

Even closing almost all application I still experience those slow down. I don't have high cpu usage, plenty of ram available, and no IO issue.

I ran :

sudo hdparm -t /dev/nvme0n1

dev/nvme0n1:
 Timing buffered disk reads: 2922 MB in  3.00 seconds = 973.87 MB/sec

sudo iotop -Pod5

 12:26:58 Total DISK READ :       0.00 K/s | Total DISK WRITE :       0.00 K/s
12:26:58 Actual DISK READ:       0.00 K/s | Actual DISK WRITE:       0.00 K/s
    TIME    PID  PRIO  USER     DISK READ  DISK WRITE  SWAPIN      IO    COMMAND
12:27:03 Total DISK READ :      11.03 K/s | Total DISK WRITE :     139.41 K/s
12:27:03 Actual DISK READ:     200.06 K/s | Actual DISK WRITE:      81.91 K/s
12:27:03     375 be/3 root          0.00 K     96.00 K  ?unavailable?  [jbd2/nvme0n1p3-8]
12:27:03     414 be/4 root          0.00 K     72.00 K  ?unavailable?  systemd-journald
12:27:03    2204 ?dif akadius      56.00 K    536.00 K  ?unavailable?  firefox
12:27:03    3737 be/4 root          0.00 K      4.00 K  ?unavailable?  python /usr/bin/iotop -abtqkPod5
12:27:09 Total DISK READ :    1478.01 K/s | Total DISK WRITE :     770.32 K/s
12:27:09 Actual DISK READ:    1478.01 K/s | Actual DISK WRITE:     576.95 K/s
12:27:09     375 be/3 root          0.00 K    528.00 K  ?unavailable?  [jbd2/nvme0n1p3-8]
12:27:09     414 be/4 root          0.00 K    100.00 K  ?unavailable?  systemd-journald
12:27:09    1662 ?dif akadius     192.00 K     12.00 K  ?unavailable?  thunderbird
12:27:09    2204 ?dif akadius    7416.00 K   3996.00 K  ?unavailable?  firefox
12:27:09    3737 be/4 root          0.00 K      4.00 K  ?unavailable?  python /usr/bin/iotop -abtqkPod5

free -h

free -h
               total        used        free      shared  buff/cache   available
Mem:            30Gi       2.8Gi        25Gi        78Mi       2.4Gi        27Gi
Swap:          3.7Gi          0B       3.7Gi

uname -a

Linux localhost 5.19.10-arch1-1 #1 SMP PREEMPT_DYNAMIC Tue, 20 Sep 2022 15:17:59 +0000 x86_64 GNU/Linux

sudo dmesg
http://ix.io/4bmA

sudo dmesg -t --level=alert,crit,err,warn

  #9 #10 #11 #12 #13 #14 #15
ata5.00: supports DRM functions and may not be fully accessible
ata5.00: supports DRM functions and may not be fully accessible
amdgpu: unknown parameter 'ngg' ignored
amdgpu 0000:03:00.0: amdgpu: PSP runtime database doesn't exist
amdgpu 0000:03:00.0: amdgpu: PSP runtime database doesn't exist
amdgpu: SRAT table not found
amdgpu 0000:0d:00.0: amdgpu: PSP runtime database doesn't exist
amdgpu 0000:0d:00.0: amdgpu: PSP runtime database doesn't exist
amdgpu: SRAT table not found
nvme nvme0: missing or invalid SUBNQN field.
ashmem_linux: loading out-of-tree module taints kernel.
ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP0.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20220331/psargs-330)
ACPI Error: Aborting method \_SB.PCI0.GPP0.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20220331/psargs-330)
ACPI Error: Aborting method \_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
kauditd_printk_skb: 7 callbacks suppressed
platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
thermal thermal_zone0: failed to read out thermal zone (-61)
kauditd_printk_skb: 23 callbacks suppressed
kauditd_printk_skb: 2 callbacks suppressed
kauditd_printk_skb: 10 callbacks suppressed

journalctl -b
http://ix.io/4bmB

journalctl -p 3 -b

Sep 25 12:15:56 localhost systemd-modules-load[415]: Failed to find module 'binder_linux'
Sep 25 12:15:56 localhost systemd-modules-load[415]: Failed to find module 'v4l2loopback_dc'
Sep 25 12:15:58 localhost kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP0.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20220331/psargs-330)
Sep 25 12:15:58 localhost kernel: ACPI Error: Aborting method \_SB.PCI0.GPP0.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Sep 25 12:15:58 localhost kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20220331/psargs-330)
Sep 25 12:15:58 localhost kernel: ACPI Error: Aborting method \_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Sep 25 12:16:02 localhost systemd-udevd[442]: could not find module by name='xow_blacklist'
Sep 25 12:16:02 localhost bluetoothd[1010]: profiles/input/manager.c:load_config_file() Parsing /etc/bluetooth/input.conf failed: Key file does not start with a group
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x70004, and key code 30: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x70006, and key code 46: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x70007, and key code 32: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x70008, and key code 18: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x70009, and key code 20: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x70014, and key code 16: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x70015, and key code 19: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x70016, and key code 31: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x7001a, and key code 17: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x7001b, and key code 71: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x7001d, and key code 77: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x7001e, and key code 2: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x7001f, and key code 3: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x70020, and key code 4: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x70021, and key code 5: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x70022, and key code 6: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x7002b, and key code 34: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x7002c, and key code 57: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x70039, and key code 75: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x7004f, and key code 33: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x70050, and key code 100: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x70051, and key code 81: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x70052, and key code 80: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x700e1, and key code 72: Invalid argument
Sep 25 12:16:04 localhost systemd-udevd[454]: event29: Failed to call EVIOCSKEYCODE with scan code 0x700e2, and key code 42: Invalid argument

The nvme means that i only have one smart test available and it passes, with not much description, given that my access time and bandwith are pretty good on it, I didn't investigate it further.

I'm not sure what to search for anymore, the test are run right after boot, starting only firefox, thunderbird and console.

Last edited by Akadius (2022-09-26 16:49:49)

Lone_Wolf · 2022-09-25 12:01:54

Linux localhost 5.19.10-arch1-1 #1 SMP PREEMPT_DYNAMIC Tue, 20 Sep 2022 15:17:59 +0000 x86_64 GNU/Linux

Looks like your system doesn't have a hostname (or lost it). This is known to cause severe slowdowns in X/gui.

post the content of /etc/hostname contents and the output of hostnamectl .

Akadius · 2022-09-25 12:12:37

/etc/hostname

localhost

hostnamectl

Static hostname: localhost
Transient hostname: archlinux
         Icon name: computer
        Machine ID: 1740f9418e344680b07a82a531874dfb
           Boot ID: 8306d7b151204e0c9c3ca8bd519713b6
  Operating System: Arch Linux                      
            Kernel: Linux 5.19.10-arch1-1
      Architecture: x86-64
   Hardware Vendor: To Be Filled By O.E.M.
    Hardware Model: To Be Filled By O.E.M.
  Firmware Version: P4.80

I saw a thread on this and dismissed it without even looking, I didn't know it causes so much trouble.

Mine seems to still have a hostname though. Unless localhost is now a reserved name ?

Last edited by Akadius (2022-09-25 12:13:34)

zpg443 · 2022-09-25 12:31:02

Is the bios error new, or was it appearing before the slowdown?

Slithery · 2022-09-25 12:33:19

Akadius wrote:

Unless localhost is now a reserved name ?

localhost has always been a reserved name.

Akadius · 2022-09-25 12:35:03

zpg443 wrote:

Is the bios error new, or was it appearing before the slowdown?

module 'binder_linux', it is since I installed anbox I think, never really used it or got around to remove it.

module 'v4l2loopback_dc', this one I don't know.

The ACPI errors have been here for some time, and i asked before, it wasn't a big deal apparently.

xow_blacklist, I'm looking into this one because I have disabled xow while for now because it was throwing an error during boot, but unrelated to this problem.

For the bluetooth, I have seen it before but I'm not too sure, I'm looking into it right now.

Akadius · 2022-09-25 12:35:39

Slithery wrote:

Akadius wrote:
Unless localhost is now a reserved name ?
localhost has always been a reserved name.

So I should just change it in /etc/hostname and reboot ?

Edit:

I changed hostname, reboot, still the same slow downs.

Last edited by Akadius (2022-09-25 12:40:53)

seth · 2022-09-25 12:44:36

Doesn't matter, "localhost" isn't an acceptable hostname in any event.
Please elaborate on

I experienced slow downs using firefox, thunderbird, electron apps and games.

What kind of "slow downs"? How do they manifest? (Please don't say "these applications become slower")

Eg:
- input or output related?
- video stalls?
- network related?
- immediate or do they "slow down" over time?
- do you get a decent network throughput? https://bbs.archlinux.org/viewtopic.php … 6#p2017886
- other stuff…

Edit:
- wild guess: "glxinfo -B"

Last edited by seth (2022-09-25 12:48:06)

Akadius · 2022-09-25 12:56:30

seth wrote:

Doesn't matter, "localhost" isn't an acceptable hostname in any event.
Please elaborate on
I experienced slow downs using firefox, thunderbird, electron apps and games.
What kind of "slow downs"? How do they manifest? (Please don't say "these applications become slower")
Eg:
- input or output related?
- video stalls?
- network related?
- immediate or do they "slow down" over time?
- do you get a decent network throughput? https://bbs.archlinux.org/viewtopic.php … 6#p2017886
- other stuff…

The slow downs are immediately at boot. I have for example thunderbird and a terminal application that launch automatically from i3 config,
those are generally instant to load, now it takes 10 to 20 seconds to appear on the screen.

In thunderbird, switching between accounts or email, going through menus takes some time to load.
In firefox, switching tabs, even if the page is already loaded, going to a new website takes more time than usual.

In discord, the easiest way to see it, is to go hovering with mouse on the server icon, the name start lagging and it takes lots of time (5-10 seconds) to load just the name
from the hovering, the mouse doesn't lag though.

In games, it looks like the entire application is lagging.

In i3, starting a new application is slow but switching workspace works as usual, unless an application is launched.

I'm on a 300Mb fiber and it works well enough, no slow down that I can see.

1. Newark, USA
 2. Singapore
 3. London, UK
 4. Frankfurt, Deutschland
 5. Dallas, USA
 6. Toronto, Canada
 7. Sidney, Australia
 8. Atlanta, USA
 9. 東京都 (Tokyo), 日本国 (Japan)
10. मुंबई (Bombay), Bhārat (India)
11. Fremont, USA
Enter location: 3
 1. 100MB
 2. 1GB
Slect size: 2
/dev/null                                       100%[======================================================================================================>]   1000M  35.2MB/s    in 28s     
2022-09-25 14:55:04 URL:http://speedtest.london.linode.com/1GB-london.bin [1048576000/1048576000] -> "/dev/null" [1]

seth · 2022-09-25 13:04:22

now it takes 10 to 20 seconds to appear on the screen.

How do you start the session? startx/xinit?
In case, see the last link below and post your xinitrc (though the dbus timeout is 25s)

Also "glxinfo -B"

Akadius · 2022-09-25 13:10:40

seth wrote:

now it takes 10 to 20 seconds to appear on the screen.
How do you start the session? startx/xinit?
In case, see the last link below and post your xinitrc (though the dbus timeout is 25s)
Also "glxinfo -B"

I use lightDM.

glxinfo -B

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: AMD (0x1002)
    Device: AMD Radeon RX 5700 XT (navi10, LLVM 14.0.6, DRM 3.47, 5.19.10-arch1-1) (0x731f)
    Version: 22.1.7
    Accelerated: yes
    Video memory: 8192MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 6540 MB, largest block: 6540 MB
    VBO free aux. memory - total: 15679 MB, largest block: 15679 MB
    Texture free memory - total: 6540 MB, largest block: 6540 MB
    Texture free aux. memory - total: 15679 MB, largest block: 15679 MB
    Renderbuffer free memory - total: 6540 MB, largest block: 6540 MB
    Renderbuffer free aux. memory - total: 15679 MB, largest block: 15679 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 8192 MB
    Total available memory: 23925 MB
    Currently available dedicated video memory: 6540 MB
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 5700 XT (navi10, LLVM 14.0.6, DRM 3.47, 5.19.10-arch1-1)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.1.7
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.1.7
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.1.7
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

I have an apu that I use as well, for one monitor.

This as been configured for month and no issue so far, I don't any slowdown when the screen initialize.

I use xorg.conf and xrandr to set them up.

Last edited by Akadius (2022-09-25 13:13:05)

seth · 2022-09-25 13:26:43

Sep 25 12:15:56 localhost systemd[1]: Queued start job for default target Graphical Interface.
…
Sep 25 12:16:12 localhost systemd[1]: Reached target Graphical Interface.

It takes 16 seconds to start the graphical target - something bad is going on here.
Get rid of all usb devices, the headset, the fancy gaming mouse and keyboard: everything you can spare or replace (eg. if you've got a cheap generic mouse/keyboard) and see what happens.

I have an apu that I use as well, for one monitor.

Please post your xorg log and obviously test w/o that as well…

Last edited by seth (2022-09-25 13:27:49)

Mr.Smith1974 · 2022-09-25 13:41:25

I have exactly the same problem. Recently (I can’t say exactly when), but the system began to slow down a lot, or I would even say “lag”. This is especially noticeable in Firefox.
I did not make any changes other than updating Archlinux.
It started this week or last week, and I didn't attach any importance to it either. I thought it was either because of a Firefox update or because of some add-on to it.

Please answer two questions:
1) What desktop environment are you using? I am using KDE.
2) What country are you from? This may be due to some kind of blocking of the network due to the aggression of my country against Ukraine.

seth · 2022-09-25 13:48:48

This may be due to some kind of blocking of the network

https://bbs.archlinux.org/viewtopic.php … 9#p2059109

His downstream from London seems fine, though.
If we go with your theory of whack-a-dick…tator, do you get the same effect w/ other systems, eg. a live distro like https://grml.org/ (maybe download an older version to get an older software stack)

Akadius · 2022-09-25 13:52:10

seth wrote:

Sep 25 12:15:56 localhost systemd[1]: Queued start job for default target Graphical Interface.
…
Sep 25 12:16:12 localhost systemd[1]: Reached target Graphical Interface.
It takes 16 seconds to start the graphical target - something bad is going on here.
Get rid of all usb devices, the headset, the fancy gaming mouse and keyboard: everything you can spare or replace (eg. if you've got a cheap generic mouse/keyboard) and see what happens.
I have an apu that I use as well, for one monitor.
Please post your xorg log and obviously test w/o that as well…

Unplugged all the usb beside a keyboard/mouse very generic nothing fancy.

journalctl -b
http://ix.io/4bnj

/var/log/Xorg.0.log
http://ix.io/4bni

I have just to test by deactivating my apu.
I'll edit that post as soon as it is done.

EDIT:

This make me very sad but deactivating my apu solved the slow down.

It was working fine until now. I'll do some testing to see if I can resolve the issue, but concerning archlinux, I think it's done.
Maybe it's the fact that I have to deactivate csm compatibility in order to activate Igpu in the bios.

Thanks alot for your help.

Just for info, journalctl, xorg and dmesg after deactivating the apu

journalctl -b
http://ix.io/4bnn

/var/log/Xorg.0.log
http://ix.io/4bno

sudo dmesg
http://ix.io/4bnp

Last edited by Akadius (2022-09-25 14:00:04)

seth · 2022-09-25 14:20:02

Yup.

[    33.498] randr: falling back to unsynchronized pixmap sharing
[   225.025] (EE) event23 - 2.4G Mouse: client bug: event processing lagging behind by 25ms, your system is too slow
[   228.970] (EE) event23 - 2.4G Mouse: client bug: event processing lagging behind by 23ms, your system is too slow
[   638.936] (EE) event23 - 2.4G Mouse: client bug: event processing lagging behind by 33ms, your system is too slow

There're isolated lags in the event processing, but the unsynchronized pixmap sharing between GPU and APU could indeed be a problem.

You could try the lts kernel for a regression in that area and also to drop xf86-video-amdgpu and run the modesetting driver on the amdgpu kernel module (removing the package should™ result in that unless there're xorg configlets referencing the driver)

Akadius · 2022-09-25 14:47:01

seth wrote:

Yup.
[    33.498] randr: falling back to unsynchronized pixmap sharing
[   225.025] (EE) event23 - 2.4G Mouse: client bug: event processing lagging behind by 25ms, your system is too slow
[   228.970] (EE) event23 - 2.4G Mouse: client bug: event processing lagging behind by 23ms, your system is too slow
[   638.936] (EE) event23 - 2.4G Mouse: client bug: event processing lagging behind by 33ms, your system is too slow
There're isolated lags in the event processing, but the unsynchronized pixmap sharing between GPU and APU could indeed be a problem.
You could try the lts kernel for a regression in that area and also to drop xf86-video-amdgpu and run the modesetting driver on the amdgpu kernel module (removing the package should™ result in that unless there're xorg configlets referencing the driver)

I'll try that out, lts might not be a bad idea. concerning xf86 and modesetting, I need to check with obs if it's not needed somewhere.

Akadius · 2022-09-26 09:23:47

The slow down restarted this morning, I have still the apu disabled and csm comparability disabled.

Same symptoms.

journalctl -b
http://ix.io/4bt6

sudo dmesg
http://ix.io/4bt7

sudo dmesg -t --level=alert,crit,err,warn

  #9 #10 #11 #12 #13 #14 #15
ata5.00: supports DRM functions and may not be fully accessible
ata5.00: supports DRM functions and may not be fully accessible
amdgpu: unknown parameter 'ngg' ignored
amdgpu 0000:03:00.0: amdgpu: PSP runtime database doesn't exist
amdgpu 0000:03:00.0: amdgpu: PSP runtime database doesn't exist
amdgpu: SRAT table not found
nvme nvme0: missing or invalid SUBNQN field.
ashmem_linux: loading out-of-tree module taints kernel.
ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP0.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20220331/psargs-330)
ACPI Error: Aborting method \_SB.PCI0.GPP0.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20220331/psargs-330)
ACPI Error: Aborting method \_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
kauditd_printk_skb: 15 callbacks suppressed
thermal thermal_zone0: failed to read out thermal zone (-61)
kauditd_printk_skb: 16 callbacks suppressed
kauditd_printk_skb: 1 callbacks suppressed
kauditd_printk_skb: 10 callbacks suppressed

journalctl -p 3 -b

Sep 26 11:17:55 archlinuxmain systemd-modules-load[389]: Failed to find module 'binder_linux'
Sep 26 11:17:55 archlinuxmain systemd-modules-load[389]: Failed to find module 'v4l2loopback_dc'
Sep 26 11:17:57 archlinuxmain kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP0.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20220331/psargs-330)
Sep 26 11:17:57 archlinuxmain kernel: ACPI Error: Aborting method \_SB.PCI0.GPP0.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Sep 26 11:17:57 archlinuxmain kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20220331/psargs-330)
Sep 26 11:17:57 archlinuxmain kernel: ACPI Error: Aborting method \_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Sep 26 11:18:01 archlinuxmain systemd-udevd[442]: could not find module by name='xow_blacklist'
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x70004, and key code 30: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x70006, and key code 46: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x70007, and key code 32: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x70008, and key code 18: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x70009, and key code 20: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x70014, and key code 16: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x70015, and key code 19: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x70016, and key code 31: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x7001a, and key code 17: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x7001b, and key code 71: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x7001d, and key code 77: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x7001e, and key code 2: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x7001f, and key code 3: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x70020, and key code 4: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x70021, and key code 5: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x70022, and key code 6: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x7002b, and key code 34: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x7002c, and key code 57: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x70039, and key code 75: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x7004f, and key code 33: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x70050, and key code 100: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x70051, and key code 81: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x70052, and key code 80: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x700e1, and key code 72: Invalid argument
Sep 26 11:18:03 archlinuxmain systemd-udevd[486]: event16: Failed to call EVIOCSKEYCODE with scan code 0x700e2, and key code 42: Invalid argument

Akadius · 2022-09-26 10:34:41

seth wrote:

Yup.
[    33.498] randr: falling back to unsynchronized pixmap sharing
[   225.025] (EE) event23 - 2.4G Mouse: client bug: event processing lagging behind by 25ms, your system is too slow
[   228.970] (EE) event23 - 2.4G Mouse: client bug: event processing lagging behind by 23ms, your system is too slow
[   638.936] (EE) event23 - 2.4G Mouse: client bug: event processing lagging behind by 33ms, your system is too slow
There're isolated lags in the event processing, but the unsynchronized pixmap sharing between GPU and APU could indeed be a problem.
You could try the lts kernel for a regression in that area and also to drop xf86-video-amdgpu and run the modesetting driver on the amdgpu kernel module (removing the package should™ result in that unless there're xorg configlets referencing the driver)

I tried removing xf86-video-amdgpu but xorg doesn't start. I have amdgpu in module inside mkinitcpio.conf though.

Not sure why it doesn't start.

Knowing that the slow downs are back even though my apu is disabled, mean that it might not have been the problem.

Edit:

I tried downgrading to 5.18.10 kernel but it doesn't change anything.

Last edited by Akadius (2022-09-26 11:26:06)

Lone_Wolf · 2022-09-26 11:49:21

I tried removing xf86-video-amdgpu but xorg doesn't start.

[    10.854] (==) Using config file: "/etc/X11/xorg.conf"

Probably because you're forcing X to use xf86-video-amdgpu in that xorg.conf .
move that file somewhere else (or just delete it) , then try again and post a fresh xorg log .

Akadius · 2022-09-26 14:23:01

I powered off my computer two hours ago and just came back, power on, everything works fine same as yesterday until it came back this morning.
journalctl -b
http://ix.io/4bue
sudo dmesg
http://ix.io/4buf

Current xorg.conf
http://ix.io/4bug

I'm only using amdgpu, unless this is a call for xf86-video-amdgpu.
I'll try to get ride of it to test if I can remove completely xf86.

Still I don't know how to find what trigger those slow down.

seth · 2022-09-26 14:26:07

I'm only using amdgpu, unless this is a call for xf86-video-amdgpu.

You're explicitly referencing

  Driver      "amdgpu"

make that

  Driver      "modesetting"

you should™ not even have to remove the package.
Check the xorg log to make the change applied.

Akadius · 2022-09-26 15:12:36

seth wrote:

I'm only using amdgpu, unless this is a call for xf86-video-amdgpu.
You're explicitly referencing
  Driver      "amdgpu"
make that
  Driver      "modesetting"
you should™ not even have to remove the package.
Check the xorg log to make the change applied.

I was wondering what was moddesetting in the archwiki xorg page, I though it was linked to nvidia or something.
It is done and I have remove xf86.

I guess now I have to wait for the slow down to trigger.

I wonder if I shouldn't switch to lts or zen kernel as this is my main/work machine.

It might just be a bit more stable than the stable kernel.

Thanks for the help. I'll update the thread when/if anything happens otherwise I'll mark it as solved in a week time.

Edit:

It came back. What can I check now ?

Last edited by Akadius (2022-09-26 15:29:52)

tekstryder · 2022-09-26 15:30:52

Akadius wrote:

seth wrote:

Yup.

[   225.025] (EE) event23 - 2.4G Mouse: client bug: event processing lagging behind by 25ms, your system is too slow
[   228.970] (EE) event23 - 2.4G Mouse: client bug: event processing lagging behind by 23ms, your system is too slow
[   638.936] (EE) event23 - 2.4G Mouse: client bug: event processing lagging behind by 33ms, your system is too slow

As an aside... those errors are likely innocuous. Bug report here:

https://gitlab.freedesktop.org/xorg/dri … /issues/46

Akadius · 2022-09-26 16:02:14

tekstryder wrote:

Akadius wrote:

seth wrote:

Yup.

[   225.025] (EE) event23 - 2.4G Mouse: client bug: event processing lagging behind by 25ms, your system is too slow
[   228.970] (EE) event23 - 2.4G Mouse: client bug: event processing lagging behind by 23ms, your system is too slow
[   638.936] (EE) event23 - 2.4G Mouse: client bug: event processing lagging behind by 33ms, your system is too slow

As an aside... those errors are likely innocuous. Bug report here:

https://gitlab.freedesktop.org/xorg/dri … /issues/46

Those don't seem to appear anymore.

I guess it must be xorg that slows my system, I can't think of anything else. I don't even know how to check it anymore.

Arch Linux

#1 2022-09-25 10:48:40

[Solved] Very slow system

#2 2022-09-25 12:01:54

Re: [Solved] Very slow system

#3 2022-09-25 12:12:37

Re: [Solved] Very slow system

#4 2022-09-25 12:31:02

Re: [Solved] Very slow system

#5 2022-09-25 12:33:19

Re: [Solved] Very slow system

#6 2022-09-25 12:35:03

Re: [Solved] Very slow system

#7 2022-09-25 12:35:39

Re: [Solved] Very slow system

#8 2022-09-25 12:44:36

Re: [Solved] Very slow system

#9 2022-09-25 12:56:30

Re: [Solved] Very slow system

#10 2022-09-25 13:04:22

Re: [Solved] Very slow system

#11 2022-09-25 13:10:40

Re: [Solved] Very slow system

#12 2022-09-25 13:26:43

Re: [Solved] Very slow system

#13 2022-09-25 13:41:25

Re: [Solved] Very slow system

#14 2022-09-25 13:48:48

Re: [Solved] Very slow system

#15 2022-09-25 13:52:10

Re: [Solved] Very slow system

#16 2022-09-25 14:20:02

Re: [Solved] Very slow system

#17 2022-09-25 14:47:01

Re: [Solved] Very slow system

#18 2022-09-26 09:23:47

Re: [Solved] Very slow system

#19 2022-09-26 10:34:41

Re: [Solved] Very slow system

#20 2022-09-26 11:49:21

Re: [Solved] Very slow system

#21 2022-09-26 14:23:01

Re: [Solved] Very slow system

#22 2022-09-26 14:26:07

Re: [Solved] Very slow system

#23 2022-09-26 15:12:36

Re: [Solved] Very slow system

#24 2022-09-26 15:30:52

Re: [Solved] Very slow system

#25 2022-09-26 16:02:14

Re: [Solved] Very slow system

Board footer