Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"failed to get cgroup ignoring no medium found" #28469

Closed
memory-colors opened this issue Jul 20, 2023 · 6 comments · Fixed by #28477
Closed

"failed to get cgroup ignoring no medium found" #28469

memory-colors opened this issue Jul 20, 2023 · 6 comments · Fixed by #28477
Labels
bug 🐛 Programming errors, that need preferential fixing udev

Comments

@memory-colors
Copy link

systemd version the issue has been seen with

254-rc2-3

Used distribution

Debian Unstable

Linux kernel version used

6.3.0-2-amd64

CPU architectures issue was seen on

x86_64

Component

No response

Expected behaviour you didn't see

No response

Unexpected behaviour you saw

The message "failed to get cgroup ignoring no medium found" appears after GRUB screen. System boots normally.

Steps to reproduce the problem

Upgrade to 254-rc2-3, reboot.

Additional program output to the terminal or log subsystem illustrating the issue

No response
@memory-colors memory-colors added the bug 🐛 Programming errors, that need preferential fixing label Jul 20, 2023
@bluca
Copy link
Member

bluca commented Jul 20, 2023

That means the cgroup fs is not set up correctly, so it seems a valid warning? Was it a false positive?

@mbiebl
Copy link
Contributor

mbiebl commented Jul 20, 2023

I'm seeing that as well (initramfs-tools, not dracut). Besides the error message during early boot, I haven't noticed any ill effects caused by it.

@mbiebl
Copy link
Contributor

mbiebl commented Jul 20, 2023

Do we have to update initramfs-tools in the way it mounts / sets up cgroups ?

@bluca
Copy link
Member

bluca commented Jul 20, 2023

@yuwata will anything break in udev if it runs without cgroup fs?

@memory-colors
Copy link
Author

valid

I've never set up cgroups. This is a relatively recent installation.

@yuwata yuwata added the udev label Jul 20, 2023
yuwata added a commit to yuwata/systemd that referenced this issue Jul 21, 2023
@yuwata
udev: downgrade log level when running without cgroup
3a76ac3 
The cgroup path is optional, hence it is not necessary to warn the
failure loudly.

Closes systemd#28469.
yuwata added a commit to yuwata/systemd that referenced this issue Jul 21, 2023
@yuwata
udev: downgrade log level when running without cgroup
aa0d5d8 
The cgroup path is optional, hence it is not necessary to warn the
failure loudly.

Follow-up for f8371db.

Closes systemd#28469.
@yuwata yuwata mentioned this issue Jul 21, 2023
Merged
@yuwata
Copy link
Member

yuwata commented Jul 21, 2023

Fix is waiting in #28477.

yuwata added a commit that referenced this issue Jul 21, 2023
@yuwata
udev: downgrade log level when running without cgroup
01b030c 
The cgroup path is optional, hence it is not necessary to warn the
failure loudly.

Follow-up for f8371db.

Closes #28469.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug 🐛 Programming errors, that need preferential fixing udev
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

udev: downgrade log level when running without cgroup yuwata/systemd
4 participants
@bluca @mbiebl @yuwata @memory-colors