thin lto brakes corefreq

[LethalManBoob]

thin lto brakes corefreq

[cyring]

Indeed I can see bad connection issues with the backend:

• SysGate is Off
• No Vcore, neither temperature reported
• Caches and probably others are not displayed

CachyOS was a best effort to support but this kernel mod is too patched for a long term programming environment.
Thus your guys have to troubleshoot more than that and will be kind to verify or provide the kernel log to investigate CachyOS Patches which may conflict with the Linux mainstream kernel.

[LethalManBoob]

Turns out the LTO THIN and rt brakes dkms

[cyring]

Turns out the LTO THIN and rt brakes dkms

Regarding the AUR you may get a little help from @inglor but not sure if CachyOS is supported by package.
If not then I would suggest you manually clone or download CoreFreq source code, next build and run straight from the project directory. See CoreFreq Readme.md
However make sure before the kernel development prerequisites of CoreFreq are well installed with your CachyOS: gcc compiler, make, kernel headers, glibc. These are usually pulled by the dkms package, even if you don't use it -;)

[inglor]

@LethalManBoob you might have a better support if you were using any of the Arch Linux kernels from the repos. Can you try with the default Arch Linux real-time kernel to check if this is irelevant of CachyOS patches?

Otherwise you probably need to ask in CachyOS support or something.

[LethalManBoob]

@LethalManBoob you might have a better support if you were using any of the Arch Linux kernels from the repos. Can you try with the default Arch Linux real-time kernel to check if this is irelevant of CachyOS patches?

Otherwise you probably need to ask in CachyOS support or something.

It can build on the base aur linux-rt but not cachyos-rt

[inglor]

@LethalManBoob check with the maintainers of the cachyos-rt - probably one of their patches is breaking this.

[cyring]

@LethalManBoob
Have a look to these previous solved issues:

• Failure to build dkms modules
• DKMS compilations fails on 6.3

[ptr1337]

@LethalManBoob check with the maintainers of the cachyos-rt - probably one of their patches is breaking this.

He should provide the log of the failed compilation.
Also we are running a 6.5.3 RT on not 6.3. Not sure if this makes a difference, but we need a log.

Edit:
Also the RT Kernel does not differ much from the default "linux-cachyos". Only the recent RT patchset is applied.

[csutcliff]

My experience is that it works fine with normal kernels (including linux-cachyos) and builds fine via DKMS for the LTO variants but as soon as I boot an LTO kernel with the corefreq module enabled I cannot even log in. SDDM launches but after entering my password I get about 20 seconds of black screen before being dumped back at SDDM. If I switch to another TTY and try to login to the console it hangs after I enter username and password, never proceeds to a shell prompt. As I can't login via gui or console when this happens I don't know how to debug or get logs.

If I disable the corefreq module the LTO kernels otherwise run fine.

Has anyone got any ideas how to debug further?

[gel-crabs]

I've been using thin LTO with CoreFreq for a long time with no issues, I'm currently on cachyos 6.6-rc1 built with Clang and thin LTO. I'm almost certain this is a bug which was reported previously. It is fixed by rebuilding your kernel with CONFIG_FORTIFY_SOURCE disabled.

See #422 (comment)

[ptr1337]

I've been using thin LTO with CoreFreq for a long time with no issues, I'm currently on cachyos 6.6-rc1 built with Clang and thin LTO. I'm almost certain this is a bug which was reported previously. It is fixed by rebuilding your kernel with CONFIG_FORTIFY_SOURCE disabled.

See #422 (comment)

This still seems not for me for a solution, to disable FORTIFY_SOURCE globally for our config, just because corefreq has issues with.
There should be further debugged, why FORTIFY_SOURCE in combination with clang is breaking it or FORTIFY_SOURCE should be completely disabled in the DKMS module, if clang is used.

Maybe reporting a bug to llvm/clang would be also worth to get some further information.
https://github.com/clangbuiltlinux/linux --> there should be quite easy to get some professional help for this issue, but not sure if they support out of tree modules.

Edit:
But using the GCC kernel should be also enough. The LTO Kernel is just some little extra, if people want to use it, but not our default.