Thank you for your suggestion Mika, as a general rule I totally agree with you and I do not mess with kernel default parameters, but I remember "pcie_aspm=off" was necessary at the time I set up the system. Probably a kernel or a BIOS update makes it unnecessary today.
I see it removes these messages from my logs but I trust you when you say they have not an impact on functionality:
May 21 11:01:36 um773arch kernel: pcieport 0000:05:04.0: Unable to change power state from D3hot to D0, device inaccessible May 21 11:01:36 um773arch kernel: igb 0000:09:00.0 eth0: PCIe link lost May 21 11:01:36 um773arch kernel: xhci_hcd 0000:08:00.0: xHCI host controller not responding, assume dead May 21 11:01:36 um773arch kernel: xhci_hcd 0000:07:00.0: xHCI host controller not responding, assume dead May 21 11:01:36 um773arch kernel: usb 3-1: 1:1: cannot set freq 48000 to ep 0x82 May 21 11:01:36 um773arch kernel: usb 3-1: 10:0: cannot get min/max values for control 2 (id 10) May 21 11:01:41 um773arch kernel: xhci_hcd 0000:06:00.0: xHCI host controller not responding, assume dead May 21 11:01:41 um773arch kernel: xhci_hcd 0000:06:00.0: HC died; cleaning up May 21 11:01:41 um773arch kernel: usb 1-2: 1:1: cannot set freq 48000 to ep 0x1 May 21 11:01:41 um773arch kernel: usb 1-2: 1:2: cannot set freq 48000 to ep 0x1 May 21 11:01:41 um773arch kernel: usb 1-2: 1:3: cannot set freq 96000 to ep 0x1 May 21 11:01:41 um773arch kernel: usb 1-2: 1:4: cannot set freq 96000 to ep 0x1 May 21 11:01:41 um773arch kernel: usb 1-2: 1:5: cannot set freq 48000 to ep 0x1 May 21 11:01:41 um773arch kernel: usb 1-2: 2:1: cannot set freq 48000 to ep 0x82 May 21 11:01:41 um773arch kernel: usb 1-2: 7:0: cannot get min/max values for control 2 (id 7) May 21 11:01:41 um773arch kernel: usb 1-2: 5:0: cannot get min/max values for control 2 (id 5) May 21 11:01:41 um773arch kernel: usb 1-2: 6:0: cannot get min/max values for control 2 (id 6) May 21 11:01:41 um773arch (udev-worker)[453]: controlC0: /usr/lib/udev/rules.d/78-sound-card.rules:5 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:03.1/0000:04:00.0/0000:05:01.0/0000:07:00.0/usb3/3-1/3-1:1.0/sound/card0/controlC0/../uevent}, ignoring: No such file or directory May 21 11:01:42 um773arch (udev-worker)[440]: controlC1: /usr/lib/udev/rules.d/78-sound-card.rules:5 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:03.1/0000:04:00.0/0000:05:00.0/0000:06:00.0/usb1/1-2/1-2:1.0/sound/card1/controlC1/../uevent}, ignoring: No such file or directory May 21 11:01:43 um773arch kernel: hid-generic 0003:0D8C:0134.000A: No inputs registered, leaving
On Tue, May 21, 2024 at 10:55 AM Mika Westerberg mika.westerberg@linux.intel.com wrote:
Hi,
On Tue, May 21, 2024 at 10:07:23AM +0200, Gia wrote:
Thank you Mika,
Here you have the output of sudo journalctl -k without enabling the kernel option "pcie_aspm=off": https://codeshare.io/7JPgpE. Without "pcie_aspm=off", "thunderbolt.host_reset=false" is not needed, my thunderbolt dock does work. I also connected a 4k monitor to the thunderbolt dock thinking it could provide more data.
I'm almost sure I used this option when I set up this system because it solved some issues with system suspending, but it happened many months ago.
Okay. I recommend not to use it. The defaults should always be the best option (unless you really know what you are doing or working around some issue).
The dmesg you shared looks good, there are few oddities but they should not matter from functional perspective (unless you are planning to have a second monitor connected).
First is this:
May 21 09:59:40 um773arch kernel: thunderbolt 0000:36:00.5: IOMMU DMA protection is disabled
It should really be enabled but I'm not familiar with AMD hardware to tell more so hoping Mario can comment on that.
The second thing is the USB4 link that seems to be degraded to 2x10G = 20G even though you say it is a Thunderbolt cable. I'll comment more on that in the other email.