Details
-
Bug
-
Resolution: Duplicate
-
Critical
-
None
-
None
Description
reactos-bootcd-0.4.15-dev-6902-g83e1193-x86-gcc-lin-dbg new VM, first boot but does not seems fully systematic (only 1st boot as "common factor")
Regression as it used to work with : Retesting CORE-9110 and CORE-18280
Guilty commit between 
bootcd-0.4.15-dev-4914-g2220e56 and 
0.4.15-dev-6902-g83e1193
If VM is restarted, installation starts without BSOD
Given the backtrace, recent CC commits from DougLyons may be the cause : https://github.com/reactos/reactos/commits/master/ntoskrnl/cc
WARNING: MmAdjustWorkingSetSize at ntoskrnl/mm/ARM3/mmsup.c:58 is UNIMPLEMENTED!*** Fatal System Error: 0x00000139 |
(0x00000003,0xF648CA2C,0xF648C9CC,0x00000000) |
Entered debugger on embedded INT3 at 0x0008:0x805A5098.kdb:> bt |
Eip:
|
<ntoskrnl.exe:1a5098 (sdk/lib/rtl/i386/debug_asm.S:56 (RtlpBreakWithStatusInstruction))> |
Frames:
|
<ntoskrnl.exe:96b9d (ntoskrnl/ke/bug.c:1070 (KeBugCheckWithTf))> |
<ntoskrnl.exe:167073 (ntoskrnl/ke/i386/traphdlr.c:1613 (KiRaiseSecurityCheckFailureHandler))> |
<ntoskrnl.exe:39a1 (:0 (KiRaiseSecurityCheckFailure))> |
<ntoskrnl.exe:8bb9 (/mnt/ramdisk/buildbot/output-MinGW-i386/sdk/include/ddk/wdm.h:11531 (CcRosUnmarkDirtyVacb))> |
<ntoskrnl.exe:8bfe (ntoskrnl/cc/view.c:167 (CcRosFlushVacb))> |
<ntoskrnl.exe:a4a7 (ntoskrnl/cc/view.c:1140 (CcFlushCache))> |
<ntoskrnl.exe:10f3c3 (ntoskrnl/mm/section.c:3278 (MmCreateImageSection))> |
<ntoskrnl.exe:1115a0 (ntoskrnl/mm/section.c:4727 (MmCreateSection))> |
<ntoskrnl.exe:df277 (ntoskrnl/mm/ARM3/section.c:3529 (NtCreateSection))> |
<ntoskrnl.exe:3fe5 (:0 (KiSystemCallTrampoline))> |
<ntoskrnl.exe:16772b (ntoskrnl/ke/i386/traphdlr.c:1840 (KiSystemServiceHandler))> |
<ntoskrnl.exe:3e2f (:0 (KiFastCallEntry))> |
<ntdll.dll:f49d>
|
<kernel32.dll:164ed>
|
<Vivaldi.1.0.435.46.exe:27c1> |
<Vivaldi.1.0.435.46.exe:2a63> |
<Vivaldi.1.0.435.46.exe:2ff2> |
<Vivaldi.1.0.435.46.exe:306d> |
<kernel32.dll:11b41>kdb:> cont
|
(ntoskrnl/ke/bug.c:568) Potentially unloaded driver! |
(ntoskrnl/ke/bug.c:568) Potentially unloaded driver! |
(ntoskrnl/ke/bug.c:568) Potentially unloaded driver! |
(ntoskrnl/ke/bug.c:568) Potentially unloaded driver! |
|
Exact same pattern as CORE-19319
Attachments
Issue Links
- duplicates
-
-
- Resolved
-
- is duplicated by
-
-
- Resolved
-