In case you are already aware of the issue, feel free to ignore this
mail. I just want to make aware that there could be multiple
interrelated (bug) reports that might be considered in conjunction and
not on their own, given that the amount of affected users is above
average (I could imagine this is not limited to ask.Fedora).
As far as it concerns ask.Fedora: since 6.3 was introduced, we have many
users in ask.Fedora with issues that seem to be ACPI related (more
precisely, `ucsi_acpi`, but maybe not just this) and that makes it
impossible to use kernels after 6.2.15 except with
`module_blacklist=ucsi_acpi`.
I already asked the users to provide a bug report (this is how I became
aware that the report template was broken ;), but I am not sure if the
report(s) illustrate the number of users that have come up with the same
issue. Since not all users with issues end up on ask.Fedora, we don't
know the actual number of affected systems, but so many users with the
same kernel issue is a seldom phenomenon.
So far, most users with 6.3.X ACPI-related issues are found in this topics:
https://discussion.fedoraproject.org/t/fedora-hangs-on-boot-after-upgrading-to-kernel-6-3-4/83605/
-> black screen after grub menu with stable kernels after 6.2.15
-> everything fine with 6.2.15
-> mitigation: module_blacklist=ucsi_acpi (several users confirmed this
to mitigate the issue)
Links to the related bug reports are contained.
The nvidia-driver issue that has accidentally merged in this topic is
something different (the nvidia case is alredy solved anyway by an
earlier kernel fix). The case in which already 6.2.15 was affected seems
to be something different as well.
Except those nvidia-driver-users where a fixed kernel already solved the
issue, in the cases where we identified it, affected users had `cat
/proc/sys/kernel/tainted` = 0. Of course not all useres provided
documentation so we cannot know for sure if that applies to all.
Additionally, it might be noted that we have further reports on
ask.Fedora where users have issues that could have a link to ACPI, but
not to `ucsi_acpi` in specific - so far it is only the correlation that
6.2.15 works but everything later not, and that the respectively
described issue could be explained by ACPI-related bugs (don't know
yet). One F37 user consolidated their data in this bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=2213179 -> here the
mitigation is removing the KVM switch in between system and monitor,
although it works fine in 6.2.15. I think that's all reports with
noteworthy data/documentation.
Not sure if we have further related reports elsewhere. Also, I check at
the moment only those topics that are explicitly added to the #kernel
category since I have little time, so maybe we have more reports about it.
Best,
Chris
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
