X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C81FE3.975CA8DE@onstor-exch02.onstor.net>; Mon, 5 Nov 2007 11:39:33 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C81FE3.975CA8DE"
References: <20071105111450.1389cc29@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: idea on cksseg problem
Date: Mon, 5 Nov 2007 11:37:19 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0A4470@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: idea on cksseg problem
Thread-Index: Acgf4CMe4OWm/lGTRW2cwbV1HHGaCQAAyR6I
From: "Rick Lund" <rick.lund@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"Brian Stark" <brian.stark@onstor.com>
Cc: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C81FE3.975CA8DE
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

We are using the CFE draminit code, which as I remember, only =
initializes the memory ranges for the amount of memory which physically =
exists.  I will check the CS settings, but I don't think this is the =
problem.
=20
-Rick

________________________________

From: Andy Sharp
Sent: Mon 11/5/2007 11:14 AM
To: Brian Stark
Cc: Rick Lund; Maxim Kozlovsky
Subject: idea on cksseg problem



I am forming a theory on why we vapor lock when accessing cksseg0
address -- we aren't being selective enough on what addresses are
mapped/configured to memory banks.  We need to make sure that we
map/configure only those addresses that have actual physical memory.  I
suspect we are letting the default configuration take place, which is
specified in the 1250 manual.   We don't have any memory at 0xc000.0000
but perhaps we have that address range configured to go to the memory
controller when we shouldn't, causing vapor lock whenever we access it.

Does this make any sense to anyone?  Causing any bells to ring?

Cheers,

a

PS There is a good reference to this on page 137 of the 1250 User
Manual (that's the PDF page number, page 109 of the internal document
numbering).



------_=_NextPart_001_01C81FE3.975CA8DE
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>idea on cksseg problem</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.3199" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText30569 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>We are using =
the CFE draminit code, which as I remember, only initializes the memory =
ranges for the amount of memory which physically exists.&nbsp; I will =
check the CS settings, but I don't think this is the =
problem.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>-Rick</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Andy Sharp<BR><B>Sent:</B> Mon =
11/5/2007 11:14 AM<BR><B>To:</B> Brian Stark<BR><B>Cc:</B> Rick Lund; =
Maxim Kozlovsky<BR><B>Subject:</B> idea on cksseg =
problem<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>I am forming a theory on why we vapor lock when =
accessing cksseg0<BR>address -- we aren't being selective enough on what =
addresses are<BR>mapped/configured to memory banks.&nbsp; We need to =
make sure that we<BR>map/configure only those addresses that have actual =
physical memory.&nbsp; I<BR>suspect we are letting the default =
configuration take place, which is<BR>specified in the 1250 =
manual.&nbsp;&nbsp; We don't have any memory at 0xc000.0000<BR>but =
perhaps we have that address range configured to go to the =
memory<BR>controller when we shouldn't, causing vapor lock whenever we =
access it.<BR><BR>Does this make any sense to anyone?&nbsp; Causing any =
bells to ring?<BR><BR>Cheers,<BR><BR>a<BR><BR>PS There is a good =
reference to this on page 137 of the 1250 User<BR>Manual (that's the PDF =
page number, page 109 of the internal =
document<BR>numbering).<BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C81FE3.975CA8DE--
