From:	"Charles Sandmann" <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: CWSDPMR0: system crash on INVD
Date:	Wed, 28 Mar 2001 16:38:58
Organization:	Aspen Technology, Inc.
Lines:	17
Message-ID:	<3ac213a2.sandmann@clio.rice.edu>
References:	<99t5g6$m5r$1 AT murdoch DOT acc DOT Virginia DOT EDU>
NNTP-Posting-Host:	dcloan.hou.aspentech.com
X-Trace:	selma.aspentech.com 985821324 32288 10.32.115.107 (28 Mar 2001 23:15:24 GMT)
X-Complaints-To:	postmaster AT aspentech DOT com
NNTP-Posting-Date:	28 Mar 2001 23:15:24 GMT
X-NewsEditor:	ED-1.5.8
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> When using the CWSDPR0.EXE (via stubedit), there is a privileged
> instruction that still crashes my machine: "invd", which invalidates
> the caches but does not write back dirty lines to main memory (i.e. is
> used only when coherency is not an issue.) Switching to the "wbinvd"
> instruction gets rid of the problem.
..

> This is not a stumbling block to me (in fact I noticed this a year ago
> and have not worried about it since switching over to "wbinvd"), but I
> thought someone who maintains CWSDPR0.EXE would want to know. 

I'm always fascinated by some of the things I find out that people
do with the software :-)

I would have to read the details of what this instruction does again
and play with some various hardware to think about it - but probably
the fix is use "wbinvd" ...  thanks for the interesting note.

- Raw text -