All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 795] [dpdk-19.11] unit_tests_power/power_cpufreq: unit test failed
Date: Thu, 26 Aug 2021 11:24:55 +0000	[thread overview]
Message-ID: <bug-795-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=795

            Bug ID: 795
           Summary: [dpdk-19.11] unit_tests_power/power_cpufreq: unit test
                    failed
           Product: DPDK
           Version: 19.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
DPDK version: Use make showversion or for a non-released version: git remote -v
&& git show-ref --heads
commit 179f2a3a8a56600a66e4e0830bbe993be67f9d7e (HEAD, tag: v19.11.10-rc1,
origin/19.11)
Author: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Date:   Wed Aug 18 16:45:29 2021 +0200    version: 19.11.10-rc1   
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
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 
NIC driver: ixgbe-5.10.2


Test Setup
Steps to reproduce
List the steps to reproduce the issue.

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.

APP: HPET is not enabled, using TSC as default timer
RTE>>power_cpufreq_autotest
POWER: Env isn't set yet!
POWER: Attempting to initialise ACPI cpufreq power management...
POWER: Power management governor of lcore 2 has been set to user space
successfully
POWER: Initialized successfully for lcore 2 power management
POWER: Power management governor of lcore 2 has been set back to ondemand
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: Power management governor of lcore 2 has been set to user space
successfully
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 ondemand
successfully
POWER: Power management of lcore 2 has exited from 'userspace' mode and been
set back to the original
Test Failed
RTE>>


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.

1, former bug [DPDK-26715] [dpdk-21.05] unit_tests_power/power_cpufreq: unit
test failed - IT JIRA (Supports IC/ITS Data) (intel.com):

the former part of the fixed patch(http://dpdk.org/patch/95860) has been merged
into LTS19.11.10-rc1. 

 2, the next related bug [DPDK-28772] [dpdk-20.11]
unit_tests_power/power_cpufreq: unit test failed - IT JIRA (Supports IC/ITS
Data) (intel.com)
apply its patch, also test failed. 

so need future debug.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2021-08-26 11:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 11:24 bugzilla [this message]
2021-12-15 11:11 ` [Bug 795] [dpdk-19.11] unit_tests_power/power_cpufreq: unit test failed bugzilla

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-795-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.