https://bugs.dpdk.org/show_bug.cgi?id=687
Bug ID: 687
Summary: [dpdk-21.05] unit_tests_power/power_cpufreq: unit test
failed
Product: DPDK
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: zhiminx.hu...@intel.com
Target Milestone: ---
ENV:
DPDK version:
dpdk-21.05-rc1: 1b593b9c832e9b284cc59665fe662242a3fc1daf
OS: CentOS Stream release 8/4.18.0-277.el8.x86_64
Compiler: gcc version 8.4.1 20200928 (Red Hat 8.4.1-1) (GCC)
Hardware platform: Intel(R) Xeon(R) Gold 6139 CPU @ 2.30GHz
NIC hardware: Intel Corporation Ethernet Controller E810-C for QSFP [8086:1592]
CVL100Gx2
NIC firmware:
ice: 1.6.0_rc26_4_g2fb2c79e_dirty
firmware-version: 3.00 0x800071ff 1.2928.0
ICE OS Default Package version 1.3.26.0
Reproduced step:
1.
echo 2 > /sys/bus/pci/devices/0000\:81\:00.0/sriov_numvfs
2.
ip link set ens801f0 vf 0 trust on
3.
x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 1,2,3,4 -n 4 -a
0000:81:01.0,cap=dcf -a 0000:81:01.1 --file-prefix=dpdk_11923_20210423100520
-- -i
4.
flow validate 0 ingress pattern eth / ipv6 / udp / gtpu / ipv6 src is 2001::1 /
tcp dst is 23 / end actions vf id 1 / end
output:
RTE>>power_cpufreq_autotest
POWER: Env isn't set yet!
POWER: Attempting to initialise ACPI cpufreq power management...
POWER: Initialized successfully for lcore 2 power management
POWER: Power management governor of lcore 2 has been set back to successfully
POWER: Power management of lcore 2 has exited from 'userspace' mode and been
set back to the original
POWER: Lcore id 128 can not exceeds 127
POWER: Initialized successfully for lcore 2 power management
POWER: Power management of lcore 2 is in use
POWER: Invalid lcore ID
POWER: NULL buffer supplied
POWER: Buffer size is not enough
POWER: Invalid lcore ID
POWER: Power management governor of lcore 2 has been set back to successfully
POWER: Power management of lcore 2 has exited from 'userspace' mode and been
set back to the original
Test Failed
expected output:
RTE>>power_cpufreq_autotest
POWER: Env isn't set yet!
POWER: Attempting to initialise ACPI cpufreq power management...
POWER: Initialized successfully for lcore 2 power management
POWER: Power management governor of lcore 2 has been set back to successfully
POWER: Power management of lcore 2 has exited from 'userspace' mode and been
set back to the original
POWER: Lcore id 128 can not exceeds 127
POWER: Initialized successfully for lcore 2 power management
POWER: Power management of lcore 2 is in use
POWER: Invalid lcore ID
POWER: NULL buffer supplied
POWER: Buffer size is not enough
POWER: Invalid lcore ID
POWER: Invalid lcore ID
POWER: Invalid frequency index 64, which should be less than 15
POWER: Invalid frequency index 15, which should be less than 15
POWER: Invalid lcore ID
POWER: Invalid lcore ID
POWER: Invalid lcore ID
POWER: Invalid lcore ID
POWER: Invalid lcore ID
POWER: Invalid lcore ID
POWER: Power management governor of lcore 2 has been set back to successfully
POWER: Power management of lcore 2 has exited from 'userspace' mode and been
set back to the original
POWER: Power management of lcore 2 is not used
POWER: Lcore id 128 can not exceeds 127
Test OK
bad commit id: 606a234c6d3607c93a0426bdccdbf9aaa2b8e5f6
commit 606a234c6d3607c93a0426bdccdbf9aaa2b8e5f6 (refs/bisect/bad)
Author: Richael Zhuang <richael.zhu...@arm.com>
Date: Thu Apr 15 13:59:30 2021 +0800
test/power: round CPU frequency to check
The value in "/sys/.../cpuinfo_cur_freq" may not be exactly the
same as what was set. For example, if "2400000" is written to
"/sys/.../cpufreq/scaling_setspeed" to set the frequency, then the
value in "/sys/.../cpuinfo_cur_freq" may be "2401222". So need to
round the value.
Fixes: ed7c51a6a680 ("app/test: vm power management")
Cc: sta...@dpdk.org
Signed-off-by: Richael Zhuang <richael.zhu...@arm.com>
Reviewed-by: David Hunt <david.h...@intel.com>
diff --git a/app/test/test_power_cpufreq.c b/app/test/test_power_cpufreq.c
index d47b3e0a1a..f753d24ac5 100644
— a/app/test/test_power_cpufreq.c
+++ b/app/test/test_power_cpufreq.c
--
You are receiving this mail because:
You are the assignee for the bug.
