Bug 2124986
| Summary: | upowerd fail to initialize in kernel 5.19 printing a trace in kernel log | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Hector Vido <hvidosil> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 37 | CC: | acaringi, airlied, alciregi, awilliam, bcotton, bskeggs, eelena, gmarr, hdegoede, hpa, jarodwilson, jforbes, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, robatino, steved | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | kernel-5.19.8-300.fc37 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-09-12 17:47:26 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: | 2009539 | ||||||
| Attachments: |
|
||||||
|
Description
Hector Vido
2022-09-07 16:22:54 UTC
Proposed as a Blocker for 37-beta by Fedora user hectorvido using the blocker tracking app because: Booting the machine with a kernel higher than 5.18 makes upowerd unstable, failing to initialize, printing traces in kernel logs and slowing the start up and shutdown. Looks like this problem is describe here https://bbs.archlinux.org/viewtopic.php?id=279027 and a fix is already inside the kernel https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=5f73aa2cf8bef4a39baa1591c3144ede4788826e The problem don't happen with the rawhide kernel (6.0.0-0.rc4.31.fc38.x86_64) on Fedora 36. Please make the bug public if you want to propose it as a release blocker. Fedora is a public project, and non-Red Hatters need to be able to see the bug. Thanks! Thanks, makes sense, don't know why I was created as private. I was trying to do it, but for some reason, probably permission, I cannot remove the "fedora_contrib_private" group from the Groups List. Thanks, Andre. I assumed it was RH-private, my bad, but fedora_contrib_private is still not necessary :) Also happens here with a Thinkpad P1 gen 2 connected to a ThinkPad Thunderbolt 4 Dock. System becomes unresponsive, sometimes after a few hours being idle, sometimes after a few minutes while being used. In today's F37 Beta Go/No-Go meeting, we agreed to reject this as an F37 Beta blocker as it does not violate any basic or beta release criteria. https://meetbot.fedoraproject.org/fedora-meeting/2022-09-08/f37-beta-go_no_go-meeting.2022-09-08-17.00.log.html#l-121 I am going to nominate this as an F37 Final blocker on the "All system services present after installation with one of the release-blocking package sets must start properly, unless they require hardware which is not present." criterion https://fedoraproject.org/wiki/Fedora_37_Final_Release_Criteria#System_services This should be fixed with 5.19.8 pushing to stable now. Thanks for the quick update, I can't reproduce it with kernel-5.19.8-200.fc36.x86_64. Same think here, it is gone, there is nothing in the logs about upower with kernel 5.19.8-200.fc36.x86_64. Thank you! Should I close or it still need to go through more validations? Since the bug is filed against F37, we should wait till the F37 update is pushed stable: https://bodhi.fedoraproject.org/updates/FEDORA-2022-87b1c059b6 FEDORA-2022-87b1c059b6 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-87b1c059b6 FEDORA-2022-87b1c059b6 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. Discussed during the 2022-09-12 blocker review meeting: [0] The decision to delay the classification of this as a blocker bug was made as the vote here is kind of split, but in any case the bug will be closed soon as it's confirmed fixed in 5.19.8, so we'll just punt it and it should have gone away by next week. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-09-12/f37-blocker-review.2022-09-12-16.01.txt |