[dpdk-dev] Your Bugzilla bug list needs attention.

[dpdk-dev] Your Bugzilla bug list needs attention.

[bugzilla]

[This e-mail has been automatically generated.]

You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://dpdk.space:8000/) that require
attention.

All of these bugs are in the CONFIRMED
state, and have not been touched in 7 days or more.
You need to take a look at them, and decide on an initial action.

Generally, this means one of three things:

(1) You decide this bug is really quick to deal with (like, it's INVALID),
    and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to
    someone else. (Hint: if you don't know who to reassign it to, make
    sure that the Component field seems reasonable, and then use the
    "Reset Assignee to default" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
    Accept the bug by setting the status to IN_PROGRESS.

To get a list of all CONFIRMED bugs, you can use this URL (bookmark
it if you like!):
http://dpdk.space:8000/buglist.cgi?bug_status=CONFIRMED&assigned_to=dev@dpdk.org

Or, you can use the general query page, at 
http://dpdk.space:8000/query.cgi

Appended below are the individual URLs to get to all of your CONFIRMED bugs
that haven't been touched for 7 days or more.

You will get this message once a day until you've dealt with these bugs!

 Green goal: power efficiency with all hardwares
    -> http://dpdk.space:8000/show_bug.cgi?id=1
 dpdk-pdump leads to ovs-vswitchd crash
    -> http://dpdk.space:8000/show_bug.cgi?id=6
 Kernel crash after "Detected Tx Unit Hang" report
    -> http://dpdk.space:8000/show_bug.cgi?id=15
 Does not cross-compile: buildtools/check-experimental-syms.sh assumes `objdump`
    -> http://dpdk.space:8000/show_bug.cgi?id=32
 "rte_eth_tx_queue_setup" will be failed if argument "tx_conf" not specified
    -> http://dpdk.space:8000/show_bug.cgi?id=43
 Reciprocal division: Fail [Crash]
    -> http://dpdk.space:8000/show_bug.cgi?id=46
 For RSS flow actions, e1000_ethdev.h uses IGB_MAX_RX_QUEUE_NUM instead of IGB_MAX_RX_QUEUE_NUM_82576
    -> http://dpdk.space:8000/show_bug.cgi?id=83
 rte_memcpy() moves data incorrectly on Ubuntu 18.04 on Intel Skylake
    -> http://dpdk.space:8000/show_bug.cgi?id=97
 axgbe driver does not support 1G Copper 1000BASE-T SFPs (Unsupported AN_CL37)
    -> http://dpdk.space:8000/show_bug.cgi?id=99
 Cannot create crypto_openssl after vdev_uninit
    -> http://dpdk.space:8000/show_bug.cgi?id=105
 pktgen -s option send pcap traffic once
    -> http://dpdk.space:8000/show_bug.cgi?id=113
 rte_rand() is not thread-safe but not documented as such
    -> http://dpdk.space:8000/show_bug.cgi?id=114
 conflicting information for 'Running DPDK Applications Without Root Privileges'
    -> http://dpdk.space:8000/show_bug.cgi?id=118
 configure rx queue for JUMBO frame returns warning as offload is 0x0, but eth_pcap_rx_jumbo is present
    -> http://dpdk.space:8000/show_bug.cgi?id=164
 DPDK on Azure using `intel-go/nff-go` fails using `hv_netvsc` driver
    -> http://dpdk.space:8000/show_bug.cgi?id=175
 secondary process cannot execute  iommu
    -> http://dpdk.space:8000/show_bug.cgi?id=176
 Problem using cloned rte_mbuf buffers with KNI interface
    -> http://dpdk.space:8000/show_bug.cgi?id=183
 PVP zero-loss performance degradation without --legacy-mem
    -> http://dpdk.space:8000/show_bug.cgi?id=185
 Merge linux and bsd eal_thread.c which are same
    -> http://dpdk.space:8000/show_bug.cgi?id=187
 ethdev API for firmware version request is not tested
    -> http://dpdk.space:8000/show_bug.cgi?id=225
 Flow control mode on mac Intel Corporation I350 Gigabit Network Connection (rev 01) issues
    -> http://dpdk.space:8000/show_bug.cgi?id=227
 Running test-build.sh Fails on ppc_64 fails due to hard-coded requirement for IXGBE_PMD in examples/vm_power_manager
    -> http://dpdk.space:8000/show_bug.cgi?id=237
 [tree-wide] enhance getopt_long usage
    -> http://dpdk.space:8000/show_bug.cgi?id=238
 ipsec-secgw fails to initialize when librte_ipsec is enabled
    -> http://dpdk.space:8000/show_bug.cgi?id=239
 QEMU (vIOMMU+virtio) crashes when DPDK exits
    -> http://dpdk.space:8000/show_bug.cgi?id=241
 Unable to run DPDK test with "make test" command
    -> http://dpdk.space:8000/show_bug.cgi?id=253
 Tap driver unnecessarily triggers timeout on failure
    -> http://dpdk.space:8000/show_bug.cgi?id=258
 Unaligned memory access when reading ipv6 header
    -> http://dpdk.space:8000/show_bug.cgi?id=279
 X710 PF Reset Issue with DPDK VF Driver
    -> http://dpdk.space:8000/show_bug.cgi?id=280
 Fix missing headers in FreeBSD CURRENT build
    -> http://dpdk.space:8000/show_bug.cgi?id=282
 BPF: array ins_chk is missing an entry
    -> http://dpdk.space:8000/show_bug.cgi?id=283
 netvsc PMD/dpdk/azure: Driver lockup with multi-queue configuration
    -> http://dpdk.space:8000/show_bug.cgi?id=287
 Target name recorded wrong when try to build dpdk with x86_64-native-linux-gcc
    -> http://dpdk.space:8000/show_bug.cgi?id=288
 mlx5: 100G interface capability not recognized
    -> http://dpdk.space:8000/show_bug.cgi?id=289
 FM10K dpdk driver - memory leak with KNI interface - interface up/down
    -> http://dpdk.space:8000/show_bug.cgi?id=291

[dpdk-dev] Your Bugzilla bug list needs attention.

[bugzilla]

[This e-mail has been automatically generated.]

You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://dpdk.org/tracker/) that require
attention.

All of these bugs are in the CONFIRMED
state, and have not been touched in 7 days or more.
You need to take a look at them, and decide on an initial action.

Generally, this means one of three things:

(1) You decide this bug is really quick to deal with (like, it's INVALID),
    and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to
    someone else. (Hint: if you don't know who to reassign it to, make
    sure that the Component field seems reasonable, and then use the
    "Reset Assignee to default" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
    Accept the bug by setting the status to IN_PROGRESS.

To get a list of all CONFIRMED bugs, you can use this URL (bookmark
it if you like!):
http://dpdk.org/tracker/buglist.cgi?bug_status=CONFIRMED&assigned_to=dev@dpdk.org

Or, you can use the general query page, at 
http://dpdk.org/tracker/query.cgi

Appended below are the individual URLs to get to all of your CONFIRMED bugs
that haven't been touched for 7 days or more.

You will get this message once a day until you've dealt with these bugs!

 Green goal: power efficiency with all hardwares
    -> http://dpdk.org/tracker/show_bug.cgi?id=1