Created attachment 1910262 [details] journalctl log 1. Please describe the problem: 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 2. What is the Version-Release number of the kernel: 5.19.7-300, but happens with any kernel higher than 5.18. 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : Yes it worked previously with kernel 5.18, the problem started with kernel 5.19.6 after an upgrade. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: This happens only when the notebook is plugged in the Lenovo Dockstation Thinkpad Thunderbolt 3 Dock Gen using a any kernel based on 5.19. This dockstation is delivered by Red Hat to its associates and probably there is a lot out there (a least here in Brazil). 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: This happens in Fedora 36 for a quite some time and Fedora 37 beta, I can't test the latest kernel right now, but I will. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag.
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