[ros-bugs] [Bug 4249] New: UnknownDevices app asserts at start

[ReactOS.Bugzilla at www.reactos.org]

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

           Summary: UnknownDevices app asserts at start
           Product: ReactOS
           Version: TRUNK
          Platform: VirtualBox
               URL: http://www.halfdone.com/Development/UnknownDevices/
        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


This bug originates in 39925 (the hyperspace commit by code ninjas). One
revision before UD works more/less fine.

To replicate: on rev 39925, using vbox 2.1.4, run UnknownDevices app (you can
get it from the given link, latest beta version).

The debug log:

Assertion 'KeGetCurrentIrql() <= APC_LEVEL' failed at
ntoskrnl/include/internal/ke_x.h line 1798
PuTTYEntered debugger on embedded INT3 at 0x0008:0x808c2572.
kdb:> bt
Eip:
<NTOSKRNL.EXE:c2573 (lib/rtl/res.c:278 (LdrFindResourceDirectory_U at 16))>
Frames:
<NTOSKRNL.EXE:147a3 (ntoskrnl/include/internal/ke_x.h:1824
(CcRosReleaseCacheSegment at 20))>
<NTOSKRNL.EXE:8bdd4 (ntoskrnl/include/internal/ke_x.h:1856
(MmNotPresentFaultSectionView at 16))>
<NTOSKRNL.EXE:8cc0a (ntoskrnl/mm/section.c:1320 (MmAccessFaultSectionView at 16))>
<NTOSKRNL.EXE:80282 (ntoskrnl/mm/mminit.c:295 (MiDbgKernelLayout at 0))>
<NTOSKRNL.EXE:8037b (ntoskrnl/mm/mminit.c:317 (MiDbgDumpMemoryDescriptors at 0))>
<NTOSKRNL.EXE:bcdc1 (ntoskrnl\ke\i386\trap.s:0 (KiUnexpectedInterrupt58))>
<ntdll.dll:4975 (dll/ntdll/ldr/utils.c:1725 (LdrFixupImports))>
<ntdll.dll:57c2 (dll/ntdll/ldr/utils.c:1998 (LdrPEStartup))>
<ntdll.dll:24f4 (dll/ntdll/ldr/startup.c:498 (LdrpInit at 12))>
<ntdll.dll:607e (dll\ntdll\dispatch\i386\dispatch.S:107
(KiUserCallbackExceptionHandler))>
kdb:>


-- 
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.