Bug 1874117
| Summary: | 5.8.3-300.fc33.aarch64 kernel panic on boot (X-Gene PMU) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Paul Whalen <pwhalen> | ||||||
| Component: | kernel | Assignee: | Peter Robinson <pbrobinson> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 33 | CC: | acaringi, airlied, awilliam, bskeggs, fzatlouk, hdegoede, ichavero, itamar, jarodwilson, jcm, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, mjg59, msalter, pbrobinson, robatino, steved | ||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||
| Target Release: | --- | ||||||||
| Hardware: | aarch64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | AcceptedBlocker | ||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-10-13 20:49:50 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 245418, 1766775, 1766777 | ||||||||
| Attachments: |
|
||||||||
|
Description
Paul Whalen
2020-08-31 15:34:34 UTC
Created attachment 1713174 [details]
fulll boot log
Last working kernel was 5.8.2-300.fc33.aarch64 5.8.3-300.fc33.aarch64 panics on boot. Created attachment 1713385 [details]
Fix uninitialized variable in xgene PMU driver
A recent v5.9-rc1 patch uncovered a long standing bug in xgene PMU driver. This patche initializes the resource struct so that later reference to a bad pointer is avoided.
I'll send a patch upstream tomorrow. Patch pushed to 5.8.x for F-33/32/31. Thanks for the patch Mark. Proposing as a blocker for F33 beta, this greatly inhibits testing on aarch64. Affects any device that uses the X-Gene PMU driver, not just the Ampere eMag. Accepted as Beta Blocker per voting in https://pagure.io/fedora-qa/blocker-review/issue/59 . Bug hinders execution of required Beta test plans or dramatically reduces test coverage on aarch64. 5.8.6-301.fc33.aarch64 boots as expected on the emag. Thanks again Mark. FEDORA-2020-5081eec059 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-5081eec059 FEDORA-2020-5081eec059 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. This isn't properly fixed, there's a new fix headed upstream for 5.10: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/commit/?h=for-next/core&id=a76b8236edcf Proposed as a Blocker for 33-final by Fedora user pbrobinson using the blocker tracking app because: Issues on enterprise aarch64 Ampete eMAG systems including the HW we use for the builders. FEDORA-2020-9664e2f1d2 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-9664e2f1d2 FEDORA-2020-9664e2f1d2 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-9664e2f1d2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-9664e2f1d2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-9664e2f1d2 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. The update apparently wasn't marked as fixing the bug; can we close it or is something else needed? Thanks! (In reply to Adam Williamson from comment #17) > The update apparently wasn't marked as fixing the bug; can we close it or is > something else needed? Thanks! Which update? I updated to a newer more robust fix that is landing upstream in 5.10 as part of the 5.8.14 kernel, it seems the changelog was trimmed. So IMO this can be closed. * Wed Oct 7 2020 Peter Robinson <pbrobinson> - Fix aarch64 boot crash on BTI capable systems - Fix boot crash on aarch64 Ampere eMAG systems (rhbz #1874117) * Thu Oct 1 12:09:16 CDT 2020 Justin M. Forbes <jforbes> - 5.8.13-300 - Linux v5.8.13 https://bodhi.fedoraproject.org/updates/FEDORA-2020-9664e2f1d2 - #c16 above says it was pushed to stable. That was the 5.8.14-300 update. So if you think that fixed it, let's go ahead and close. |