On 18 August 2017 at 11:52, Dai Xiang <xiangx....@intel.com> wrote: > Cool, after use this kernel_cmdline, 4\5\6\8 can pass now, but 1\7\9 still > can not:
Why do you say that 4/5/6/8 have passed ? > cpufreq_01.0/cpu0: checking 'scaling_available_frequencies' exists in > '/sys/devices/system/cpu/cpu0/cpufreq'... Err > cpufreq_01.0/cpu1: checking 'scaling_available_frequencies' exists in > '/sys/devices/system/cpu/cpu1/cpufreq'... Err > cpufreq_01.0/cpu2: checking 'scaling_available_frequencies' exists in > '/sys/devices/system/cpu/cpu2/cpufreq'... Err > cpufreq_01.0/cpu3: checking 'scaling_available_frequencies' exists in > '/sys/devices/system/cpu/cpu3/cpufreq'... Err > cpufreq_01.0/cpu4: checking 'scaling_available_frequencies' exists in > '/sys/devices/system/cpu/cpu4/cpufreq'... Err > cpufreq_01.0/cpu5: checking 'scaling_available_frequencies' exists in > '/sys/devices/system/cpu/cpu5/cpufreq'... Err > cpufreq_01.0/cpu6: checking 'scaling_available_frequencies' exists in > '/sys/devices/system/cpu/cpu6/cpufreq'... Err > cpufreq_01.0/cpu7: checking 'scaling_available_frequencies' exists in > '/sys/devices/system/cpu/cpu7/cpufreq'... Err > > cpufreq_01: fail > > cpufreq_07.0/cpu0: can not reach a quescient point for 'ondemand'... > skip > cpufreq_07.0/cpu1: can not reach a quescient point for 'ondemand'... > skip > cpufreq_07.0/cpu2: can not reach a quescient point for 'ondemand'... > skip > cpufreq_07.0/cpu3: can not reach a quescient point for 'ondemand'... > skip > cpufreq_07.0/cpu4: can not reach a quescient point for 'ondemand'... > skip > IPMI BMC is not supported on this machine, skip bmc-watchdog setup! > cpufreq_07.0/cpu5: can not reach a quescient point for 'ondemand'... > skip > cpufreq_07.0/cpu6: can not reach a quescient point for 'ondemand'... > skip > cpufreq_07.0/cpu7: can not reach a quescient point for 'ondemand'... > skip > > cpufreq_07: skip > > cpufreq_09.0/cpu0: checking 'powersave' sets frequency to 1600000 KHz... > Err > cpufreq_09.1/cpu0: checking 'powersave' frequency 1600000 KHz is fixed... > Err > cpufreq_09.0/cpu1: checking 'powersave' sets frequency to 1600000 KHz... > Err > cpufreq_09.1/cpu1: checking 'powersave' frequency 1600000 KHz is fixed... > Err > cpufreq_09.0/cpu2: checking 'powersave' sets frequency to 1600000 KHz... > Err > cpufreq_09.1/cpu2: checking 'powersave' frequency 1600000 KHz is fixed... > Err > cpufreq_09.0/cpu3: checking 'powersave' sets frequency to 1600000 KHz... > Err > cpufreq_09.1/cpu3: checking 'powersave' frequency 1600000 KHz is fixed... > Err > cpufreq_09.0/cpu4: checking 'powersave' sets frequency to 1600000 KHz... > Err > cpufreq_09.1/cpu4: checking 'powersave' frequency 1600000 KHz is fixed... > Err > cpufreq_09.0/cpu5: checking 'powersave' sets frequency to 1600000 KHz... > Err > cpufreq_09.1/cpu5: checking 'powersave' frequency 1600000 KHz is fixed... > Err > cpufreq_09.0/cpu6: checking 'powersave' sets frequency to 1600000 KHz... > Err > cpufreq_09.1/cpu6: checking 'powersave' frequency 1600000 KHz is fixed... > Err > cpufreq_09.0/cpu7: checking 'powersave' sets frequency to 1600000 KHz... > Err > cpufreq_09.1/cpu7: checking 'powersave' frequency 1600000 KHz is fixed... > Err I can see all of them fail and the reason is quite simple to see. Even intel-pstate doesn't provide a frequency table and so whatsoever depends on a frequency table will fail. These tests aren't really meant for x86 stuff, sorry about that :( -- viresh _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
