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

'NTOSKRNL work queue deadlock' after exiting NTVDM or command.com

    XMLWordPrintable

Details

    Description

      I can make this happen in 0.4.6rc1 gcc dbg and trunk 75707 gcc dbg.

      I just start the game POP2 via NTVDM (which immediately exits - this has never been different in the past)

      But what happens then is a really bad thing:
      The black NTVDM window is still visible when Win32K plays two iterations 'Looping Louie' and then we run into a full
      NTOSKRNL Work Queue Deadlock detected
      I can not interact with the system any longer.
      Not even ACPI-shutdown works at this point anymore.

      I can make this happen with at least 4 of 5tries.
      r75707.log
      I waited 18minutes in the hope it would break into debugger automatically maybe, but it didn't.

      I tested: this is a regression: r73532 is guilty/unhider

      Attachments

        1. CORE-13734-regressionTest-workQueueDeadlock.txt
          4 kB
          reactosfanboy
        2. cpu-consumers.png
          30 kB
          reactosfanboy
        3. r75707.log
          43 kB
          reactosfanboy
        4. r75707-deadlock.png
          20 kB
          reactosfanboy
        5. r75707-multipleTabK-procList-l2l.log
          150 kB
          reactosfanboy

        Issue Links

          Activity

            People

              ThFabba ThFabba
              reactosfanboy reactosfanboy
              Votes:
              3 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: