Bug 1687065
Summary: | acer travelmate spin b1 b118 kernel crash + recovery | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | richard meinsen <richard> | ||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 29 | CC: | airlied, bskeggs, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, steved | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2019-11-27 21:26:23 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: | |||||||
Attachments: |
|
Description
richard meinsen
2019-03-09 10:01:48 UTC
Created attachment 1542317 [details]
rawhide boot log / problem also with rawhide
changing kernel repo doesn't work as described in bug report template
"sudo dnf update kernel --enablerepo=rawhide" gives gpg key errors
"sudo dnf update kernel --enablerepo=rawhide --releasever=30 --nogpg"
works but it would be better if --nogpg would not be necessary
Hmm, this can only happen if their is no ACPI companion node for the controller, so I guess your ACPI tables are missing a node for one of the i2c-controllers. I've written 2 patches to make the kernel deal properly with this. I've just started a scratch kernel-build with the 2 patches for this added: https://koji.fedoraproject.org/koji/taskinfo?taskID=33323493 Please give this a try once it is finished building (this will take a couple of hours), see here for generic instructions on how to test a kernel directly from koji: https://fedorapeople.org/~jwrdegoede/kernel-test-instructions.txt thanks, with uefi turned of and installed as described the problem seems to be fixed by your patches. will switch back to uefi on and wait till the patches are integrated in and delivered with the fedora std. kernel. i can double check then => please give me a ping then if you want. Thank you for testing the patched kernel. I've submitted the patches upstream now. This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |