Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2080694 Information from BlockerBugs App: <img alt="2080694" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2080694" />
The votes have been last counted at 2022-05-02 15:50 UTC and the last processed comment was #comment-795368
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
Hardware specific, but increasingly common hardware.
FinalBlocker +1 FinalFE +1
FinalBlocker +1
So no one with a ryzen like this have tested kernel 5.17 before? Strange, and we have a successful kernel test week... Anyway, 5.17.5 is already at repos. FinalBlocker +1 FinalFE +1
It is hardware specific, but the outcome is bad enough (need to disconnect all batteries to make the laptop power up again) that I believe this deserves FinalBlocker +1
FinalBlocker +1 AGREED AcceptedFinalBlocker
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F36 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.