25 Jun
2004
25 Jun
'04
1:16 p.m.
Core isn't non-volatile! The contents of core memory is destroyed
everytime you read it. The computer has to restore the contents after every
read. I don't know if this is handled in the read/write circuitry, the
controller or by the CPU but I expect that the read/write circuitry does
it. It sounds like whatever is supposed to be restoring the contents of
those locations is bad. If you can store both 1s and 0 in each location and
then read them back then it appears that the cores and the write circuits
and read circuits are all working. But somewhere in there is something that
feeds the read data back to the write circuits so that it can be restored,
I suspect that that's where your problem is. Let me know what you find
when you find out the source of the problem.
Joe
At 10:53 AM 6/25/04 +0800, you wrote:
I have MM11-DP (16kW parity core) in my /04 which seems to have a little
problem.
Several locations which I've checked seems to be losing content (core is
supposed to be non-volatile). I've been debugging custom bootloaders
for the past week and it has since gone past annoying. It's like 3
locations out of 50 that are always reverting back to 000000 after a reboot.
Perhaps it's the driver logic to these 3 particular cores that are not
functioning properly? Or is it the cores itself?
--
/wai-sun