https://bugzilla.kernel.org/show_bug.cgi?id=63661 claims to be the same as this bug and that the problem is caused by "pci: Rework ASPM disable code" from commit 3c076351c4027a56d5005a39a0b518a4ba393ce2.
I'm not 100% sure that's the case, because comment #8 reports that "pci=conf1" is a workaround, and I don't know how that would be related to ASPM.
I would like to see complete dmesg logs and "lspci -vvxxx" output both with and without "pci=conf1" to explore that issue. Obviously a user should not have to specify a parameter like that to get things to work.
https:/ /bugzilla. kernel. org/show_ bug.cgi? id=63661 claims to be the same as this bug and that the problem is caused by "pci: Rework ASPM disable code" from commit 3c076351c4027a5 6d5005a39a0b518 a4ba393ce2.
I'm not 100% sure that's the case, because comment #8 reports that "pci=conf1" is a workaround, and I don't know how that would be related to ASPM.
I would like to see complete dmesg logs and "lspci -vvxxx" output both with and without "pci=conf1" to explore that issue. Obviously a user should not have to specify a parameter like that to get things to work.