Bug 1800003

Summary:	kernel 5.5 before 5.5.5: Couldn't move remaining userspace processes, ignoring: Input/output error
Product:	[Fedora] Fedora	Reporter:	Harald Reindl <h.reindl>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	31	CC:	airlied, bskeggs, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, lnykryn, masami256, mchehab, mjg59, msekleta, ssahani, s, stealthcipher, steved, systemd-maint, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-03 13:46:11 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 Harald Reindl 2020-02-06 19:49:13 UTC Comment hidden (abuse)

i am alleric against the woirds "fail" and "error" especially  when something is talking about "Input/output error" in normal operations - systemd really needs to lear distinct between debug and regular operating with his logging

[root@testserver:~]$ systemctl daemon-reexec
[root@testserver:~]$ dmesg -c
[Thu Feb  6 20:45:26 2020] systemd[1]: systemd v243.6-1.fc31 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified)
[Thu Feb  6 20:45:26 2020] systemd[1]: Detected virtualization vmware.
[Thu Feb  6 20:45:26 2020] systemd[1]: Detected architecture x86-64.
[Thu Feb  6 20:45:26 2020] systemd[1]: Couldn't move remaining userspace processes, ignoring: Input/output error

[root@testserver:~]$ system-errors.sh
[Thu Feb  6 20:47:14 2020] systemd[1]: Couldn't move remaining userspace processes, ignoring: Input/output error
[Thu Feb  6 20:47:15 2020] systemd[1]: Couldn't move remaining userspace processes, ignoring: Input/output error
Feb  6 20:47:15 testserver systemd[1]: Couldn't move remaining userspace processes, ignoring: Input/output error
Feb  6 20:47:17 testserver systemd[1]: Couldn't move remaining userspace processes, ignoring: Input/output error

Comment 1 Zbigniew Jędrzejewski-Szmek 2020-02-06 19:54:37 UTC

Kernel version? This is apparently a kernel bug, see
https://github.com/systemd/systemd/issues/14682.

Comment 2 Harald Reindl 2020-02-06 19:55:48 UTC

Linux testserver.rhsoft.net 5.5.2-200.fc31.x86_64 #1 SMP Thu Feb 6 17:23:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

https://koji.fedoraproject.org/koji/buildinfo?buildID=1457411

Comment 3 Harald Reindl 2020-02-11 18:44:20 UTC

https://www.kernel.org/

stable: 	5.5.3 	2020-02-11

Comment 4 Harald Reindl 2020-02-12 07:05:25 UTC

[root@testserver:~]$ uname -r
5.5.3-200.fc31.x86_64

Feb 12 08:03:33 testserver systemd[1]: Couldn't move remaining userspace processes, ignoring: Input/output error
Feb 12 08:03:35 testserver systemd[1]: Couldn't move remaining userspace processes, ignoring: Input/output error

until that is fixed no way that 5.5 is touching a physical machine for testing

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

*** Bug 1802090 has been marked as a duplicate of this bug. ***

Comment 6 Ryan 2020-02-12 11:10:14 UTC

I am running Kernel-5.5.3-200.fc31 now,  it's also affected.

Comment 7 Harald Reindl 2020-02-20 00:38:46 UTC

fixed with https://koji.fedoraproject.org/koji/taskinfo?taskID=41668217

https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.5.5

commit dcf6b17b8a036bb53f65d1a4f0e1636a5df96868
Author: Tejun Heo <tj>
Date:   Thu Jan 30 11:37:33 2020 -0500

    cgroup: init_tasks shouldn't be linked to the root cgroup
    
    commit 0cd9d33ace336bc424fc30944aa3defd6786e4fe upstream.
    
    5153faac18d2 ("cgroup: remove cgroup_enable_task_cg_lists()
    optimization") removed lazy initialization of css_sets so that new
    tasks are always lniked to its css_set. In the process, it incorrectly
    ended up adding init_tasks to root css_set. They show up as PID 0's in
    root's cgroup.procs triggering warnings in systemd and generally
    confusing people.
    
    Fix it by skip css_set linking for init_tasks.
    
    Signed-off-by: Tejun Heo <tj>
    Reported-by: https://github.com/joanbm
    Link: https://github.com/systemd/systemd/issues/14682
    Fixes: 5153faac18d2 ("cgroup: remove cgroup_enable_task_cg_lists() optimization")
    Cc: stable.org # v5.5+
    Signed-off-by: Greg Kroah-Hartman <gregkh>

Comment 8 Zbigniew Jędrzejewski-Szmek 2020-03-03 13:46:11 UTC

We have kernel-5.5.7-200.fc31 and kernel-5.5.7-100.fc30 in stable now, let's close this.