[ros-bugs] [Bug 3626] cmd shell initially comes up in permanent loop printing squares

[ReactOS.Bugzilla at www.reactos.org]

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





--- Comment #9 from Haos <olaf_siejka at o2.pl>  2008-11-18 21:23:36 CET ---
The result (with said dprint):

...
(subsystems\win32\csrss\win32csr\guiconsole.c:1149) 208
(subsystems\win32\csrss\win32csr\guiconsole.c:1149) 208
(subsystems\win32\csrss\win32csr\guiconsole.c:1149) 208
(subsystems\win32\csrss\win32csr\guiconsole.c:1149) 208
(subsystems\win32\csrss\win32csr\guiconsole.c:1149) 208
(subsystems\win32\csrss\win32csr\guiconsole.c:1149) 208
...

I was able to replicate this issue on another machine. After installing ROS
from scratch, you just try to start cmd via Start/run (dunno about desktop
icon) right after ROS boots. If cmd starts normally, reboot and try again. This
methode doesnt work on VM though.

Csrss backtrace on that second machine was almost identical, only difference
was a second thread in Running state:

Attached to thread 0x000000ac.
kdb:> bt
Eip:
<NTOSKRNL.EXE:102fd (ntoskrnl/ke/wait.c:183 (@KiExitDispatcher at 4))>
Frames:
<NTOSKRNL.EXE:ccc4 (ntoskrnl/include//internal/ke_x.h:276
(KeReleaseSemaphore at 16))>
<NTOSKRNL.EXE:665c7 (ntoskrnl/lpc/reply.c:379 (NtReplyWaitReceivePortEx at 20))>
<NTOSKRNL.EXE:66a52 (ntoskrnl/lpc/reply.c:542 (NtReplyWaitReceivePort at 16))>
<NTOSKRNL.EXE:a14ea (ntoskrnl\ke\i386\trap.s:244 (KiFastCallEntry))>
<ntdll.dll:5f0e (dll\ntdll\dispatch\i386\dispatch.S:267
(KiFastSystemCallRet at 0))>
<00000000>


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