[haiku-development] Re: Anyone seen this - Vesa delay
- From: Ingo Weinhold <ingo_weinhold@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 09 Jul 2008 00:33:19 +0200
On 2008-07-08 at 19:17:12 [+0200], Jan Klötzke <jan.kloetzke@xxxxxxxxxx>
wrote:
> Jan Klötzke <jan.kloetzke@xxxxxxxxxx> wrote:
> > Stephan Assmus <superstippi@xxxxxx> wrote:
> > > I know that Ingo is experiencing the same behavior. On my system, I just
> > > get "General System Error" when I try to change resolution (VESA also)
> > > during runtime. But I think if I have a vesa kernel settings file with
> > > anything different than the native resolution, my system does not boot.
> > > I
> > > am not sure, but I thought for the behavior you describe, there is a bug
> > > report, but I could be wrong.
> > >
> > > Jan, any ideas?
> >
> > Unfortunately not really. I suspect that there is an error in the
> > instruction emulation part of the vm86 stuff which confuses the BIOS. Just
> > a wild guess. I was not able yet to reproduce it on any of my systems
> > here.
> >
> > What makes it really interesting and what is new to me is that you get
> > a "General System Error". Would you mind to enable TRACE_VM86 in
> > src/system/kernel/arch/x86/vm86.cpp and capture the output? Maybe I can
> > spot something there because the traces I've got so far did not contain
> > anything suspicious...
>
> Wait a minute... I found something. The PUSHF/POPF instructions were not
> emulated correctly! The attached patch should fix that. Hope that solves the
> problems. At least it should be applied nonetheless.
It does solve the long mode change times here.
CU, Ingo
Other related posts:
