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.

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

PREEMPT_RT detection on kernel 6.12 #257

Open
alexswerner opened this issue Jan 15, 2025 · 1 comment · May be fixed by #260
Open

PREEMPT_RT detection on kernel 6.12 #257

alexswerner opened this issue Jan 15, 2025 · 1 comment · May be fixed by #260

Comments

@alexswerner
Copy link

Hi,

to see how things go when using a mainline kernel which has most of the PREEMPT_RT patch merged I'm trying kernel version 6.12. However, the realtime_tools does not detect that it is a kernel with PREEMPT_RT:

[ros2_control_node-1] [INFO] [1736951683.409251251] [controller_manager]: Spawning controller_manager RT thread with scheduler priority: 50
[ros2_control_node-1] [WARN] [1736951683.409437310] [controller_manager]: No real-time kernel detected on this system. See [https://control.ros.org/master/doc/ros2_control/controller_manager/doc/userdoc.html] for details on how to enable realtime scheduling.

The detection happens in

bool has_realtime_kernel()
through checking the existence of a file /sys/kernel/realtime. This file does not exists in a 6.12 kernel with PREEMPT_RT activated. Other have noticed this as well: https://forum.linuxcnc.org/38-general-linuxcnc-questions/54542-real-time-kerel-not-detected-on-patched-6-12?start=40 . In that thread people point out that this patch creates the file:
https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git/commit/?h=linux-6.12.y-rt-rebase&id=3e7545de923c4e8184c2be0b95341fdc7ef1c193 . This has not been merged for now (v6.13-rc7).

@saikishor saikishor linked a pull request Jan 19, 2025 that will close this issue
@saikishor
Copy link
Member

Hello @alexswerner!

Thanks for raising this issue. I've tried a different approach in PR: #260. Do you think this will solve the issue?. If the changes look good to you, do you mind testing it and approving the PR.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants