For what it's worth, rc0 builds are a Fedora only thing. Upstream doesn't release rc0. They're not linux-next but they can still have these kinds of bugs. I'd say, move to kernel-6.15.0-0.rc0.20250331git4e82c87058f4.6.fc43 or stick with 6.14.0, and just abandon the kernel that isn't working. And also for reporting, it needs to go upstream. Test list can't really do much with these reports. To do that you'd need to isolate it to a part of the kernel, I'm guessing this is an ACPI bug, and report the problem on that list. So what I do is: * collect all the reproduce steps and logs, put it in a Fedora bugzilla * write up a summary email, noting the downstream bug report (the Fedora bz) [1] * send to the proper mailing list as found in a current kernel MAINTAINERS file [2] Some lists do accept emails from non-subscribed senders, others don't. I'm not sure which the ACPI list is, but I recently joined so I have this handy, otherwise you have to go dig around for it since it's a per list thing. mail to: majordomo@xxxxxxxxxxxxxxx body contains: subscribe linux-acpi [1] Example https://lore.kernel.org/linux-acpi/90e6da7b-a2b2-4ff3-bb04-f39b1f6c5e70@xxxxxxxxxxxxxxxx/ [2] https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS?h=v6.14 -- Chris Murphy -- _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/test@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
