[ros-bugs] [Bug 1208] New: Fatal Pagefault in second stage installer.

ReactOS.Bugzilla at reactos.org ReactOS.Bugzilla at reactos.org
Wed Dec 28 06:13:06 CET 2005


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

           Summary: Fatal Pagefault in second stage installer.
           Product: ReactOS
           Version: TRUNK
          Platform: VMWare 5
        OS/Version: ReactOS
            Status: NEW
          Severity: critical
          Priority: P3
         Component: Win32
        AssignedTo: ros-bugs at reactos.org
        ReportedBy: waxdragon at gmail.com
         QAContact: ros-bugs at reactos.org


Between 20364 and 20368, I started seeing lockups during second stage install. 
The fatal page fault was:

Entered debugger on last-chance exception number 14 (Page Fault)
Memory at 0xfffffff4 could not be read: Page not present.
kdb:> bt
Eip:
<win32k.sys:909af (./subsys/win32k/ntuser/msgqueue.c:271
(co_MsqTranslateMouseMessage))>
Frames:
<win32k.sys:9169b (./subsys/win32k/ntuser/msgqueue.c:621
(co_MsqPeekHardwareMessage))>
<win32k.sys:92b8a (./subsys/win32k/ntuser/msgqueue.c:1259 (co_MsqFindMessage))>
<win32k.sys:885b6 (./subsys/win32k/ntuser/message.c:731 (co_IntPeekMessage))>
<win32k.sys:89033 (./subsys/win32k/ntuser/message.c:941 (co_IntWaitMessage))>
<win32k.sys:89362 (./subsys/win32k/ntuser/message.c:1051 (NtUserGetMessage))>
<ntoskrnl.exe:9ab1c (ntoskrnl/ke/i386/syscall.S:372 (KiSystemService))>
<user32.dll:52bd3 (lib/user32/windows/message.c:1166 (GetMessageW))>
<win32csr.dll:75fe (subsys/csrss/win32csr/desktopbg.c:188 (DtbgDesktopThread))>
<KERNEL32.dll:2fd9d (./lib/kernel32/thread/thread.c:55 (BaseThreadStartup))>
<00000000>
kdb:> regs
CS:EIP  0x0008:0x9d8a59af
SS:ESP  0x0010:0x9e14ea64
   EAX  0xfffffff4   EBX  0x80db03b0
   ECX  0x00000000   EDX  0x9d9023d0
   ESI  0x0184fe24   EDI  0x9e14ed64
   EBP  0x9e14ea8c
EFLAGS  0x00010293  CF AF SF IF IOPL0 RF
kdb:>

Digging deeper I am seeing numerous page faults while loading resources, such as:

Entered debugger on first-chance exception number 14 (Page Fault)
Memory at 0x00000000 could not be read: Page not present.
kdb:> bt
Eip:
<ntdll.dll:ad22 (lib/rtl/res.c:190 (LdrpAccessResource))>
Frames:
<ntdll.dll:a8ba (lib/rtl/i386/res_asm.s:19 ())>
<KERNEL32.dll:23bec (./lib/kernel32/misc/res.c:169 (LoadResource))>
<user32.dll:2f3d9 (lib/user32/windows/bitmap.c:138 (LoadCursorIconImage))>
<user32.dll:2fdf6 (lib/user32/windows/bitmap.c:409 (LoadImageW))>
<user32.dll:31fb6 (lib/user32/windows/cursor.c:261 (LoadCursorW))>
<user32.dll:32728 (lib/user32/windows/defwnd.c:277 (DefWndHandleSetCursor))>
<user32.dll:35022 (lib/user32/windows/defwnd.c:1225 (User32DefWindowProc))>
<user32.dll:358b1 (lib/user32/windows/defwnd.c:1536 (DefWindowProcW))>
<user32.dll:1de24 (lib/user32/controls/static.c:441 (StaticWndProc_common))>
<user32.dll:1df04 (lib/user32/controls/static.c:462 (StaticWndProcW))>
<user32.dll:52657 (lib/user32/windows/message.c:962 (IntCallWindowProcW))>
<user32.dll:53a52 (lib/user32/windows/message.c:1866
(User32CallWindowProcFromKernel))>
<ntdll.dll:a15b (lib/ntdll/main/i386/dispatch.S:105 (KiUserCallbackDispatcher))>
<comctl32.dll:3cc74 (lib/comctl32/propsheet.c:2770 (do_loop))>
<comctl32.dll:3d05d (lib/comctl32/propsheet.c:2897 (PropertySheetW))>
<syssetup.dll:5417 (lib/syssetup/wizard.c:1856 (InstallWizard))>
<syssetup.dll:20f1 (lib/syssetup/install.c:543 (InstallReactOS))>
<setup.exe:133a (subsys/system/setup/setup.c:86 (RunNewSetup))>
<setup.exe:13a5 (subsys/system/setup/setup.c:122 (WinMain))>
<setup.exe:14db (subsys/system/setup/setup.c:123 (WinMain))>
<setup.exe:116a> 
<setup.exe:1038>
<KERNEL32.dll:29c95 (./lib/kernel32/process/create.c:68 (BaseProcessStartup))>
<00000000>
kdb:>

and:

kdb:> bt
Eip:
<user32.dll:4238b (lib/user32/windows/icon.c:249 (CreateIconFromResourceEx))>
Frames:
<user32.dll:2f461 (lib/user32/windows/bitmap.c:146 (LoadCursorIconImage))>
<user32.dll:2fdf6 (lib/user32/windows/bitmap.c:409 (LoadImageW))>
<user32.dll:31fb6 (lib/user32/windows/cursor.c:261 (LoadCursorW))>
<win32csr.dll:727f (subsys/csrss/win32csr/desktopbg.c:67 (DtbgWindowProc))>
<user32.dll:52657 (lib/user32/windows/message.c:962 (IntCallWindowProcW))>
<user32.dll:53a52 (lib/user32/windows/message.c:1866
(User32CallWindowProcFromKernel))>
<ntdll.dll:a15b (lib/ntdll/main/i386/dispatch.S:105 (KiUserCallbackDispatcher))>
<win32csr.dll:75fe (subsys/csrss/win32csr/desktopbg.c:188 (DtbgDesktopThread))>
<KERNEL32.dll:2fd9d (./lib/kernel32/thread/thread.c:55 (BaseThreadStartup))>
<00000000>
kdb:> regs
CS:EIP  0x001b:0x77e9238b
SS:ESP  0x0023:0x0144fb24
   EAX  0x87dcfcfc   EBX  0x0144fdec
   ECX  0x0144ffb4   EDX  0xf000ff53
   ESI  0x00000000   EDI  0x00000000
   EBP  0x0144fb6c
EFLAGS  0x00000246  PF ZF IF IOPL0
kdb:>

Most of the resource loading pagefaults occur silently unless you have KDB set
to trap them, but the fatal page fault occurs when you move the mouse in the
second stage installer, causing the mouse cursor to be drawn. That is when you
will see the first and fatal page fault.  Also of note, the Messagebox you get
when you do not fill in your name in the second stage installer is missing it's
icons, replaced with what appears to be the system default icons.  Conferring
with Alex, this probably means resource loading in general is affected.

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


More information about the Ros-bugs mailing list