If you have other Thunderbolt 3 devices, do they also cause issues with this computer?
Do you have another Thunderbolt 3 computer to boot Linux to try the dock?
Please give "lspci -vnnt" with dock attached before boot and working so I can be sure of topology.
Mika, do you think it could it be worth changing the ACPI OSI name to mimic Windows to see if ACPI is treating us differently?
I see there is a conflict with reserved memory (I have never seen this before) but it is with the SPI controller, not Thunderbolt.
The dmesg suggests booting with pci=realloc. It is worth that with Ice Lake, Linux refuses to reassign (my theory is that ACPI _DSM method evaluates to zero).
I would really like the struct resource to be changed in Linux so that the desired alignment is preserved after assignment, so that we can see it. I suspect the dock has funny alignment expectations which we cannot easily see.
For future tests, you may want to pass pci.dyndbg to kernel parameters to give more information.
This is a bunch of random thoughts and observations for now. I will continue to scour the logs for clues.
Thanks for the additional information, Benoit.
If you have other Thunderbolt 3 devices, do they also cause issues with this computer?
Do you have another Thunderbolt 3 computer to boot Linux to try the dock?
Please give "lspci -vnnt" with dock attached before boot and working so I can be sure of topology.
Mika, do you think it could it be worth changing the ACPI OSI name to mimic Windows to see if ACPI is treating us differently?
I see there is a conflict with reserved memory (I have never seen this before) but it is with the SPI controller, not Thunderbolt.
The dmesg suggests booting with pci=realloc. It is worth that with Ice Lake, Linux refuses to reassign (my theory is that ACPI _DSM method evaluates to zero).
I would really like the struct resource to be changed in Linux so that the desired alignment is preserved after assignment, so that we can see it. I suspect the dock has funny alignment expectations which we cannot easily see.
For future tests, you may want to pass pci.dyndbg to kernel parameters to give more information.
This is a bunch of random thoughts and observations for now. I will continue to scour the logs for clues.