From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1213] [Windows] BSOD when shutting down testpmd
Date: Fri, 07 Apr 2023 14:34:57 +0000 [thread overview]
Message-ID: <bug-1213-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1213
Bug ID: 1213
Summary: [Windows] BSOD when shutting down testpmd
Product: DPDK
Version: 22.11
Hardware: All
OS: Windows
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: a.pollenus@deltacast.tv
Target Milestone: ---
Hello,
When shutting down the testpmd command I get a BSOD (PROCESS_HAS_LOCKED_PAGES):
This testpmd allocate 40 queues RX and 40 queues TX. The total number of mbuf
is set to 7000000. This command is supposed to allocate +- 40GB of memory in
total for the 80 queues.
.\dpdk-testpmd.exe -l 1-5 -n 4 -a 0000:5e:00.0 -- --socket-num=0 --burst=16
--txd=1024 --rxd=1024 --mbcache=512 --txq=40 --rxq=40 --nb-cores=4
--txpkts=1500 -i --forward-mode=flowgen --eth-peer=0,01:00:5e:00:00:05
--tx-ip=10.10.1.14,239.0.0.5 --tx-udp=42500,42500 --total-num-mbuf=7000000
This testpmd command is working properly until you call quit in the interactive
command line. When the application shutdown the machine freeze and show a BSOD
(PROCESS_HAS_LOCKED_PAGES).
When analysing the minidump generated, we see that some page are found in the
process that have been terminated.
In the bellow comment you'll find the minidump analyze.
Could you try to reproduce it on your side ?
The problem doesn't seem to be linked to some out of memory issues. (The server
have a total of 384 GB of ram and should handle easily 40GB of allocation)
SETUP:
CPU : 2x Intel Xeon platinum 8268
RAM: 6x memory channel - 192GB on each numa
OS: Windows Server 2022 21H2
NIC: Intel E810 100G Dual port
DPDK version: 22.11
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3728 bytes --]
reply other threads:[~2023-04-07 14:34 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-1213-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).