[ros-bugs] [Bug 2872] New: ReactOS Setup - Failed Assertions

[ReactOS.Bugzilla at www.reactos.org]

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

           Summary: ReactOS Setup - Failed Assertions
           Product: ReactOS
           Version: TRUNK
          Platform: QEmu
        OS/Version: ReactOS
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: Kernel
        AssignedTo: ros-bugs at reactos.org
        ReportedBy: stefan__100__ at hotmail.com
         QAContact: ros-bugs at reactos.org


Created an attachment (id=2125)
 --> (http://www.reactos.org/bugzilla/attachment.cgi?id=2125)
Stack Frames for the Assertions

During the final part of ReactOS text-mode setup stage, the "Flushing Cache"
stage entered before rebooting, one of the two following assertions can occur
(stack frames are provided in the attachment):


Assertion 1: Assertion '(Resource->Flag & ResourceNeverExclusive) == 0' failed
at ntoskrnl\ex\resource.c line 785

Assertion 2: Assertion '(Resource->Flag & ResourceNeverExclusive) == 0' failed
at ntoskrnl\ex\resource.c line 2275


Most of the time I never encounter these, so I suspect there is some tricky
timing issue involved. Alas, I am unable to figure out what timing causes the
assertions to be hit.

I discovered the following through the use of KDB:
Using "cont" to go past assertion 1 causes assertion 2 to be hit.
Using "cont" on assertion 2 causes assertion 2 to be hit again.

Forcing ReactOS to shut down after this issue causes boot errors to occur after
rebooting. Thus, a reinstall is required.


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