Bug 1802090

Summary: Systemd: Couldn't move remaining userspace processes, ignoring: Input/output error
Product: [Fedora] Fedora Reporter: Ryan <stealthcipher>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 31CC: airlied, bskeggs, fsumsal, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, lnykryn, masami256, mchehab, mjg59, msekleta, ssahani, s, steved, systemd-maint, zbyszek
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: 2020-02-12 11:04:20 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:

Description Ryan 2020-02-12 10:53:17 UTC
Description of problem:
systemd is throwing error to logs about an IO error removing userspace processes since upgrade to 5.5.2-200.fc31

Version-Release number of selected component (if applicable):
243.6-1.fc31

How reproducible:
every boot

Steps to Reproduce:
1. Participate in kernel test day and install 5.5.2-200 kernel
2. Note in `journalctl -k` the message above

Actual results:
Couldn't move remaining userspace processes, ignoring: Input/output error

Expected results:
A normal boot.

Additional info:
External issue in github against systemd (linked)

Comment 1 Frantisek Sumsal 2020-02-12 10:57:38 UTC
I think this should be re-assigned to the kernel folks, as the issue is in the kernel, not systemd, see https://github.com/systemd/systemd/issues/14682#issuecomment-580339777 and https://lore.kernel.org/lkml/20200130164717.GE180576@mtj.thefacebook.com/.

Comment 2 Frantisek Sumsal 2020-02-12 11:04:20 UTC

*** This bug has been marked as a duplicate of bug 1800003 ***