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.
Politics : Formerly About Advanced Micro Devices

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Petz who wrote (73008)9/24/1999 3:41:00 PM
From: Goutam  Read Replies (3) of 1571475
 
Petz,

Intel halts Xeon 550 shipments after flaw discovered

By Ed Scannell and Mike Lattig - InfoWorld Electric
Posted at 11:57 AM PT, Sep 24, 1999

Intel has put a hold on shipping two versions of its 550-MHz Pentium III Xeon 550 chips to OEMs for at least a couple of weeks because of a bug that is causing eight-way servers to hang, company officials confirmed.

Versions of the chip containing the 512Kb and 1MB caches have a problem involving communication between the processor and Intel's Saber motherboard, although company officials said they are still evaluating the full extent of the problem. The 2MB cache version of the chip does not appear to have the glitch, officials from both Intel and two OEMs said.

"We know there is a problem when we have a specific input signal from the processor that is at a slightly different range of voltage than specified on the processor data sheet. We expect to hopefully see a workaround in the next couple of weeks," said Otto Pijpker, an Intel spokesman.

A number of OEMs over the past couple of weeks were registering complaints that systems with the 512KB and 1MB versions of the chip were hanging on boot-up and presenting them with what one OEM called the "blue screen of death."

Intel officials admitted they discovered the problem during the typical stress tests they perform, which involve running industrial strength software intended to show up any defects in the chip and associated hardware.

"You have to keep in mind that this [problem] was observed in running test software that purposely stresses the processor and memory sub-systems, [software] that you would not see in general usage," Pijpker said.

Some analysts believe the problem is a mixed blessing. The bad news is chip bugs are never good because they cause problems with how systems process what could be crucial server-level applications. The good news is Intel appears to have caught the problem early on before many customers have deployed systems containing the offending chips.

They caution, however, that users should consult with their manufacturers to see if there are problems specific to that manufacturers configuration of the system.

"I can't tell how big a deal it is because we don't know how many people have bought the system so far. If they have, they probably want to contact their system vendors to see what they can do," said James Gruener, an analyst at The Aberdeen Group, a market research company, in Boston.

Both Intel officials and analysts said they do not know how many systems OEMs have shipped out containing the chip.
Manufacturers interviewed this week declined to say how many systems they have shipped to customers.

Intel shipped the finished versions of the Xeon 550 to OEMs on Aug. 23. Gruener said the problem may not hold Intel up to the most flattering light as large accounts begin to weigh eight-way servers containing the Xeon 550 with competing architectures.

"It probably doesn't bode well for the perception that Intel is ready to challenge other architectures in the enterprise. What people have to remember about the Intel platform, though, is that this is no different than any other microprocessor arch in terms of having an errata," Gruener said.


Intel Corp., in Santa Clara, Calif., is at www.intel.com.

Ed Scannell is an InfoWorld editor at large, based in Framingham, Mass.Michael Lattig is an InfoWorld reporter.

infoworld.com

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