Everything works, looking for trouble anyway (Ideapad 530S-ARR)

Questions about hardware, drivers and peripherals
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
User avatar
OveS
Level 4
Level 4
Posts: 204
Joined: Fri Jan 01, 2016 3:26 pm
Location: France

Everything works, looking for trouble anyway (Ideapad 530S-ARR)

Post by OveS »

I have this Lenovo Ideapad since a month now, and after initial issues with wifi and touchpad, everything seems to work as it should. I installed kernel 4.18 to get things working. I added touchpad support with dkms ( i2c-amd-mp2) that apparently has been submitted to be included in the kernel at some level.

But surfing around the net and different forums, all kind of stuff can be found. So now I'm wondering why there are so many warning and error messages from the kernel. Is the AMD Ryzen not completely supported yet?

Here is some information, first inxi -Fxz

Code: Select all

System:    Host: ideapad Kernel: 4.18.20-041820-generic x86_64 bits: 64 compiler: gcc v: 8.2.0 Desktop: Cinnamon 4.0.9 
           Distro: Linux Mint 19.1 Tessa base: Ubuntu 18.04 bionic 
Machine:   Type: Laptop System: LENOVO product: 81H1 v: Lenovo ideapad 530S-14ARR serial: <filter> 
           Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN serial: <filter> UEFI: LENOVO v: 8PCN50WW 
           date: 12/25/2018 
Battery:   ID-1: BAT0 charge: 45.8 Wh condition: 45.8/45.5 Wh (101%) model: CPT-COS L17C4PB0 status: Full 
CPU:       Topology: Quad Core model: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx bits: 64 type: MT MCP arch: Zen 
           L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 31938 
           Speed: 1418 MHz min/max: 1600/2000 MHz Core speeds (MHz): 1: 1391 2: 1522 3: 1537 4: 1560 5: 1381 6: 1365 
           7: 1455 8: 1457 
Graphics:  Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] vendor: Lenovo driver: amdgpu 
           v: kernel bus ID: 03:00.0 
           Display: x11 server: X.Org 1.19.6 driver: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD RAVEN (DRM 3.26.0 4.18.20-041820-generic LLVM 7.0.0) v: 4.5 Mesa 18.2.2 
           direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 03:00.1 
           Device-2: Advanced Micro Devices [AMD] vendor: Lenovo driver: N/A bus ID: 03:00.5 
           Device-3: Advanced Micro Devices [AMD] vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 03:00.6 
           Sound Server: ALSA v: k4.18.20-041820-generic 
Network:   Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Lenovo driver: ath10k_pci 
           v: kernel bus ID: 01:00.0 
           IF: wlp1s0 state: up mac: <filter> 
           Device-2: Atheros type: USB driver: btusb bus ID: 1-4:2 
Drives:    Local Storage: total: 238.47 GiB used: 83.09 GiB (34.8%) 
           ID-1: /dev/nvme0n1 model: HFM256GDHTNG-8310A size: 238.47 GiB 
Partition: ID-1: / size: 28.71 GiB used: 11.69 GiB (40.7%) fs: ext4 dev: /dev/nvme0n1p5 
           ID-2: /home size: 156.24 GiB used: 66.02 GiB (42.3%) fs: ext4 dev: /dev/nvme0n1p6 
           ID-3: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p7 
Sensors:   System Temperatures: cpu: 47.9 C mobo: N/A gpu: amdgpu temp: 47 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 276 Uptime: 1d 4h 11m Memory: 7.41 GiB used: 3.88 GiB (52.4%) Init: systemd runlevel: 5 
           Compilers: gcc: 7.3.0 Shell: bash v: 4.4.19 inxi: 3.0.27 
This report is what surprised me with its numerous errors and warnings:

dmesg -Hx --level=emerg,alert,crit,err,warn

Code: Select all

kern  :err   : [Mar 9 09:41] [Firmware Bug]: AMD-Vi: IOAPIC[4] not in IVRS table
kern  :err   : [  +0,000000] [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
kern  :err   : [  +0,000000] [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found
kern  :err   : [  +0,000000] AMD-Vi: Disabling interrupt remapping
kern  :err   : [  +0,000000] AMD-Vi: Unable to write to IOMMU perf counter.
kern  :warn  : [  +0,000185] pci 0000:00:00.2: can't derive routing for PCI INT A
kern  :warn  : [  +0,000002] pci 0000:00:00.2: PCI INT A: not connected
kern  :warn  : [  +0,004452]  PPR NX GT IA GA PC GA_vAPIC
kern  :err   : [  +0,149200] tpm_crb MSFT0101:00: can't request region for resource [mem 0xbf7a6000-0xbf7a9fff]
kern  :warn  : [  +0,000036] tpm_crb: probe of MSFT0101:00 failed with error -16
kern  :warn  : [  +0,008573] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i80
kern  :err   : [  +0,750559] PKCS#7 signature not signed with a trusted key
kern  :err   : [  +0,000028] PKCS#7 signature not signed with a trusted key
kern  :warn  : [  +0,000011] i2c_amd_mp2: loading out-of-tree module taints kernel.
kern  :err   : [  +0,011982] PKCS#7 signature not signed with a trusted key
kern  :err   : [  +0,001571] PKCS#7 signature not signed with a trusted key
kern  :err   : [  +0,000097] PKCS#7 signature not signed with a trusted key
kern  :warn  : [  +0,011177] i2c_hid i2c-MSFT0001:00: i2c-MSFT0001:00 supply vdd not found, using dummy regulator
kern  :warn  : [  +0,051719] kfd kfd: DID 15dd is missing in supported_devices
kern  :err   : [  +0,000002] kfd kfd: kgd2kfd_probe failed
kern  :err   : [  +0,264822] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service f
kern  :err   : [  +0,000060] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service f
daemon:err   : [  +1,543796] systemd[1]: /lib/systemd/system/resilio-sync.service:23: Not an absolute path, ignoring: ${SY
kern  :err   : [  +0,220252] PKCS#7 signature not signed with a trusted key
kern  :warn  : [  +0,135272] uvcvideo 3-2:1.0: Entity type for entity Extension 4 was not initialized!
kern  :warn  : [  +0,000003] uvcvideo 3-2:1.0: Entity type for entity Extension 3 was not initialized!
kern  :warn  : [  +0,000002] uvcvideo 3-2:1.0: Entity type for entity Processing 2 was not initialized!
kern  :warn  : [  +0,000001] uvcvideo 3-2:1.0: Entity type for entity Camera 1 was not initialized!
kern  :err   : [Mar 9 10:00] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000006] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000005] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 10:54] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000008] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000006] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 11:03] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000007] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000005] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 12:28] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000004] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000003] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 12:31] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000007] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000004] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 15:01] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000005] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000003] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :warn  : [Mar 9 19:39] IRQ 43: no longer affine to CPU3
kern  :warn  : [  +0,051901] IRQ 36: no longer affine to CPU5
kern  :warn  : [  +0,000027] IRQ 42: no longer affine to CPU5
kern  :warn  : [  +0,000038] IRQ 66: no longer affine to CPU5
kern  :warn  : [  +0,051457] IRQ 26: no longer affine to CPU7
kern  :warn  : [  +0,000023] IRQ 34: no longer affine to CPU7
kern  :warn  : [  +0,000017] IRQ 35: no longer affine to CPU7
kern  :warn  : [  +0,000047] IRQ 41: no longer affine to CPU7
kern  :warn  : [  +0,000047] IRQ 47: no longer affine to CPU7
kern  :warn  : [  +0,000013] IRQ fixup: irq 68 move in progress, old vector 38
kern  :warn  : [  +0,000009] IRQ 68: no longer affine to CPU7
kern  :warn  : [  +0,099862]  cache: parent cpu1 should not be sleeping
kern  :warn  : [  +0,002865]  cache: parent cpu2 should not be sleeping
kern  :warn  : [  +0,002905]  cache: parent cpu3 should not be sleeping
kern  :warn  : [  +0,003645]  cache: parent cpu4 should not be sleeping
kern  :warn  : [  +0,002981]  cache: parent cpu5 should not be sleeping
kern  :warn  : [  +0,003095]  cache: parent cpu6 should not be sleeping
kern  :warn  : [  +0,003232]  cache: parent cpu7 should not be sleeping
kern  :warn  : [  +0,188283] ACPI: button: The lid device is not compliant to SW_LID.
(END)
kern  :err   : [Mar 9 10:00] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000006] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000005] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 10:54] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000008] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000006] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 11:03] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000007] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000005] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 12:28] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000004] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000003] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 12:31] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000007] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000004] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 15:01] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000005] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000003] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :warn  : [Mar 9 19:39] IRQ 43: no longer affine to CPU3
kern  :warn  : [  +0,051901] IRQ 36: no longer affine to CPU5
kern  :warn  : [  +0,000027] IRQ 42: no longer affine to CPU5
kern  :warn  : [  +0,000038] IRQ 66: no longer affine to CPU5
kern  :warn  : [  +0,051457] IRQ 26: no longer affine to CPU7
kern  :warn  : [  +0,000023] IRQ 34: no longer affine to CPU7
kern  :warn  : [  +0,000017] IRQ 35: no longer affine to CPU7
kern  :warn  : [  +0,000047] IRQ 41: no longer affine to CPU7
kern  :warn  : [  +0,000047] IRQ 47: no longer affine to CPU7
kern  :warn  : [  +0,000013] IRQ fixup: irq 68 move in progress, old vector 38
kern  :warn  : [  +0,000009] IRQ 68: no longer affine to CPU7
kern  :warn  : [  +0,099862]  cache: parent cpu1 should not be sleeping
kern  :warn  : [  +0,002865]  cache: parent cpu2 should not be sleeping
kern  :warn  : [  +0,002905]  cache: parent cpu3 should not be sleeping
kern  :warn  : [  +0,003645]  cache: parent cpu4 should not be sleeping
kern  :warn  : [  +0,002981]  cache: parent cpu5 should not be sleeping
kern  :warn  : [  +0,003095]  cache: parent cpu6 should not be sleeping
kern  :warn  : [  +0,003232]  cache: parent cpu7 should not be sleeping
kern  :warn  : [  +0,188283] ACPI: button: The lid device is not compliant to SW_LID.
~
(END)
kern  :err   : [Mar 9 10:00] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000006] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000005] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 10:54] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000008] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000006] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 11:03] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000007] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000005] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 12:28] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000004] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000003] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 12:31] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000007] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000004] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 15:01] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000005] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000003] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :warn  : [Mar 9 19:39] IRQ 43: no longer affine to CPU3
kern  :warn  : [  +0,051901] IRQ 36: no longer affine to CPU5
kern  :warn  : [  +0,000027] IRQ 42: no longer affine to CPU5
kern  :warn  : [  +0,000038] IRQ 66: no longer affine to CPU5
kern  :warn  : [  +0,051457] IRQ 26: no longer affine to CPU7
kern  :warn  : [  +0,000023] IRQ 34: no longer affine to CPU7
kern  :warn  : [  +0,000017] IRQ 35: no longer affine to CPU7
kern  :warn  : [  +0,000047] IRQ 41: no longer affine to CPU7
kern  :warn  : [  +0,000047] IRQ 47: no longer affine to CPU7
kern  :warn  : [  +0,000013] IRQ fixup: irq 68 move in progress, old vector 38
kern  :warn  : [  +0,000009] IRQ 68: no longer affine to CPU7
kern  :warn  : [  +0,099862]  cache: parent cpu1 should not be sleeping
kern  :warn  : [  +0,002865]  cache: parent cpu2 should not be sleeping
kern  :warn  : [  +0,002905]  cache: parent cpu3 should not be sleeping
kern  :warn  : [  +0,003645]  cache: parent cpu4 should not be sleeping
kern  :warn  : [  +0,002981]  cache: parent cpu5 should not be sleeping
kern  :warn  : [  +0,003095]  cache: parent cpu6 should not be sleeping
kern  :warn  : [  +0,003232]  cache: parent cpu7 should not be sleeping
kern  :warn  : [  +0,188283] ACPI: button: The lid device is not compliant to SW_LID.
~
~
(END)
kern  :err   : [Mar 9 10:00] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000006] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000005] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 10:54] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000008] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000006] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 11:03] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000007] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000005] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 12:28] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000004] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000003] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 12:31] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000007] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000004] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 15:01] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000005] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000003] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :warn  : [Mar 9 19:39] IRQ 43: no longer affine to CPU3
kern  :warn  : [  +0,051901] IRQ 36: no longer affine to CPU5
kern  :warn  : [  +0,000027] IRQ 42: no longer affine to CPU5
kern  :warn  : [  +0,000038] IRQ 66: no longer affine to CPU5
kern  :warn  : [  +0,051457] IRQ 26: no longer affine to CPU7
kern  :warn  : [  +0,000023] IRQ 34: no longer affine to CPU7
kern  :warn  : [  +0,000017] IRQ 35: no longer affine to CPU7
kern  :warn  : [  +0,000047] IRQ 41: no longer affine to CPU7
kern  :warn  : [  +0,000047] IRQ 47: no longer affine to CPU7
kern  :warn  : [  +0,000013] IRQ fixup: irq 68 move in progress, old vector 38
kern  :warn  : [  +0,000009] IRQ 68: no longer affine to CPU7
kern  :warn  : [  +0,099862]  cache: parent cpu1 should not be sleeping
kern  :warn  : [  +0,002865]  cache: parent cpu2 should not be sleeping
kern  :warn  : [  +0,002905]  cache: parent cpu3 should not be sleeping
kern  :warn  : [  +0,003645]  cache: parent cpu4 should not be sleeping
kern  :warn  : [  +0,002981]  cache: parent cpu5 should not be sleeping
kern  :warn  : [  +0,003095]  cache: parent cpu6 should not be sleeping
kern  :warn  : [  +0,003232]  cache: parent cpu7 should not be sleeping
kern  :warn  : [  +0,188283] ACPI: button: The lid device is not compliant to SW_LID.
~
~
~
(END)
kern  :err   : [Mar 9 10:00] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000006] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000005] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 10:54] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000008] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000006] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 11:03] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000007] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000005] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 12:28] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000004] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000003] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 12:31] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000007] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000004] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 15:01] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000005] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000003] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :warn  : [Mar 9 19:39] IRQ 43: no longer affine to CPU3
kern  :warn  : [  +0,051901] IRQ 36: no longer affine to CPU5
kern  :warn  : [  +0,000027] IRQ 42: no longer affine to CPU5
kern  :warn  : [  +0,000038] IRQ 66: no longer affine to CPU5
kern  :warn  : [  +0,051457] IRQ 26: no longer affine to CPU7
kern  :warn  : [  +0,000023] IRQ 34: no longer affine to CPU7
kern  :warn  : [  +0,000017] IRQ 35: no longer affine to CPU7
kern  :warn  : [  +0,000047] IRQ 41: no longer affine to CPU7
kern  :warn  : [  +0,000047] IRQ 47: no longer affine to CPU7
kern  :warn  : [  +0,000013] IRQ fixup: irq 68 move in progress, old vector 38
kern  :warn  : [  +0,000009] IRQ 68: no longer affine to CPU7
kern  :warn  : [  +0,099862]  cache: parent cpu1 should not be sleeping
kern  :warn  : [  +0,002865]  cache: parent cpu2 should not be sleeping
kern  :warn  : [  +0,002905]  cache: parent cpu3 should not be sleeping
kern  :warn  : [  +0,003645]  cache: parent cpu4 should not be sleeping
kern  :warn  : [  +0,002981]  cache: parent cpu5 should not be sleeping
kern  :warn  : [  +0,003095]  cache: parent cpu6 should not be sleeping
kern  :warn  : [  +0,003232]  cache: parent cpu7 should not be sleeping
kern  :warn  : [  +0,188283] ACPI: button: The lid device is not compliant to SW_LID.
~
~
~
~
(END)
kern  :err   : [Mar 9 10:00] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000006] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000005] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 10:54] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000008] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000006] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 11:03] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000007] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000005] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 12:28] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000004] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000003] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 12:31] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000007] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000004] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :err   : [Mar 9 15:01] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter
kern  :err   : [  +0,000005] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
kern  :err   : [  +0,000003] pcieport 0000:00:01.2:    [12] Replay Timer Timeout  
kern  :warn  : [Mar 9 19:39] IRQ 43: no longer affine to CPU3
kern  :warn  : [  +0,051901] IRQ 36: no longer affine to CPU5
kern  :warn  : [  +0,000027] IRQ 42: no longer affine to CPU5
kern  :warn  : [  +0,000038] IRQ 66: no longer affine to CPU5
kern  :warn  : [  +0,051457] IRQ 26: no longer affine to CPU7
kern  :warn  : [  +0,000023] IRQ 34: no longer affine to CPU7
kern  :warn  : [  +0,000017] IRQ 35: no longer affine to CPU7
kern  :warn  : [  +0,000047] IRQ 41: no longer affine to CPU7
kern  :warn  : [  +0,000047] IRQ 47: no longer affine to CPU7
kern  :warn  : [  +0,000013] IRQ fixup: irq 68 move in progress, old vector 38
kern  :warn  : [  +0,000009] IRQ 68: no longer affine to CPU7
kern  :warn  : [  +0,099862]  cache: parent cpu1 should not be sleeping
kern  :warn  : [  +0,002865]  cache: parent cpu2 should not be sleeping
kern  :warn  : [  +0,002905]  cache: parent cpu3 should not be sleeping
kern  :warn  : [  +0,003645]  cache: parent cpu4 should not be sleeping
kern  :warn  : [  +0,002981]  cache: parent cpu5 should not be sleeping
kern  :warn  : [  +0,003095]  cache: parent cpu6 should not be sleeping
kern  :warn  : [  +0,003232]  cache: parent cpu7 should not be sleeping
kern  :warn  : [  +0,188283] ACPI: button: The lid device is not compliant to SW_LID.
What can I do to "clean this up"? Please note, however, I'm not a developer or anything like that, just an end user with a lot of technical curiosity.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
--
Minisforum X400 (AMD Ryzen 4350G, 16/512GB)
MacBook Air M1 --- iPad Air 5th Gen
Raspberry Pi 4 4GB (NextcloudPi server)
User avatar
Pjotr
Level 23
Level 23
Posts: 19880
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland) 🇳🇱
Contact:

Re: Everything works, looking for trouble anyway (Ideapad 530S-ARR)

Post by Pjotr »

Well, there are some known Ryzen problems. Solutions in this thread:
viewtopic.php?f=49&t=285701&p=1579867
Tip: 10 things to do after installing Linux Mint 21.3 Virginia
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
User avatar
OveS
Level 4
Level 4
Posts: 204
Joined: Fri Jan 01, 2016 3:26 pm
Location: France

Re: Everything works, looking for trouble anyway (Ideapad 530S-ARR)

Post by OveS »

Thank you! I installed the upstream amdgpu firmware stuff and the post-boot list of errors seems shorter:

Code: Select all

kern  :err   : [Mar10 16:21] [Firmware Bug]: AMD-Vi: IOAPIC[4] not in IVRS table
kern  :err   : [  +0,000000] [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
kern  :err   : [  +0,000000] [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found
kern  :err   : [  +0,000000] AMD-Vi: Disabling interrupt remapping
kern  :err   : [  +0,000000] AMD-Vi: Unable to write to IOMMU perf counter.
kern  :warn  : [  +0,000271] pci 0000:00:00.2: can't derive routing for PCI INT A
kern  :warn  : [  +0,000001] pci 0000:00:00.2: PCI INT A: not connected
kern  :warn  : [  +0,004943]  PPR NX GT IA GA PC GA_vAPIC
kern  :err   : [  +0,151181] tpm_crb MSFT0101:00: can't request region for resource [mem 0xbf7a6000-0xbf7a9fff]
kern  :warn  : [  +0,000037] tpm_crb: probe of MSFT0101:00 failed with error -16
kern  :warn  : [  +0,008659] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
kern  :err   : [  +0,758061] PKCS#7 signature not signed with a trusted key
kern  :err   : [  +0,000038] PKCS#7 signature not signed with a trusted key
kern  :warn  : [  +0,000015] i2c_amd_mp2: loading out-of-tree module taints kernel.
kern  :err   : [  +0,010052] PKCS#7 signature not signed with a trusted key
kern  :err   : [  +0,001316] PKCS#7 signature not signed with a trusted key
kern  :err   : [  +0,000143] PKCS#7 signature not signed with a trusted key
kern  :warn  : [  +0,009938] i2c_hid i2c-MSFT0001:00: i2c-MSFT0001:00 supply vdd not found, using dummy regulator
kern  :warn  : [  +0,047948] kfd kfd: DID 15dd is missing in supported_devices
kern  :err   : [  +0,000001] kfd kfd: kgd2kfd_probe failed
kern  :err   : [  +0,308080] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector
kern  :err   : [  +0,000060] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector
daemon:err   : [  +1,534162] systemd[1]: /lib/systemd/system/resilio-sync.service:23: Not an absolute path, ignoring: ${SYNC_RUN_DIR}/
kern  :err   : [  +0,266340] PKCS#7 signature not signed with a trusted key
kern  :err   : [  +0,000484] PKCS#7 signature not signed with a trusted key
kern  :warn  : [  +0,063224] uvcvideo 3-2:1.0: Entity type for entity Extension 4 was not initialized!
kern  :warn  : [  +0,000003] uvcvideo 3-2:1.0: Entity type for entity Extension 3 was not initialized!
kern  :warn  : [  +0,000002] uvcvideo 3-2:1.0: Entity type for entity Processing 2 was not initialized!
kern  :warn  : [  +0,000002] uvcvideo 3-2:1.0: Entity type for entity Camera 1 was not initialized!
--
Minisforum X400 (AMD Ryzen 4350G, 16/512GB)
MacBook Air M1 --- iPad Air 5th Gen
Raspberry Pi 4 4GB (NextcloudPi server)
User avatar
thx-1138
Level 8
Level 8
Posts: 2092
Joined: Fri Mar 10, 2017 12:15 pm
Location: Athens, Greece

Re: Everything works, looking for trouble anyway (Ideapad 530S-ARR)

Post by thx-1138 »

OveS wrote: Sun Mar 10, 2019 11:28 am..............................
...try passing the following to grub's parameters:
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 idle=nomwait iommu=soft
The kfd & drm:construct will likely go away at some point via kernel updates. The uvcvideo ones are innocent.
The tpm, you could probably disable it in the bios, and save some (not really much) battery as well.
If you find it spams the log after disabling it there, re-enable it, and ignore it...
The resilio one: you have to ask it's developers why their service is not correct in the first place...
User avatar
OveS
Level 4
Level 4
Posts: 204
Joined: Fri Jan 01, 2016 3:26 pm
Location: France

Re: Everything works, looking for trouble anyway (Ideapad 530S-ARR)

Post by OveS »

Cool!

Code: Select all

kern  :err   : [Mar10 16:55] tpm_crb MSFT0101:00: can't request region for resource [mem 0xbf7a6000-0xbf7a9f
kern  :warn  : [  +0,000035] tpm_crb: probe of MSFT0101:00 failed with error -16
kern  :warn  : [  +0,010725] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please
kern  :err   : [  +0,749172] PKCS#7 signature not signed with a trusted key
kern  :warn  : [  +0,000051] i2c_amd_mp2: loading out-of-tree module taints kernel.
kern  :err   : [  +0,000006] PKCS#7 signature not signed with a trusted key
kern  :err   : [  +0,009684] PKCS#7 signature not signed with a trusted key
kern  :warn  : [  +0,013872] i2c_hid i2c-MSFT0001:00: i2c-MSFT0001:00 supply vdd not found, using dummy regu
kern  :warn  : [  +0,050377] kfd kfd: DID 15dd is missing in supported_devices
kern  :err   : [  +0,000001] kfd kfd: kgd2kfd_probe failed
kern  :err   : [  +0,300323] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Ada
kern  :err   : [  +0,000060] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Ada
daemon:err   : [  +1,557953] systemd[1]: /lib/systemd/system/resilio-sync.service:23: Not an absolute path, 
kern  :err   : [  +0,214799] PKCS#7 signature not signed with a trusted key
kern  :warn  : [  +0,169364] uvcvideo 3-2:1.0: Entity type for entity Extension 4 was not initialized!
kern  :warn  : [  +0,000004] uvcvideo 3-2:1.0: Entity type for entity Extension 3 was not initialized!
kern  :warn  : [  +0,000002] uvcvideo 3-2:1.0: Entity type for entity Processing 2 was not initialized!
kern  :warn  : [  +0,000002] uvcvideo 3-2:1.0: Entity type for entity Camera 1 was not initialized!
I'm very satisfied with these improvements, thank you @Pjotr and @thx-1138 !
--
Minisforum X400 (AMD Ryzen 4350G, 16/512GB)
MacBook Air M1 --- iPad Air 5th Gen
Raspberry Pi 4 4GB (NextcloudPi server)
User avatar
Pjotr
Level 23
Level 23
Posts: 19880
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland) 🇳🇱
Contact:

Re: Everything works, looking for trouble anyway (Ideapad 530S-ARR)

Post by Pjotr »

To make applying these fixes easier, I've written a simple step-by-step how-to for it:
https://easylinuxtipsproject.blogspot.c ... .html#ID27
(item 27)
Tip: 10 things to do after installing Linux Mint 21.3 Virginia
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
User avatar
thx-1138
Level 8
Level 8
Posts: 2092
Joined: Fri Mar 10, 2017 12:15 pm
Location: Athens, Greece

Re: Everything works, looking for trouble anyway (Ideapad 530S-ARR)

Post by thx-1138 »

...the ivrs tables / device mapping is not always identical, the above was (relatively) specific to Oves' model.
Eg. different Lenovo model / example (with Ryzen as well) here.
Someone can manually find the addresses for his/her system with the following procedure.

The iommu=soft is also somewhat of a secondary measure, a generalized precaution if you will,
more in the line of, since the hardware's iommu already has it's issues, better avoid using such for the time being...
Lots of Ryzen systems still seem to experience weird issues with iommu (AMD-Vi),
either getting page faults, or not even being able to install in the first place...
and people found that booting with either iommu=pt (passthrough) or iommu=soft is a viable workaround.
However someone might also just be fine without it - it might and it might not be 'necessarily needed',
in contrast to the previous two parameters...

There isn't really a 'single-one-fix' for them all...depends on how messed up the BIOS firmware is.
Without updates from the vendor, there's only so much kernel devs can do.
It's way more accurate for someone to check his/her logs,
and then dig reports for similar error messages / components in kernel's bugzilla...
User avatar
Pjotr
Level 23
Level 23
Posts: 19880
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland) 🇳🇱
Contact:

Re: Everything works, looking for trouble anyway (Ideapad 530S-ARR)

Post by Pjotr »

thx-1138 wrote: Wed Mar 20, 2019 8:44 am ...the ivrs tables / device mapping is not always identical, the above was (relatively) specific to Oves' model.
Eg. different Lenovo model / example (with Ryzen as well) here.
Someone can manually find the addresses for his/her system with the following procedure.

The iommu=soft is also somewhat of a secondary measure, a generalized precaution if you will,
more in the line of, since the hardware's iommu already has it's issues, better avoid using such for the time being...
Lots of Ryzen systems still seem to experience weird issues with iommu (AMD-Vi),
either getting page faults, or not even being able to install in the first place...
and people found that booting with either iommu=pt (passthrough) or iommu=soft is a viable workaround.
However someone might also just be fine without it - it might and it might not be 'necessarily needed',
in contrast to the previous two parameters...

There isn't really a 'single-one-fix' for them all...depends on how messed up the BIOS firmware is.
Without updates from the vendor, there's only so much kernel devs can do.
It's way more accurate for someone to check his/her logs,
and then dig reports for similar error messages / components in kernel's bugzilla...
Thanks for this extra information.... I'm looking for measures that can be applied (more or less) generically. Would this be roughly generic:

Code: Select all

GRUB_CMDLINE_LINUX="idle=nomwait iommu=soft"
or should it only be this:

Code: Select all

GRUB_CMDLINE_LINUX="iommu=soft"
Tip: 10 things to do after installing Linux Mint 21.3 Virginia
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
User avatar
thx-1138
Level 8
Level 8
Posts: 2092
Joined: Fri Mar 10, 2017 12:15 pm
Location: Athens, Greece

Re: Everything works, looking for trouble anyway (Ideapad 530S-ARR)

Post by thx-1138 »

I'd only recommend in a more generic manner the idle=nomwait myself,
as the others are somewhat more involved / system-specific...

Over-generalizing now, maybe kinda think of the iommu soft/pt parameters for Ryzens,
sort of like the 'equivalent' of i8042.reset i8042.nomux for non-detected touchpads...
Yes, that would likely be the very first parameter i'd try upon a non-detected touchpad, but it's certainly not a silver bullet
(and might as well make things worse or at least more complicated, especially for people without much experience...)

Edit: here's a (not-so-)nice bug report of just how convoluted it is / can get,
depending on Ryzen version, firmware etc (ie. why it's also preferable for someone to try digging more specifically)...
Last edited by thx-1138 on Wed Mar 20, 2019 10:40 am, edited 1 time in total.
User avatar
Pjotr
Level 23
Level 23
Posts: 19880
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland) 🇳🇱
Contact:

Re: Everything works, looking for trouble anyway (Ideapad 530S-ARR)

Post by Pjotr »

thx-1138 wrote: Wed Mar 20, 2019 10:25 am I'd only recommend in a more generic manner the idle=nomwait myself,
as the others are somewhat more involved / system-specific...
OK, idle=nomwait it is. I've corrected my how-to. :)

Having such a generic set of measures has the advantage that they can be applied without previous system-specific research. And they might (hopefully) be sufficient in many cases....

Thanks for sharing your knowledge!
Tip: 10 things to do after installing Linux Mint 21.3 Virginia
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
Locked

Return to “Hardware Support”