CyrIng

Issue is present with all tracers using /proc/kallsyms powertop perf trace

Es ist das problem Nicht unsolved yet 😟

Excluding PowerTop, are you getting the same issue when entering: cat /proc/kallsyms

Hello, See Wiki for CoreFreq as the Clock Source, CPU Freq and CPU Idle driver 64 settings can be made permanent as the driver arguments. You can list them with: modinfo corefreqk.ko parm: ArchID:Force an architecture (ID) (int) parm: AutoClock:Estimate Clock Frequency 0:Spec; 1:Once; 2:Auto (int) parm: SleepInterval:Timer interval (ms) (uint) parm: TickInterval:System requested interval (ms) (uint) parm: Experimental:Enable features under development (int) parm: CPU_Count:-1:Kernel(default); 0:Hardware; >0: User value (int) parm: Target_Ratio_Unlock:1:Target Ratio Unlock; 0:Lock (short) parm: Clock_Ratio_Unlock:1:MinRatio; 2:MaxRatio; 3:Both Unlock (short) parm: Turbo_Ratio_Unlock:1:Turbo Ratio Unlock; 0:Lock (short) parm: Uncore_Ratio_Unlock:1:Uncore Ratio Unlock; 0:Lock (short) parm: ServiceProcessor:Select a CPU to run services with (int) parm: RDPMC_Enable:Enable RDPMC bit in CR4 register (ushort) parm: NMI_Disable:Disable the NMI Handler (ushort) parm: Override_SubCstate:Override Sub C-States (array of ushort) parm: PkgCStateLimit:Package C-State Limit (short) parm: IOMWAIT_Enable:I/O MWAIT Redirection Enable (short) parm: CStateIORedir:Power Mgmt IO Redirection C-State (short) parm: Config_TDP_Level:Config TDP Control Level (short) parm: Custom_TDP_Offset:TDP Limit Offset (watt) (array of short) parm: Activate_TDP_Limit:Activate TDP Limiting (array of short) parm: Activate_TDP_Clamp:Activate TDP Clamping (array of short) parm: Custom_TDC_Offset:TDC Limit Offset (amp) (short) parm: Activate_TDC_Limit:Activate TDC Limiting (short) parm: L1_HW_PREFETCH_Disable:Disable L1 HW Prefetcher (short) parm: L1_HW_IP_PREFETCH_Disable:Disable L1 HW IP Prefetcher (short) parm: L2_HW_PREFETCH_Disable:Disable L2 HW Prefetcher (short) parm: L2_HW_CL_PREFETCH_Disable:Disable L2 HW CL Prefetcher (short) parm: SpeedStep_Enable:Enable SpeedStep (short) parm: C1E_Enable:Enable SpeedStep C1E (short) parm: TurboBoost_Enable:Enable Turbo Boost (short) parm: C3A_Enable:Enable C3 Auto Demotion (short) parm: C1A_Enable:Enable C3 Auto Demotion (short) parm: C3U_Enable:Enable C3 UnDemotion (short) parm: C1U_Enable:Enable C1 UnDemotion (short) parm: CC6_Enable:Enable Core C6 State (short) parm: PC6_Enable:Enable Package C6 State (short) parm: ODCM_Enable:Enable On-Demand Clock Modulation (short) parm: ODCM_DutyCycle:ODCM DutyCycle [0-7] | [0-14] (short) parm: PowerMGMT_Unlock:Unlock Power Management (short) parm: PowerPolicy:Power Policy Preference [0-15] (short) parm: Turbo_Activation_Ratio:Turbo Activation Ratio (short) parm: PState_FID:P-State Frequency Id (int) parm: PState_VID:P-State Voltage Id (int) parm: HWP_Enable:Hardware-Controlled Performance States (short) parm: HWP_EPP:Energy Performance Preference (short) parm: HDC_Enable:Hardware Duty Cycling (short) parm: EEO_Disable:Disable Energy Efficiency Optimization (short) parm: R2H_Disable:Disable Race to Halt (short) parm: Clear_Events:Clear Thermal and Power Events (uint) parm: ThermalScope:[0:None; 1:SMT; 2:Core; 3:Package] (int) parm: VoltageScope:[0:None; 1:SMT; 2:Core; 3:Package] (int) parm: PowerScope:[0:None; 1:SMT; 2:Core; 3:Package] (int) parm: Register_CPU_Idle:Register the Kernel cpuidle driver (short) parm: Register_CPU_Freq:Register the Kernel cpufreq driver (short) parm: Register_Governor:Register the Kernel governor (short) parm: Register_ClockSource:Register Clock Source driver (short) parm: Idle_Route:[0:Default; 1:I/O; 2:HALT; 3:MWAIT] (short) parm: Mech_IBRS:Mitigation Mechanism IBRS (short) parm: Mech_STIBP:Mitigation Mechanism STIBP (short) parm: Mech_SSBD:Mitigation Mechanism SSBD (short) parm: Mech_IBPB:Mitigation Mechanism IBPB (short) parm: Mech_L1D_FLUSH:Mitigation Mechanism Cache L1D Flush (short) parm: Mech_PSFD:Mitigation Mechanism PSFD (short) parm: WDT_Enable:Watchdog Hardware Timer (short)

i5-11400 added into CPU-support Danke

@sg400maestro Really nice, thank you. I will cleanup your credentials within the Terminal title before posting.

@sg400maestro as a template you can see this recents addition to post your screenshots and CLI outputs @ich777 thank you for your explanations, my deutsch is no more as it's best

The relative frequency is computed from the processor performance counters. Those are sampled over a period, default 1 second; the previous sample being substracted to the current, you are getting a relative frequency. Press [ ! ] to toggle the frequency mode: relative to absolute Hertz

Hello, Sorry to disturb you but found your screenshots with a i5-11400 driving CoreFreq. Do you mind to provide me more outputs which will be added into the CoreFreq wiki at CPU support ? I'm especially interested in your testings of the CoreFreq features which can be toggled on/off among windows: "Processor" ; "Technologies" ; "Power, Current & Thermal" ; "Performance Monitoring" ; "Memory Controller" For any help, thank you. CyrIng

@ich777 Hello Atom is fixed in 1.89.3 Other users are still using plugin with an outdated version of CoreFreq. I would suggest you won't autostart CoreFreq in the plugin, not even the driver, and let Users manage to start manually with a warning "Experimental" and a reference to the GitHub project to read first. What do you think about that ?

Hello What is your processor as listed by lscpu or /proc/cpuinfo ?

Thanks a lot for your reply. If feasible, you can boot my CoreFreq live ISO image at: cyring.fr Release is 1 89.3 Development is 1.90.0 Those images are ArchLinux based with ideal kernel boot options (see project Readme.md). CoreFreq build and startup are fully automated. Those ISOs are huge to download, about 1 GB. if your Processor is stable with those ISO then your Processor is supported by CoreFreq.

@vincentvriends Hello, Was it a hard crash, CPU frozen, or you were still able to reach a shell ? Because in your kernel log, beside this original successful startup message: CoreFreq(2:6): Processor [ 06_A5] Architecture [Comet Lake] SMT [8/8] I don't find the evidence of a Processor crash (usually, displayed with registers trapped and execution callflow) Version 1.88 is by the way outdated, I recommend you switch to the latest 1.89.3 version. See with the unRAID plugin author for availability. If CoreFreq is indeed the root cause, I will appreciate you create an issue with the necessary detail on my GitHub project at: github.com/cyring/CoreFreq/issues Best regards CyrIng

A fix for the Atom C2750 is awaiting for your testings: github.com/cyring/CoreFreq/issues/319#issuecomment-1024796833 @ich777 it might be a difficult for @rbronco21 to boot the ISO image or rebuild from branch. Could you create a dedicated unRAID plugin with this Avoton CoreFreq hot fix ? Thank you both for your returns, and helping me to provide that fix to the mainline code.

@ich777 It is warmly recommended to new CoreFreq users to have a look first for processor support (architecture CPUID) within the Wiki - CPU Support: github.com/cyring/CoreFreq/wiki If CPU architecture is not listed, you have to download and try the live ISO image before everything: github.com/cyring/CoreFreq/wiki/Live-CD Fyi, this image is fully automated to build and run CoreFreq with ArchLinux inside. User disks are not mounted to spare them from any crash. If image is starting nicely CoreFreq then you are go for the unRAID plugin. Your screenshots and Cli outputs will be warmly welcomed to complete the CPU Support list.

CoreFreq 1.89.1 released

Ctrl + p To screenshot current screen. The output file corefreq-xxxxxx can then be read with command less -R Alt + p To record everything as an ascii-cinema. Video duration can be set in Settings menu.

Hi, I'm the author of CoreFreq and not of that UNRAID plugin. Issues are to be opened on GitHub https://github.com/cyring/CoreFreq/issues CoreFreq must be first tested on your Server processors with my original source code. If you don't have a Linux development platform to build CoreFreq, I'm providing a live image to build and run as an all-in-one ISO. https://github.com/cyring/CoreFreq/wiki/Live-CD CyrIng

Hello, Apologies for that crash but this plugin is embedded an outdated version of CoreFreq. See with the UNRAID CoreFreq plugin author for a refresh. Vanilla CoreFreq project is developing fixes for Xeon families as soon as I am informed through GitHub issues: https://github.com/cyring/CoreFreq/issues Feel free to contact me through a fulfilled and detailed issue, titled will your processor brand string, and issue body filled with Markdown of kernel crash log, Daemon and Client outputs, like option "-s" It usually don't take me lot of time to find the source of the issue and to provide a fix on the development branch for your testings. Recently I have provided fixes for Server processors. You can first try the develop branch at: https://github.com/cyring/CoreFreq/tree/develop Regards CyrIng

Tested CPU are listed into wiki/cpu support. So far no AMD family 15h has contributed to the project.

Some Zen3 owners showed me CoreFreq is working fine. Which issue do you have ?

Hello Unraid, If you're facing some difficulties with Corefreq, feel free to ask me: github.com/cyring/CoreFreq/discussions CyrIng