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 : AMD:News, Press Releases and Information Only!
AMD 203.14-0.8%Jan 9 9:30 AM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Yougang Xiao who wrote (1871)11/1/1997 3:16:00 AM
From: Yousef  Read Replies (2) of 6843
 
Yougang,

Re: "My second question to you is ... has Intel ever experienced "yield" problem like AMD is facing now?"

Not recently ... process problems like this happened back in the 80's.
With new process equipment and better process understanding, margin
problems like this are avoidable.

Re: "How long (if any) for Intel to solve such problem?"

As I tried to explain to Petz, there are basically two types of yield
problems: 1)low yield at slow functional test ... low yield across all
speed bins ... 2)low yield at high frequency ... referred to as low
survival yield. (slow speed bins unaffected).

It turns out the yield problem #1 is the easiest to detect, solve and
start producing good parts. Yield problem #2 (which is what I believe
is affecting AMD) is a more difficult problem in which a process parameter
or group of parameters has drifted (maybe even all are within spec) and
these parameters are causing high speed failures. My experience on this
type of problem says that it takes 2 process "cycle times" (a total of
about 4 months) to find "root cause", implement a fix and then get all new
material/wafers out and qualified. So if this problem was detected in
late July ... then "fixed" wafers could be coming out late in November.

Hope this helps.

Make It So,
Yousef
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext