Uploaded image for project: 'Core ReactOS'
  1. Core ReactOS
  2. CORE-14094

[Virtual PC 2004 SP1] "Assertion failed: FastMutex->Owner != Thread", during init of mouclass.sys + vpc-8042.sys

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 0.4.15
    • NTCore
    • Virtual PC 2004 SP1 (5.3.582.27)

    Description

      1. Install ROS.
      2. Install VPC VM Additions. Reboot to "activate" them.
      3. Boot fails:

      (ntoskrnl/kd/kdio.c:105) ReactOS 0.4.8-dev (Build 20171210-0.4.8-dev-391-g197ec4c) (Commit 197ec4c5b8f807ee64f323d1461295841bd31c59)
      ...
      (ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\System32\drivers\vpc-8042.sys at FCAB4000 with 11 pages
      (ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\System32\drivers\WMILIB.SYS at FCAAC000 with 8 pages
      (ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\System32\drivers\kbdclass.sys at FCA98000 with 14 pages
      (ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\System32\drivers\mouclass.sys at FCA8A000 with e pages
       
      *** Assertion failed: FastMutex->Owner != Thread
      ***   Source File: /srv/buildbot/Build_GCCLin_x86/build/ntoskrnl/include/internal/ex.h, line 1269
       
      Break repeatedly, break Once, Ignore, terminate Process or terminate Thread (boipt)? 
      kdb:> o
      Execute '.cxr FCB79240' to dump context
      [7h
      Entered debugger on embedded INT3 at 0x0008:0x80949fee.
      kdb:> bt
      Eip:
      <NTOSKRNL.EXE:149fef (:0 (DbgBreakPoint))>
      Frames:
      <NTOSKRNL.EXE:2fe4d (ntoskrnl/include/internal/ex.h:1269 (ExAcquireFastMutexUnsafe))>
      <vpc-8042.sys:9f5c>
      <NTOSKRNL.EXE:6f88b (ntoskrnl/io/iomgr/irp.c:1223 (IofCallDriver))>
      <mouclass.sys:2639 (drivers/input/mouclass/mouclass.c:863 (ClassPnp))>
      <NTOSKRNL.EXE:6f88b (ntoskrnl/io/iomgr/irp.c:1223 (IofCallDriver))>
      <NTOSKRNL.EXE:775e3 (ntoskrnl/io/pnpmgr/pnpmgr.c:1308 (IopSynchronousCall))>
      <NTOSKRNL.EXE:77684 (ntoskrnl/io/pnpmgr/pnpmgr.c:598 (IopSendRemoveDevice))>
      <NTOSKRNL.EXE:7c21b (ntoskrnl/io/pnpmgr/pnpmgr.c:4168 (IoInvalidateDeviceState))>
      <vpc-8042.sys:9aa6>
      <vpc-8042.sys:9954>
      <vpc-8042.sys:9ff8>
      <NTOSKRNL.EXE:6f88b (ntoskrnl/io/iomgr/irp.c:1223 (IofCallDriver))>
      <mouclass.sys:119f (drivers/input/mouclass/misc.c:45 (ForwardIrpAndWait))>
      <mouclass.sys:2529 (drivers/input/mouclass/mouclass.c:823 (ClassPnp))>
      <NTOSKRNL.EXE:6f88b (ntoskrnl/io/iomgr/irp.c:1223 (IofCallDriver))>
      <NTOSKRNL.EXE:775e3 (ntoskrnl/io/pnpmgr/pnpmgr.c:1308 (IopSynchronousCall))>
      <NTOSKRNL.EXE:7c3f3 (ntoskrnl/io/pnpmgr/pnpmgr.c:672 (IopStartDevice2))>
      <NTOSKRNL.EXE:7bf57 (ntoskrnl/io/pnpmgr/pnpmgr.c:726 (IopStartAndEnumerateDevice))>
      <NTOSKRNL.EXE:7bfd8 (ntoskrnl/io/pnpmgr/pnpmgr.c:796 (IopStartDevice))>
      <NTOSKRNL.EXE:76e21 (ntoskrnl/io/pnpmgr/pnpinit.c:376 (PipCallDriverAddDevice))>
      <NTOSKRNL.EXE:7c74d (ntoskrnl/io/pnpmgr/pnpmgr.c:2749 (IopActionInitChildServices))>
      <NTOSKRNL.EXE:77951 (ntoskrnl/io/pnpmgr/pnpmgr.c:1367 (IopTraverseDeviceTreeNode))>
      <NTOSKRNL.EXE:77966 (ntoskrnl/io/pnpmgr/pnpmgr.c:1381 (IopTraverseDeviceTreeNode))>
      <NTOSKRNL.EXE:77966 (ntoskrnl/io/pnpmgr/pnpmgr.c:1381 (IopTraverseDeviceTreeNode))>
      <NTOSKRNL.EXE:77966 (ntoskrnl/io/pnpmgr/pnpmgr.c:1381 (IopTraverseDeviceTreeNode))>
      <NTOSKRNL.EXE:7798d (ntoskrnl/io/pnpmgr/pnpmgr.c:1406 (IopTraverseDeviceTree))>
      <NTOSKRNL.EXE:77bf2 (ntoskrnl/io/pnpmgr/pnpmgr.c:2794 (IopInitializePnpServices))>
      <NTOSKRNL.EXE:7b9dd (ntoskrnl/io/pnpmgr/pnpmgr.c:2481 (IopEnumerateDevice))>
      <NTOSKRNL.EXE:17b72d (ntoskrnl/io/iomgr/iomgr.c:578 (IoInitSystem))>
      <NTOSKRNL.EXE:176b95 (ntoskrnl/ex/init.c:1801 (Phase1InitializationDiscard))>
      <NTOSKRNL.EXE:3352a (ntoskrnl/ex/init.c:2015 (Phase1Initialization))>
      <NTOSKRNL.EXE:113354 (ntoskrnl/ps/thread.c:156 (PspSystemThreadStartup))>
      <NTOSKRNL.EXE:12a699 (ntoskrnl/ke/i386/thrdini.c:78 (KiThreadStartup))>
      <NTOSKRNL.EXE:11331b (ntoskrnl/ps/state.c:565 (NtQueueApcThread))>
      <5d8950ec>
      Couldn't access memory at 0x83E58959!
      kdb:> cont

      NB: This works fine on Windows XP.

      Attachments

        Issue Links

          Activity

            People

              bug zilla Bug Zilla
              Serge Gautherie Serge Gautherie
              Votes:
              6 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: