From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 660E042822; Tue, 28 Mar 2023 15:24:13 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 03EFB40EDF; Tue, 28 Mar 2023 15:24:13 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 82BE040156 for ; Tue, 28 Mar 2023 15:24:11 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 6529342857; Tue, 28 Mar 2023 15:24:11 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [Bug 1201] virtphys sometimes causing bluescreen Date: Tue, 28 Mar 2023 13:24:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: other X-Bugzilla-Version: 22.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: a.pollenus@deltacast.tv X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: Content-Type: multipart/alternative; boundary=16800098510.FaE2C7bD.2846164 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --16800098510.FaE2C7bD.2846164 Date: Tue, 28 Mar 2023 15:24:11 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All https://bugs.dpdk.org/show_bug.cgi?id=3D1201 Bug ID: 1201 Summary: virtphys sometimes causing bluescreen Product: DPDK Version: 22.11 Hardware: x86 OS: Windows Status: UNCONFIRMED Severity: critical Priority: Normal Component: other Assignee: dev@dpdk.org Reporter: a.pollenus@deltacast.tv Target Milestone: --- Created attachment 247 --> https://bugs.dpdk.org/attachment.cgi?id=3D247&action=3Dedit bluescreen When using DPDK on windows server 2019 sometimes we get a bluescreen. This bluescreen seams to be caused by virt2phys.sys The issue has only been reproduced on Windows server 2019. On windows 10,11 and server 2022 no bluescreen. To reproduce this issue only test-pmd is necessary. Bellow the crash analyse: Microsoft (R) Windows Debugger Version 10.0.22621.755 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\ja\Desktop\BSOD VCS\MEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address sp= ace may not be available. WARNING: Whitespace at start of path element ************* Path validation summary ************** Response Time (ms) Location Deferred .sympath cache*C:\MySymbols Deferred=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 srv*https://msdl.microsoft.com/download/symbols WARNING: Whitespace at start of path element Symbol search path is: .sympath cache*C:\MySymbols;srv*https://msdl.microsoft.com/download/symbols; C:\local\github\dpdk-kmods\windows\virt2phys\x64\Release Executable search path is:=20 WARNING: Whitespace at start of path element Windows 10 Kernel Version 17763 MP (8 procs) Free x64 Product: Server, suite: TerminalServer SingleUserTS Edition build lab: 17763.1.amd64fre.rs5_release.180914-1434 Machine Name: Kernel base =3D 0xfffff803`07eba000 PsLoadedModuleList =3D 0xfffff803`082d2= 4d0 Debug session time: Fri Mar 24 13:59:11.850 2023 (UTC + 1:00) System Uptime: 0 days 0:04:38.551 Loading Kernel Symbols .............................................................Page 197e55 not present in the dump file. Type ".hh dbgerr004" for details .. ................................................................ .............................. Loading User Symbols PEB is paged out (Peb.Ldr =3D 000000cd`0513b018). Type ".hh dbgerr001" for details Loading unloaded module list ........ For analysis of this file, run !analyze -v 0: kd> !analyze -v ***************************************************************************= **** * = * * Bugcheck Analysis = * * = * ***************************************************************************= **** SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the BugCheck Arg2: fffff8030afe2542, Address of the instruction which caused the BugCheck Arg3: ffffce0bfaf2e3f0, Address of the context record for the exception that caused the BugCheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2280 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 14939 Key : Analysis.Init.CPU.mSec Value: 4796 Key : Analysis.Init.Elapsed.mSec Value: 85415 Key : Analysis.Memory.CommitPeak.Mb Value: 126 Key : WER.OS.Branch Value: rs5_release Key : WER.OS.Timestamp Value: 2018-09-14T14:34:00Z Key : WER.OS.Version Value: 10.0.17763.1 FILE_IN_CAB: MEMORY.DMP BUGCHECK_CODE: 3b BUGCHECK_P1: c0000005 BUGCHECK_P2: fffff8030afe2542 BUGCHECK_P3: ffffce0bfaf2e3f0 BUGCHECK_P4: 0 CONTEXT: ffffce0bfaf2e3f0 -- (.cxr 0xffffce0bfaf2e3f0) rax=3Dffffe78772ee6000 rbx=3Da787ff756b60cddd rcx=3Da787ff756b60cde5 rdx=3Dffffce0bfaf2f300 rsi=3D000001f55b600000 rdi=3Dffffe7876c3cde20 rip=3Dfffff8030afe2542 rsp=3Dffffce0bfaf2ede0 rbp=3D00000000000001d4 r8=3D0000000000000000 r9=3D7fffe787726cafd8 r10=3D7ffffffffffffffc r11=3Dffffe78771bd6080 r12=3Dffffe78772282080 r13=3Dffffe7876ad78940 r14=3D0000000000200000 r15=3D000001f55b600000 iopl=3D0 nv up ei ng nz na pe nc cs=3D0010 ss=3D0018 ds=3D002b es=3D002b fs=3D0053 gs=3D002b = efl=3D00010282 virt2phys!virt2phys_process_find_block+0xa [inlined in virt2phys!virt2phys_translate+0xd2]: fffff803`0afe2542 488b03 mov rax,qword ptr [rbx] ds:002b:a787ff75`6b60cddd=3D???????????????? Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXPNP: 1 (!blackboxpnp) PROCESS_NAME: vcs.exe STACK_TEXT:=20=20 ffffce0b`faf2ede0 fffff803`0afe15c6 : 00001878`8e199398 ffffce0b`faf2ee= b9 ffffe787`71e66c60 00001878`8e199398 : virt2phys!virt2phys_translate+0xd2 [C:\local\github\dpdk-kmods\windows\virt2phys\virt2phys_logic.c @ 369]=20 ffffce0b`faf2ee80 fffff80e`a28276fb : ffffe787`6f7fc4a0 00000000`000000= 00 00000000`00000000 00001878`952876b8 : virt2phys!virt2phys_device_EvtIoInCallerContext+0x1c6 [C:\local\github\dpdk-kmods\windows\virt2phys\virt2phys.c @ 225]=20 ffffce0b`faf2ef20 fffff80e`a282704d : ffffe787`6f7fc4a0 ffffe787`729ebb= 60 00000000`00000000 00000000`00000001 : Wdf01000!FxPkgIo::DispatchStep1+0x69b [minkernel\wdf\framework\shared\irphandlers\io\fxpkgio.cpp @ 324]=20 ffffce0b`faf2efe0 fffff80e`a2821b73 : ffffe787`729ebb60 ffffe787`742d38= 10 00000000`00000000 fffff803`07f26c16 : Wdf01000!FxPkgIo::Dispatch+0x5d [minkernel\wdf\framework\shared\irphandlers\io\fxpkgio.cpp @ 119]=20 ffffce0b`faf2f040 fffff803`07ee6d19 : ffffe787`742d3810 00000000`000000= 01 00000000`00000000 00000000`00000002 : Wdf01000!FxDevice::DispatchWithLock+0= x113 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1430]=20 ffffce0b`faf2f0a0 fffff803`08493911 : ffffce0b`faf2f440 ffffe787`729ebb= 60 00000000`00000001 ffffe787`742d3810 : nt!IofCallDriver+0x59 ffffce0b`faf2f0e0 fffff803`08493681 : ffffe787`00000005 ffffe787`742d38= 10 ffffce0b`20206f49 ffffce0b`faf2f440 : nt!IopSynchronousServiceTail+0x1b1 ffffce0b`faf2f190 fffff803`08493746 : ffffe787`71bd6080 00000000`000000= 00 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xe61 ffffce0b`faf2f2e0 fffff803`08085bf5 : ffffce0b`faf2f440 fffff803`085328= 6b 00000000`00000000 ffffe787`73efc700 : nt!NtDeviceIoControlFile+0x56 ffffce0b`faf2f350 00007ffa`8b450144 : 00000000`00000000 00000000`000000= 00 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25 000000cd`052fb568 00000000`00000000 : 00000000`00000000 00000000`000000= 00 00000000`00000000 00000000`00000000 : 0x00007ffa`8b450144 FAULTING_SOURCE_LINE:=20 C:\local\github\dpdk-kmods\windows\virt2phys\virt2phys_logic.c FAULTING_SOURCE_FILE:=20 C:\local\github\dpdk-kmods\windows\virt2phys\virt2phys_logic.c FAULTING_SOURCE_LINE_NUMBER: 369 FAULTING_SOURCE_CODE:=20=20 113: struct virt2phys_block *cur; 114:=20 115: for (node =3D process->blocks.Next; node !=3D NULL; node =3D node->Next) { 116: cur =3D CONTAINING_RECORD(node, struct virt2phys_bl= ock, next); > 117: if (cur->mdl->StartVa =3D=3D virt) 118: return cur; 119: } 120: return NULL; 121: } 122:=20 SYMBOL_NAME: virt2phys!virt2phys_translate+d2 MODULE_NAME: virt2phys IMAGE_NAME: virt2phys.sys STACK_COMMAND: .cxr 0xffffce0bfaf2e3f0 ; kb BUCKET_ID_FUNC_OFFSET: d2 FAILURE_BUCKET_ID: AV_virt2phys!virt2phys_translate OS_VERSION: 10.0.17763.1 BUILDLAB_STR: rs5_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {a5b3e3eb-f919-3986-0426-062d62e143e1} Followup: MachineOwner --------- --=20 You are receiving this mail because: You are the assignee for the bug.= --16800098510.FaE2C7bD.2846164 Date: Tue, 28 Mar 2023 15:24:11 +0200 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
Bug ID 1201
Summary virtphys sometimes causing bluescreen
Product DPDK
Version 22.11
Hardware x86
OS Windows
Status UNCONFIRMED
Severity critical
Priority Normal
Component other
Assignee dev@dpdk.org
Reporter a.pollenus@deltacast.tv
Target Milestone --- 

Created attac=
hment 247 [details]
bluescreen

When using DPDK on windows server 2019 sometimes we get a bluescreen.

This bluescreen seams to be caused by virt2phys.sys

The issue has only been reproduced on Windows server 2019.

On windows 10,11 and server 2022 no bluescreen.

To reproduce this issue only test-pmd is necessary.

Bellow the crash analyse:

Microsoft (R) Windows Debugger Version 10.0.22621.755 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\ja\Desktop\BSOD VCS\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address sp=
ace
may not be available.

WARNING: Whitespace at start of path element

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       .sympath cache*C:\MySymbols
Deferred=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
srv*https://msdl.mi=
crosoft.com/download/symbols
WARNING: Whitespace at start of path element
Symbol search path is: .sympath
cache*C:\MySymbols;srv*https://msdl.microsoft.com/download/symbols;
C:\local\github\dpdk-kmods\windows\virt2phys\x64\Release
Executable search path is:=20
WARNING: Whitespace at start of path element
Windows 10 Kernel Version 17763 MP (8 procs) Free x64
Product: Server, suite: TerminalServer SingleUserTS
Edition build lab: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base =3D 0xfffff803`07eba000 PsLoadedModuleList =3D 0xfffff803`082d2=
4d0
Debug session time: Fri Mar 24 13:59:11.850 2023 (UTC + 1:00)
System Uptime: 0 days 0:04:38.551
Loading Kernel Symbols
.............................................................Page 197e55 not
present in the dump file. Type ".hh dbgerr004" for details
..
................................................................
..............................
Loading User Symbols
PEB is paged out (Peb.Ldr =3D 000000cd`0513b018).  Type ".hh dbgerr001=
" for
details
Loading unloaded module list
........
For analysis of this file, run !analyze -v
0: kd> !analyze -v
***************************************************************************=
****
*                                                                          =
   *
*                        Bugcheck Analysis                                 =
   *
*                                                                          =
   *
***************************************************************************=
****

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff8030afe2542, Address of the instruction which caused the BugCheck
Arg3: ffffce0bfaf2e3f0, Address of the context record for the exception that
caused the BugCheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2280

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 14939

    Key  : Analysis.Init.CPU.mSec
    Value: 4796

    Key  : Analysis.Init.Elapsed.mSec
    Value: 85415

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 126

    Key  : WER.OS.Branch
    Value: rs5_release

    Key  : WER.OS.Timestamp
    Value: 2018-09-14T14:34:00Z

    Key  : WER.OS.Version
    Value: 10.0.17763.1


FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8030afe2542

BUGCHECK_P3: ffffce0bfaf2e3f0

BUGCHECK_P4: 0

CONTEXT:  ffffce0bfaf2e3f0 -- (.cxr 0xffffce0bfaf2e3f0)
rax=3Dffffe78772ee6000 rbx=3Da787ff756b60cddd rcx=3Da787ff756b60cde5
rdx=3Dffffce0bfaf2f300 rsi=3D000001f55b600000 rdi=3Dffffe7876c3cde20
rip=3Dfffff8030afe2542 rsp=3Dffffce0bfaf2ede0 rbp=3D00000000000001d4
 r8=3D0000000000000000  r9=3D7fffe787726cafd8 r10=3D7ffffffffffffffc
r11=3Dffffe78771bd6080 r12=3Dffffe78772282080 r13=3Dffffe7876ad78940
r14=3D0000000000200000 r15=3D000001f55b600000
iopl=3D0         nv up ei ng nz na pe nc
cs=3D0010  ss=3D0018  ds=3D002b  es=3D002b  fs=3D0053  gs=3D002b           =
  efl=3D00010282
virt2phys!virt2phys_process_find_block+0xa [inlined in
virt2phys!virt2phys_translate+0xd2]:
fffff803`0afe2542 488b03          mov     rax,qword ptr [rbx]
ds:002b:a787ff75`6b60cddd=3D????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


PROCESS_NAME:  vcs.exe

STACK_TEXT:=20=20
ffffce0b`faf2ede0 fffff803`0afe15c6     : 00001878`8e199398 ffffce0b`faf2ee=
b9
ffffe787`71e66c60 00001878`8e199398 : virt2phys!virt2phys_translate+0xd2
[C:\local\github\dpdk-kmods\windows\virt2phys\virt2phys_logic.c @ 369]=
=20
ffffce0b`faf2ee80 fffff80e`a28276fb     : ffffe787`6f7fc4a0 00000000`000000=
00
00000000`00000000 00001878`952876b8 :
virt2phys!virt2phys_device_EvtIoInCallerContext+0x1c6
[C:\local\github\dpdk-kmods\windows\virt2phys\virt2phys.c @ 225]=20
ffffce0b`faf2ef20 fffff80e`a282704d     : ffffe787`6f7fc4a0 ffffe787`729ebb=
60
00000000`00000000 00000000`00000001 : Wdf01000!FxPkgIo::DispatchStep1+0x69b
[minkernel\wdf\framework\shared\irphandlers\io\fxpkgio.cpp @ 324]=20
ffffce0b`faf2efe0 fffff80e`a2821b73     : ffffe787`729ebb60 ffffe787`742d38=
10
00000000`00000000 fffff803`07f26c16 : Wdf01000!FxPkgIo::Dispatch+0x5d
[minkernel\wdf\framework\shared\irphandlers\io\fxpkgio.cpp @ 119]=20
ffffce0b`faf2f040 fffff803`07ee6d19     : ffffe787`742d3810 00000000`000000=
01
00000000`00000000 00000000`00000002 : Wdf01000!FxDevice::DispatchWithLock+0=
x113
[minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1430]=20
ffffce0b`faf2f0a0 fffff803`08493911     : ffffce0b`faf2f440 ffffe787`729ebb=
60
00000000`00000001 ffffe787`742d3810 : nt!IofCallDriver+0x59
ffffce0b`faf2f0e0 fffff803`08493681     : ffffe787`00000005 ffffe787`742d38=
10
ffffce0b`20206f49 ffffce0b`faf2f440 : nt!IopSynchronousServiceTail+0x1b1
ffffce0b`faf2f190 fffff803`08493746     : ffffe787`71bd6080 00000000`000000=
00
00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xe61
ffffce0b`faf2f2e0 fffff803`08085bf5     : ffffce0b`faf2f440 fffff803`085328=
6b
00000000`00000000 ffffe787`73efc700 : nt!NtDeviceIoControlFile+0x56
ffffce0b`faf2f350 00007ffa`8b450144     : 00000000`00000000 00000000`000000=
00
00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000cd`052fb568 00000000`00000000     : 00000000`00000000 00000000`000000=
00
00000000`00000000 00000000`00000000 : 0x00007ffa`8b450144


FAULTING_SOURCE_LINE:=20
C:\local\github\dpdk-kmods\windows\virt2phys\virt2phys_logic.c

FAULTING_SOURCE_FILE:=20
C:\local\github\dpdk-kmods\windows\virt2phys\virt2phys_logic.c

FAULTING_SOURCE_LINE_NUMBER:  369

FAULTING_SOURCE_CODE:=20=20
   113:         struct virt2phys_block *cur;
   114:=20
   115:         for (node =3D process->blocks.Next; node !=3D NULL; node=
 =3D
node->Next) {
   116:                 cur =3D CONTAINING_RECORD(node, struct virt2phys_bl=
ock,
next);
>  117:                 if (cur->mdl->StartV=
a =3D=3D virt)
   118:                         return cur;
   119:         }
   120:         return NULL;
   121: }
   122:=20


SYMBOL_NAME:  virt2phys!virt2phys_translate+d2

MODULE_NAME: virt2phys

IMAGE_NAME:  virt2phys.sys

STACK_COMMAND:  .cxr 0xffffce0bfaf2e3f0 ; kb

BUCKET_ID_FUNC_OFFSET:  d2

FAILURE_BUCKET_ID:  AV_virt2phys!virt2phys_translate

OS_VERSION:  10.0.17763.1

BUILDLAB_STR:  rs5_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a5b3e3eb-f919-3986-0426-062d62e143e1}

Followup:     MachineOwner
---------

You are receiving this mail because:
  • You are the assignee for the bug.
=20=20=20=20=20=20=20=20=20=20
= --16800098510.FaE2C7bD.2846164--