SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : All About Sun Microsystems

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Prognosticator who wrote (34713)8/28/2000 8:55:46 PM
From: THE WATSONYOUTH  Read Replies (1) of 64865
 
At least Sun appear to be mea-culpa'ing and learning from the event. To the extent of even designing around it with mirrored memory modules in future server designs: outstanding!

This "mirrored memory" means they will have to use 16Meg for actual 8Meg of memory (doubling up every bit). I believe that means they were never using ECC modules but simple parity modules in the first place. That would explain why the applications terminated every time a parity check detected a memory error. Since simple parity checking can only detect single bit errors, I think there is a good possibility that some data got corrupted. I think 8Meg ECC modules are quite rare so they instead went with this "mirrored memory" approach.. Of course, they will be paying thru the nose for 16Meg when only 8Meg is required. But, they likely had no choice. I mean.... we couldn't have USIII systems delayed any longer now....could we?? So, who makes this 16Meg fast reliable SRAM??? Only one company I know of.

By year's end, Sun will release a mirrored memory module that should address this issue once and for all, Shoemaker added...........

Sun quality???? HA! HA! LOL! What a bunch of shoemakers.

THE WATSONYOUTH
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext