Re: [ros-dev] Boot Error

[Hartmut Birr]

Hi,

I get the same error with the up build but the smp build works. It seems
that the bug comes from Thomas' handle table improvment.
PsInitClientIDManagment is called befor PsInitProcessManagment.
PsInitClientIDManagment calls some function which needs a valid current
process and which is setup later in PsInitProcessManagment. The smp
build works, because the page at address 0 is unmapped later.

- Hartmut

James Tabor schrieb:
> Wow!
> Current SVN (Head)!
>
> Used memory 1015744Kb
> (mm/mminit.c:375) Kernel Stack Limits. InitTop = 0x80133000, Init =
> 0x80130000
> (mm/virtual.c:214) FIXME: MEMORY_AREA_SYSTEM case incomplete (or
> possibly wrong)
>  for NtQueryVirtualMemory()
> (ke/bug.c:56) Found Bugcheck Resource Data!
> (ke/bug.c:67) Got Pointer to Bugcheck Resource Data!
> (ke/clock.c:80) KiInitializeSystemClock()
> (ke/clock.c:99) Finished KiInitializeSystemClock()
> No current process
> Entered debugger on last-chance exception number 14 (Page Fault)
> Memory at 0x9c could not be read: Page not present.
> No current process
> KeBugCheckWithTf at ke/catch.c:224
> A problem has been detected and ReactOS has been shut down to prevent
> damage to
> your computer.
>
> The problem seems to be caused by the following file: ntoskrnl.exe
>
> KMODE_EXCEPTION_NOT_HANDLED
>
> Technical information:
>
> *** STOP: 0x0000001E (0xc0000005,0x8002f410,0x00000000,0x00000018)
>
> ***    ntoskrnl.exe - Address 0x8002f410 base at 0x80000000, DateStamp
> 0x0
>
> Page Fault Exception: 14(0)
> Processor: 0 CS:EIP 8:8002f410 ntoskrnl.exe:2f410
> cr2 18 cr3 26000 Proc: 0
> DS 10 ES 10 FS 30 GS 10
> EAX: 00000000   EBX: 00000680   ECX: 00026000
> EDX: 00000064   EBP: 8013245c   ESI: 80132834   ESP: 801323ac
> EDI: 80132be0   EFLAGS: 00210046 kESP 801323ac Frames:
> ntoskrnl.exe:300fc
> ntoskrnl.exe:de31
> ntoskrnl.exe:1285
> ntoskrnl.exe:1aff
> ntoskrnl.exe:382d
> ntoskrnl.exe:c4a3e
> <46C>
>
> KeBugCheckWithTf at ke/catch.c:224
> A problem has been detected and ReactOS has been shut down to prevent
> damage to
> your computer.
>
> The problem seems to be caused by the following file: ntoskrnl.exe
>
> KMODE_EXCEPTION_NOT_HANDLED
>
> Technical information:
>
> *** STOP: 0x0000001E (0x80000003,0x80005c47,0x00000000,0x00000000)
>
> ***    ntoskrnl.exe - Address 0x80005c47 base at 0x80000000, DateStamp
> 0x0
>
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev