Bug 1201
Summary: | virt2phys is sometimes causing bluescreen | ||
---|---|---|---|
Product: | DPDK | Reporter: | Antoine Pollenus (a.pollenus) |
Component: | other | Assignee: | Tyler Retzlaff (roretzla) |
Status: | CONFIRMED --- | ||
Severity: | critical | CC: | a.pollenus, dmitry.kozliuk, e.houet, ming3.li, roretzla |
Priority: | High | ||
Version: | 22.11 | ||
Target Milestone: | --- | ||
Hardware: | x86 | ||
OS: | Windows | ||
Attachments: | bluescreen |
Description
Antoine Pollenus
2023-03-28 15:24:11 CEST
The crash happen with intel nics. Tested with XXV710-DA2 and E810-C The crash is reproduced easily with the command: dpdk-testpmd.exe -l 0-3 -n 4 -- -i --portmask=0x1 --nb-cores=2 sometimes the issue happen at the first launch sometimes you need few launch/stop of testpmd to get it. The issue seems to appear during the rte_eal_init. Dmitry Kozlyuk, any chance that this behaviour is due to the Windows Server 2019 limitations you mentionned in this message? https://www.mail-archive.com/dev@dpdk.org/msg169768.html > Testing revealed Windows Server 2019 does not allow allocating hugepage > memory at a reserved address, despite advertised API. So allocator has > to temporary free the region to be allocated. This creates in inherent > race condition. This issue is being discussed with Microsoft privately. If it is the case, did you receive support from Microsoft to solve this issue? Or do you know any workaround? Thank you! Marking as confirmed, because I too have seen this crash before and even analyzed a similar crash dump but with no insight why this might happen. Eric Houet, this crash is unrelated to the limitation. I'm going to post a patch to remove it, because it's really bogus but at least one user has hit it. Few months back, Mark Cheatham hit some "memory check failure" in virt2phys. I'm unsure if it was the same bug. He "was able to workaround it by changing line 307 in virt2phys_logic.c from: if (info.AllocationBase != virt || info.RegionSize != size) { to: if (info.AllocationBase != virt || info.RegionSize < size) {". Can you try this? If it helps, we can probably ask Microsoft experts for help explaining this behavior. This little patch you sent us is not fixing the BSOD. Hello Dmitry, Do you know how we could progress on this issue? Hello Antoine, please check if this patch solves the issue: http://patchwork.dpdk.org/project/dpdk/patch/20230912111759.1502806-1-ming3.li@intel.com/ Hi Dmitry, thank you for the help on that issue. I'll take a look at that as soon as I can, certainly this week or next week. |