On 4/16/25 04:30 PM, Steven A. Falco wrote:
On 4/16/25 04:42 AM, Peter Robinson wrote:
I had a brief look at this earlier and there didn't look to be much specific in
the details between the reported work/fail kernels but it seems it might be
related to AMD hardware but I don't know the details of various reported
motherboard models and didn't have the time to google all the various chipsets.
It is looking like this is somehow related to the specific kernel configuration.
I tried building from the kernel-6.14.2-0 tag of the kernel-ark repo. If I use
config-6.13.10-200.fc41.x86_64 the resulting 6.14 kernel works fine.
If I instead use config-6.14.2-300.fc42.x86_64 the resulting 6.14 kernel fails
to activate some of my USB controllers.
No idea yet which configuration item is responsible. Sadly there are quite a
few differences. At some point if I have time I'll experiment further, but for
now I'll just stay with my own kernel build of 6.14 and see if it is solid. So
far it seems to be.
Found it!
If I turn off CONFIG_PCI_REALLOC_ENABLE_AUTO then all my USB devices behave.
But with CONFIG_PCI_REALLOC_ENABLE_AUTO=y then some of my USB controllers are
broken.
I'll note that in both the Fedora bug and in the upstream kernel bug. I'm not
sure what the next step would be, but this should narrow it down.
Joe - if you are able to build a kernel it would be great to know if that helps
you too.
Steve
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
