On 2011-11-18 09:08, Cameron Gutman wrote:
On Nov 17, 2011, at 7:07 PM, James Tabor wrote:
Head up on this one. It's recoverable by just
typing "cont" and it goes on.
(dll/ntdll/ldr/ldrutils.c:1177) Overlapping DLL:
C:\ReactOS\system32\oleaut32.dll
WARNING: MmFlushVirtualMemory at ntoskrnl/mm/ARM3/virtual.c:1044 is
UNIMPLEMENTED!
fixme:(dll/win32/wintrust/register.c:1161) stub
(dll/ntdll/ldr/ldrutils.c:1138) LDR: LdrpMapDll Relocating Image Name
C:\ReactOS\system32\mshtml.dll (76650000 -> 014C0000)
(dll/ntdll/ldr/ldrutils.c:1177) Overlapping DLL:
C:\ReactOS\System32\setupapi.dll
(ntoskrnl/se/semgr.c:299) SidInToken Calls: 40000
Assertion 'RtlCheckBit(&MiUserPfnBitMap, (ULONG)Page)' failed at
ntoskrnl/mm/freelist.c line 127
Entered debugger on embedded INT3 at 0x0008:0x80904efe.
kdb:> bt
Eip:
<NTOSKRNL.EXE:104eff (lib/rtl/i386/debug_asm.S:35 (_DbgBreakPoint@0))>
Frames:
<NTOSKRNL.EXE:c283d (ntoskrnl/mm/freelist.c:127 (MmRemoveLRUUserPage@4))>
<NTOSKRNL.EXE:c18de (ntoskrnl/mm/balance.c:134 (MmReleasePageMemoryConsumer@8))>
<NTOSKRNL.EXE:cbf6a (ntoskrnl/mm/section.c:2365 (MmPageOutSectionView@16))>
<NTOSKRNL.EXE:c822c (ntoskrnl/mm/rmap.c:143 (MmPageOutPhysicalAddress@4))>
<NTOSKRNL.EXE:c17a9 (ntoskrnl/mm/balance.c:177 (MmTrimUserMemory))>
<NTOSKRNL.EXE:c141c (ntoskrnl/mm/balance.c:366 (MiBalancerThread@4))>
<NTOSKRNL.EXE:f2972 (ntoskrnl/ps/thread.c:156 (PspSystemThreadStartup@8))>
<NTOSKRNL.EXE:5a6a (ntoskrnl/ke/i386/thrdini.c:78 (KiThreadStartup@0))>
<NTOSKRNL.EXE:f290e (ntoskrnl/ps/thread.c:625 (PsCreateSystemThread@28))>
<fcdebd80>
<NTOSKRNL.EXE:152e5 (ntoskrnl/ke/wait.c:527 (KeWaitForSingleObject@20))>
<NTOSKRNL.EXE:c524e (ntoskrnl/mm/mminit.c:292 (MmMpwThreadMain@4))>
<NTOSKRNL.EXE:f2972 (ntoskrnl/ps/thread.c:156 (PspSystemThreadStartup@8))>
<NTOSKRNL.EXE:5a6a (ntoskrnl/ke/i386/thrdini.c:78 (KiThreadStartup@0))>
<NTOSKRNL.EXE:f290e (ntoskrnl/ps/thread.c:625 (PsCreateSystemThread@28))>
<fce4fab0>
<00000001>
This seems pretty bad. We're trying to page out user memory that's not
registered in the user PFN bitmap. So either the bitmap is wrong or the
MC_USER list is wrong. Any ideas?
Let's not rule out the possibility that the bitmap functions are broken btw ;)
Timo suggested making a test for them a while ago -- I've started, but it's not
finished yet. Doesn't look too good though IIRC. I'll try and get it done and
committed.
*heavily hopes that might fix some Mm problems*
I fear Mm likely has bigger problems than those functions though, so there might
be something else wrong here, too.
-Tom