[ros-bugs] [Bug 5101] New: MmInitializeMemoryLimits bugchecks when between 3602 - 3608 MB RAM is present, with new booting method

ReactOS.Bugzilla at reactos.org ReactOS.Bugzilla at reactos.org
Tue Jan 5 23:30:33 CET 2010


http://www.reactos.org/bugzilla/show_bug.cgi?id=5101

           Summary: MmInitializeMemoryLimits bugchecks when between 3602 -
                    3608 MB RAM is present, with new booting method
           Product: ReactOS
           Version: TRUNK
          Platform: QEmu
        OS/Version: ReactOS
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: Kernel
        AssignedTo: ros-bugs at reactos.org
        ReportedBy: olaf_siejka at o2.pl
         QAContact: ros-bugs at reactos.org
            Blocks: 5099


Tested on Vbox 3.1.2 64bit, on Windows 7 64bit, with ReactOS. rev. 44931. When
VM is assigned with 3602 up to 3608 MB - MmInitializeMemoryLimits bugchecks:

(ntoskrnl\kd\kdio.c:303) ARC Paths: multi(0)disk(0)cdrom(224) \
multi(0)disk(0)cdrom(224) \reactos\
WARNING:  HalStopProfileInterrupt at hal\halx86\generic\profil.c:24 is
UNIMPLEMENTED!

*** Fatal System Error: 0x0000007d (INSTALL_MORE_MEMORY)
                       (0x00000AD4,0x00000092,0x00000092,0x00000211)

Entered debugger on embedded INT3 at 0x0008:0x808c58a0.
kdb:> bt
Eip:
<808c58a1 (lib\rtl\i386\debug_asm.S:42 (RtlpBreakWithStatusInstruction))>
Frames:
<8080677d (ntoskrnl/ke/bug.c:1110 (KeBugCheckWithTf at 24))>
<80806aa0 (ntoskrnl/ke/bug.c:1462 (KeBugCheck at 4))>
<80876e13 (ARM&#9516;&#9474;::INIT:284 (MmInitializeMemoryLimits at 8))>
<8087772f (ARM&#9516;&#9474;::INIT:998 (MmArmInitSystem at 8))>
<808880d9 (ntoskrnl/mm/mminit.c:359 (MmInitSystem at 8))>
<8083661d (ntoskrnl/ex/init.c:1008 (ExpInitializeExecutive at 8))>
<80803c18 (ntoskrnl/ke/i386/kiinit.c:559 (KiInitializeKernel at 24))>
<8080103a (ntoskrnl\ke\i386\boot.S:67 (KiSetupStackAndInitializeKernel at 24))>


-- 
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.



More information about the Ros-bugs mailing list