From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 790] [dpdk-20.11] unit_tests_power/power_cpufreq: unit test failed
Date: Fri, 13 Aug 2021 10:07:19 +0000 [thread overview]
Message-ID: <bug-790-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=790
Bug ID: 790
Summary: [dpdk-20.11] unit_tests_power/power_cpufreq: unit test
failed
Product: DPDK
Version: 20.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: yux.jiang@intel.com
Target Milestone: ---
Environment
A release candidate tarball can be found at:
https://dpdk.org/browse/dpdk-stable/tag/?id=v20.11.3-rc1
These patches are located at branch 20.11 of dpdk-stable repo:
https://dpdk.org/browse/dpdk-stable/
DPDK version: Use make showversion or for a non-released version: git remote -v
&& git show-ref --heads
dpdk-20.11.3-rc1: c5f4e9dd155a4c99e219a734315b899d4340d304
OS: Red Hat Enterprise Linux release 8.3/4.18.0-305.7.1.el8_4.x86_64
Compiler: gcc version 8.4.1 20200928 (Red Hat 8.4.1-1) (GCC)
Hardware platform: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
NIC hardware: 82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb(niantic)
NIC firmware: 0x000161bf
Test Setup:
1.
usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:81:00.0 0000:81:00.1
2.
x86_64-native-linuxapp-gcc/app/test/dpdk-test -l 1-71 -n 4 -- -i
3.
power_cpufreq_autotest
Show the output from the previous commands.
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 userspace
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 userspace
successfully
POWER: Power management of lcore 2 has exited from 'userspace' mode and been
set back to the original
Test Failed
Expected Result:
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
Regression
Is this issue a regression: (Y/N) Y
First bad commit id: commit 606a234c6, but which has been fixed in 21.08.
the former part of the fixed patch(http://dpdk.org/patch/95860) has been merged
into LTS20.11.3-rc1. Need future debug.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-08-13 10:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-790-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.