#59 1874117 5.8.3-300.fc33.aarch64 kernel panic on boot (X-Gene PMU)
Closed 3 years ago by blockerbot. Opened 3 years ago by blockerbot.

Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1874117

Current vote summary

The votes have been last counted at 2020-09-04 08:07 UTC and the last processed comment was #comment-675851

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review


Proposing as a blocker for F33 beta, this greatly inhibits testing on aarch64.

@pwhalen Can you elaborate on this please? What is an "ampere eMag"? Is it on the list of release-blocking arm devices? (Just yesterday we were talking about still not being clear where this list is). How does this affect testing? Thanks.

Proposing as a blocker for F33 beta, this greatly inhibits testing on aarch64.

@pwhalen Can you elaborate on this please? What is an "ampere eMag"? Is it on the list of release-blocking arm devices? (Just yesterday we were talking about still not being clear where this list is). How does this affect testing? Thanks.

The Ampere eMag is enterprise hardware that is used extensively for internal testing and in our infrastructure. We do not have a release blocking device list for aarch64.

This affects any device that uses the X-Gene PMU driver, which includes a fair amount of aarch64 enterprise hardware.

In this case is it fitting to say that this "Bug hinders execution of required Beta test plans or dramatically reduces test coverage", when it comes to aarch64 testing (or perhaps even armhfp)?
https://fedoraproject.org/wiki/Fedora_33_Beta_Release_Criteria#Beta_Blocker_Bugs

If it affects hardware which a large portion of end users might use, that's another reason for blocking. What is your thought on having this Beta vs Final in this case?

In this case is it fitting to say that this "Bug hinders execution of required Beta test plans or dramatically reduces test coverage", when it comes to aarch64 testing (or perhaps even armhfp)?
https://fedoraproject.org/wiki/Fedora_33_Beta_Release_Criteria#Beta_Blocker_Bugs

Yes, that was the criteria I was looking for, thanks!

If it affects hardware which a large portion of end users might use, that's another reason for blocking. What is your thought on having this Beta vs Final in this case?

Beta blocker, this hardware is widely deployed and used by developers working on various Fedora issues (just had someone hit it on an Osprey system).

@pwhalen Please vote here as well, thanks.

Based on info provided by @pwhalen , I vote as

BetaBlocker +1

AGREED AcceptedBetaBlocker Bug hinders execution of required Beta test plans or dramatically reduces test coverage on aarch64.

The following votes have been closed:

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

3 years ago

Release F33 is no longer tracked by BlockerBugs, closing this ticket.

Login to comment on this ticket.

Metadata