AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20071105111110.3e584cda@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<brian.stark@onstor.com>,<rick.lund@onstor.com>,<maxim.kozlovsky@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 5 Nov 2007 11:14:50 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: Brian Stark <brian.stark@onstor.com>
Cc: Rick Lund <rick.lund@onstor.com>, Maxim Kozlovsky
 <maxim.kozlovsky@onstor.com>
Subject: idea on cksseg problem
Message-ID: <20071105111450.1389cc29@ripper.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

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).