netneo You have driver/HW issues:
$ fgrep -i error dmesg.txt
[ 1.000000] RTC BIOS diagnostic error 0x80<clock_battery>
[ 1.000003] ACPI Error: Needed type [Reference], found [Integer] 0xffffe5d492d6d828 (20190405/exresop-114)
[ 1.000003] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20190405/dswexec-500)
[ 1.000003] ACPI Error: Aborting method \_PR.CPU0._PDC due to previous error (AE_AML_OPERAND_TYPE) (20190405/psparse-581)
[ 1.044299] hdaudio0: autoconfiguration error: RIRB timeout
[ 1.044299] hdaudio0: autoconfiguration error: RIRB timeout
[ 5.782173] WARNING: 2 errors while detecting hardware; check system log.
[ 216.275986] iwm0: autoconfiguration error: fatal firmware error
[ 230.571001] iwm0: autoconfiguration error: fatal firmware error
[ 232.571703] iwm0: autoconfiguration error: could not add MAC context (error 35)
[ 251.268259] iwm0: autoconfiguration error: fatal firmware error
[ 253.268960] iwm0: autoconfiguration error: could not add MAC context (error 35)
[ 272.965868] iwm0: autoconfiguration error: fatal firmware error
[ 274.966569] iwm0: autoconfiguration error: could not add MAC context (error 35)
$
Taking these in sequence:
[ 1.000000] RTC BIOS diagnostic error 0x80<clock_battery>
...
[ 5.802180] WARNING: clock gained 6 days
Is one of your batteries not working? Loose connection? Check BIOS date and time.
[ 1.000003] x2APIC available but disabled by DMAR table
[ 1.000003] ACPI Error: Needed type [Reference], found [Integer] 0xffffe5d492d6d828 (20190405/exresop-114)
[ 1.000003] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20190405/dswexec-500)
[ 1.000003] ACPI Error: Aborting method \_PR.CPU0._PDC due to previous error (AE_AML_OPERAND_TYPE) (20190405/psparse-581)
This is a BIOS bug. Update your BIOS.
[ 216.275986] iwm0: autoconfiguration error: fatal firmware error
[ 230.571001] iwm0: autoconfiguration error: fatal firmware error
Driver issue. File a bug against iwm
.
Are you having network speed issues with your wired, or, your wireless connection?
Have you tried an i3perf
test using both?
[ 7476.648096] pms_input: unusual delay (0.060029 s), scheduling reset
[ 7631.198163] pms_input: unusual delay (0.050026 s), scheduling reset
[ 7708.288097] pms_input: unusual delay (0.060029 s), scheduling reset
Driver issue again. Explans the audio glitches. File a bug against pms/synaptics
.
Edit: before filing a bug, try the latest -HEAD image; then, if it still doesn't work there, file a bug against that instead of 9.2 or 9.1. Bug fixes first go into -HEAD, then are back-ported into -STABLE as needed. And don't worry, -HEAD is actually quite -STABLE for daily use (usually)😁.