Re: [ros-dev] [ros-diffs] [sginsberg] 43958: - Fix the "fix" of un-protecting the 7 IDT entries on P5 in HAL's BIOS call code when setting the custom Invalid Opcode handler

[Stefan Ginsberg]

Should be fixed as of 44032.

>   Date: Mon, 9 Nov 2009 00:13:51 +0300
>  From: gorbachev(a)reactos.org
>  To: ros-dev(a)reactos.org
>  Subject: Re: [ros-dev] [ros-diffs] [sginsberg] 43958: - Fix the "fix"
> of	un-protecting the 7 IDT entries on P5 in HAL's BIOS call code	when setting the
> custom Invalid Opcode handler
>  
> >   Ok...so how does it crash? And where? Can I get a
> > backtrace or something? 
>  
>  First time, HalpBiosDisplayReset() is called when booting, before
>  KiI386PentiumLockErrataFixup(). Recent changes cause a page to be
>  protected from writing. Then kernel tries to write to this page and
>  crashes. Another time, HalpBiosDisplayReset() is called when shutting
>  down; before r39959, crash happened to be there. From r39959 and
>  before r43958, write protection was established only in
>  KiI386PentiumLockErrataFixup().
>  
>  It appears that a fix for a fix for a fix is now needed:)
>  
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev 
 		 	   		  
_________________________________________________________________
Keep your friends updated—even when you’re not signed in.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/so…