[ros-dev] Re: [ros-svn] [blight] 18292: Huh, what? Oops! Just some stuff which noone cares about...

Gregor Anich blight at blight.eu.org
Thu Oct 6 18:58:28 CEST 2005


On Thursday 06 October 2005 17:49, Hartmut Birr wrote:
> blight at svn.reactos.com wrote:
> >Huh, what? Oops! Just some stuff which noone cares about...
> >
> >
> >
> >Updated files:
> >trunk/reactos/ntoskrnl/include/internal/i386/fpu.h
> >trunk/reactos/ntoskrnl/ke/i386/exp.c
> >trunk/reactos/ntoskrnl/ke/i386/fpu.c
> >
> >_______________________________________________
> >Ros-svn mailing list
> >Ros-svn at reactos.org
> >http://www.reactos.org/mailman/listinfo/ros-svn
>
> Something is wrong in this changes. If I try to install HDD-Health, I
> get a crash.
>
> - Hartmut
>
> Assertion (Ke386GetCr0() & X86_CR0_TS) == 0 failed at
> ntoskrnl\ke\i386\fpu.c:337
> A problem has been detected and ReactOS has been shut down to prevent
> damage to your computer.
>
> Technical information:
>
> *** STOP: 0x00000000 (0x00000000,0x00000000,0x00000000,0x00000000)
>
> Frames:
> <ntoskrnl.exe:1c76 (ntoskrnl/ke/bug.c:487 (KeBugCheckEx at 20))>
> <ntoskrnl.exe:1c8d (ntoskrnl/ke/bug.c:503 (KeBugCheck at 4))>
> <ntoskrnl.exe:556b6 (ntoskrnl/ke/i386/fpu.c:337 (KiGetFpuState))>
> <ntoskrnl.exe:545c1 (ntoskrnl/ke/i386/exp.c:904 (KeTrapFrameToContext at 12))>
> <ntoskrnl.exe:54bab (ntoskrnl/ke/i386/exp.c:1195 (KiDispatchException at 20))>
> <ntoskrnl.exe:577ff (ntoskrnl/ke/i386/usertrap.c:133
> (KiUserTrapHandler at 12))>
> <ntoskrnl.exe:5bcc9 (ntoskrnl/mm/i386/pfault.c:132 (KiPageFaultHandler))>
> <ntoskrnl.exe:57251 ({standard input}:152 (KiTrapProlog2))>
> <shell32.dll:ad18 (lib/shell32/shell32_main.c:480 (SHGetFileInfoW at 20))>
>

Oh, uh, oops!
I guess thats from a SMP machine? If it was SMP, can you try with a single CPU 
and let me know if it still crashes? (Sorry, I didnt think of SMP)

To temporary fix the problem you can make KiGetFpuState return NULL always I 
think.
Unfortunately I dont have a SMP machine to test so maybe it will take a bit 
until I find a good solution.


More information about the Ros-dev mailing list