Re: turbostat-17.06.23 floating point exception

2018-10-18 Thread Solio Sarabia
On Fri, Oct 12, 2018 at 07:03:41PM -0400, Len Brown wrote: > > Why would the cpu topology report 0 cpus? I added a debug entry to > > cpu_usage_stat and /proc/stat showed it as an extra column. Then > > fscanf parsing in for_all_cpus() failed, causing the SIGFPE. > > > > This is not an issue. Tha

Re: turbostat-17.06.23 floating point exception

2018-10-12 Thread Len Brown
> Why would the cpu topology report 0 cpus? I added a debug entry to > cpu_usage_stat and /proc/stat showed it as an extra column. Then > fscanf parsing in for_all_cpus() failed, causing the SIGFPE. > > This is not an issue. Thanks. Yes, it is true that turbostat doesn't check for systems with 0

Re: turbostat-17.06.23 floating point exception

2018-10-12 Thread Solio Sarabia
On Fri, Oct 12, 2018 at 11:26:30AM -0700, Solio Sarabia wrote: > Hi -- > > turbostat 17.06.23 is throwing an exception on a custom linux-4.16.12 > kernel, on Xeon E5-2699 v4 Broadwell EP, 2S, 22C/S, 44C total, HT off, > VTx off. > > Initially the system had 4.4.0-137. Then I built and installed >