Bug 1699161
Summary: | kernel-5.x creates unkillable processes after suspend with Intel Wireless 8260 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Stuart D Gathman <stuart> | ||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 28 | 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-05-28 23:57:01 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
Stuart D Gathman
2019-04-11 23:29:05 UTC
Oh sorry, I didn't actually try kernel from rawhide, just updates-testing. Workaround - don't use suspend. kernel-5.0.7-100.fc28.x86_64 is also broken. It definitely seems network related. The unkillable processes always come from a list of usual suspects - all doing something with the network, specifically wireless. (Intel 8260) Notes: kernel-5.0.8-100.fc28.x86_64 is also broken. While sometimes the first suspend works, it nearly always crashes on the second suspend/resume. One thing that is always hung is sudo and su - neither can be used after the failed resume, although the terminal, graphics, window manager otherwise continue to work normally. A better workaround: Before suspending, turn off wireless, then sudo modprobe -r iwlmvm After resuming, sudo modprobe iwlmvm, then turn on wireless This should be able to be automated. It also narrows down the problem to something in the iwlmvm (or subsidiary) driver. Ok, to automate the workaround, I added this script: # cat /usr/lib/systemd/system-sleep/iwlmvm.sh #!/bin/sh if [ "${1}" == "pre" ]; then # iwlmvm driver creates unkillable processes on suspend on kernel-5.0.x modprobe -r iwlmvm elif [ "${1}" == "post" ]; then # Do the thing you want after resume here, e.g.: modprobe iwlmvm fi The workaround reliably prevents the unkillable processes. However, the resume doesn't always successfully reload the module - there seems to be a timing problem. When this happens, the module can be loaded manually. This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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. Just tested again, and this is fixed is current kernels. |