From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zachary Amsden Subject: Re: Vmware crashes if compress/misc.c scrolls? Date: Thu, 21 Jun 2007 14:54:37 -0700 Message-ID: <467AF39D.5020606@vmware.com> References: <4679BBCB.2000202@zytor.com> <4679C152.8070407@goop.org> <4679C37E.5020908@zytor.com> <4679C497.8090500@goop.org> <4679C595.5010905@zytor.com> <4679C5DE.7090700@goop.org> <4679CA51.3080600@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4679CA51.3080600@zytor.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: "H. Peter Anvin" Cc: Virtualization Mailing List List-Id: virtualization@lists.linuxfoundation.org H. Peter Anvin wrote: > Jeremy Fitzhardinge wrote: > >> H. Peter Anvin wrote: >> >>> Jeremy Fitzhardinge wrote: >>> >>> >>>> You mean "is a real failure"? Or "is triggered by particular >>>> instructions"? It seems profoundly bogus (as in, surely DOS or >>>> something reads the framebuffer). >>>> >>>> >>>> >>> A real failure (although only triggered from some variant of protected >>> mode -- paging off?) >>> >>> >> Oh, it only happens in protected mode? So the answer to "how does the >> shadow framebuffer get populated?" is "real mode does it before >> switching to protected mode". >> >> > > Sure, but that means frobbing the boot parameter structure, with > associated problems. I guess I'm not inherently opposed to it, but I'd > like to understand if there is a cleaner workaround first. > I'm failing to understand exactly what the failure here is. Can you provide sample code that generates the problem? Surely, it should be possible to read the framebuffer. Zach