Segmentation fault

[cyring]

Segmentation fault

[cyring]

Thanks to report this issue: I have not tested it w/ Skylake (blind coding upon specs)

What about the kernel driver module corefreqk.ko : does it start normally?
What about the daemon corefreqd ?

I would first to check both.

You can run daemon in debug mode with option '-d'. This will print the info of the detected processor, transmitted from driver to the daemon

[cyring]

The general info of i7-6820HQ that CoreFreq should report the same:

http://www.cpu-world.com/CPUs/Core_i7/Intel-Core%20i7-6820HQ%20Mobile%20processor.html

[cyring]

Does the client run without the UI, starting it with cstates option ?

corefreq-cli -c

[cyring]

bigfreak85: I miss your full issue description but I read:
"seems to be a problem when qemu domain is running (win10 vm). If no Guest is Running the App doesnt crash..."

Are you running CoreFreq in a virtualized environment ?

If true, you can't because CoreFreq is a low level code running in processor ring 0

[bigfreak85]

Hi,

No! im running corefreq on the Local Machine not in the VM.
no difference whether qemu runs or not (VM powerd on or off) That's why i deleted the Comment.

I will Answer one by one:

1. Yes the Kerneldriver starts normally.
2. The Daemon also starts normally. When i start with -d flag set it give me the following output:
   root@t460p /home/bigfreak > corefreqd -d
   SysGate(1)
   CoreFreq Daemon. Copyright (C) 2015-2017 CYRIL INGENIERIE

Processor [Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz]
Architecture [Skylake/S] 8/8 CPU Online.
SleepInterval(1000), SysGate(1)

CPU #000 @ 2712.03 MHz
CPU #001 @ 2712.57 MHz
CPU #002 @ 2712.62 MHz
CPU #003 @ 2712.57 MHz
CPU #004 @ 2712.75 MHz
CPU #005 @ 2712.61 MHz
CPU #006 @ 2712.74 MHz
CPU #007 @ 2712.76 MHz
Thread [7fb87bf1e700] Init CPU 004
Thread [7fb87c71f700] Init CPU 003
Thread [7fb87cf20700] Init CPU 002
Thread [7fb87a71b700] Init CPU 007
Thread [7fb87af1c700] Init CPU 006
Thread [7fb87b71d700] Init CPU 005
Thread [7fb87df22700] Init CPU 000
Thread [7fb87d721700] Init CPU 001

3.Yes the Client starts with -c Flag and doesnt crash (10 Minutes runtime). After that knowledge i tried corefreq-cli without -c Flag in different terminals (xterm,urxvt,st) same problem appeared

[cyring]

Thanks for this info.

Can you please :
1- compile the UI w/ debug
cc -g -Wall corefreq-cli.c -o corefreq-cli -lm -lrt
2- run it with gdb until crash
3- post the faulted source line of code

[bigfreak85]

1 https://fb.naeherwohnen.de/index.php/ASZ/
2 done
3 https://fb.naeherwohnen.de/index.php/kodWq/

[cyring]

Btw, in your kernel cmd line, have you blacklisted nmi_watchdog with
'nmi_watchdog=0'

It is a requirement because nmi_watchdog use the same msr counters as CoreFreq read.

Without blacklist, the values are unexpected and can lead the UI out of buffer.

[bigfreak85]

Nope

root@t460p /boot/loader/entries > cat arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=PARTUUID=c8fae5ff-b11d-451d-8c10-58f8fde3b7f6 rw quiet splash

[bigfreak85]

have blacklisted
options root=PARTUUID=c8fae5ff-b11d-451d-8c10-58f8fde3b7f6 nmi_watchdog=0 rw quiet splash

after that it works :-D

cat /proc/sys/kernel/nmi_watchdog
0

[cyring]

Cool. :)

Please show me some screenshots of your running UI w/ load on 1 core 8-)

Check also you don't have system side effects (startup, suspend/resume, shutdown) while nmi_watchdog is blacklisted.

If you like CoreFreq, just vote for it in AUR

Thks

(I let you close this issue)

[bigfreak85]

here it comes :-D

https://fb.naeherwohnen.de/index.php/Jbz/

Edited: nicer Version with correct Size

[cyring]

Topology looks ok (Caches, Cores) in count & size
Ratios are good but it should top to x36
x8 is overwriting the header line: I need to improve this.
Architecture name sounds not correct ?
BCLK estimation is closed to factory value.