[ros-bugs] [Bug 805] Shutdown issues

[ReactOS.Bugzilla at reactos.com]

http://reactos.com/bugzilla/show_bug.cgi?id=805





------- Additional Comments From waxdragon at gmail.com  2005-27-09 06:25 -------
I tested both debug and release builds of r18117 for this bug, using
boot->cmd->exit.  Apparently this bug acts differently depending on the
"hardware" it's run on.  Under qemu 0.7.1 and 0.7.2 with the debug build, I get
a hang on shutdown that causes qemu to not release the cursor.  This happens
regardless of DEBUGPORT. Using a release build user qemu also results in a hang,
but with DEBUGPORT=screen I see this before the hang:

RTL: RtlNtStatusToDosErrorNoTeb(0xc0): no valid W32 error mapping
RTL: RtlNtStatusToDosErrorNoTeb(0xc0): no valid W32 error mapping

Under VMWare 5 with a debug build, I do not see a hang on shutdown *only if* I
am using DEBUGPORT=COM1, otherwise I see a hang.  Using DEBUGPORT=screen, ROS
actually triple faults the CPU. With a release build, I actually get a crash,
but in talking with blight, he claims the EIP is random.  I did see a different
EIP in a release build of another version. Anyway, here is the crash:

RTL: RtlNtStatusToDosErrorNoTeb(0xc0): no valid W32 error mapping
RTL: RtlNtStatusToDosErrorNoTeb(0xc0): no valid W32 error mapping
Stack underflow (tf->esp 9dba0000 Limit 9dbb0000)
Stack Segment Fault Exception: 12(0)
CS:EIP 8:9d4b88b6 <\??\C:\ReactOS\system32\win32k.sys: 418b6>
cr2 9db9fffc cr3 fc2b000 Proc: 8070c198 Pid: 78 <csrss.exe> Thrd: 80943020 Tid: ac
DS 10 ES 10 FS 30 GS 0
EAX: 8cdb289c   EBX: 00000005   ECX: 00000005
EDX: 8cdb289c   EBP: 9dba0004   ESI: 80943378
ESP: 9dba0000 EDI: 80943378   EFLAGS: 00010246 kESP 9dba0000 kernel stack base
9dbb0000
Frames: 


For reference, the above EIP is subsys/win32k/dib/dib32gen.c:688
(DIB_32BPP_BitBlt_Generic)

I concur with the inital assesment that this occured close to the win32k
rewrites.  Hopfully now that we have a profile, I can regression test to find
when this started.

-- 
Configure bugmail: http://reactos.com/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.