Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Intel Hardware

Intel's 14nm Broadwell Delayed Because of Low Yield 96

judgecorp writes "Intel has put back the delivery of its 14nm Broadwell desktop chip by a quarter because of a manufacturing issue that leaves it with too high a density of defects. The problem has been fixed, says CEO Brian Krzanich, who says, 'This happens sometimes in development phases.'" The good news is that it is just a defect density issue. A first round of tweaks failed to increase yield, but Intel seems to think a few more improvements to the 14nm process will result in acceptable yield.
This discussion has been archived. No new comments can be posted.

Intel's 14nm Broadwell Delayed Because of Low Yield

Comments Filter:
  • by stms ( 1132653 ) on Thursday October 17, 2013 @04:46PM (#45157275)

    Potentially it can keep going until the size of a transistor is just a few electrons across but as we get closer to that point quantum teleportation becomes more of an issue. This is cool video that explain some basic stuff about transistors and the end of Moore's Law.
    https://www.youtube.com/watch?v=rtI5wRyHpTg [youtube.com]

  • Not the real issue (Score:4, Interesting)

    by Anonymous Coward on Thursday October 17, 2013 @05:11PM (#45157623)

    Intel has produced two new generations of processor that were WORSE than Sandybridge. Higher power use (under load) and far less over-clockability. The newer part were ONLY better (in desktop systems) if you intended to use their new instructions (vanishingly unlikely) or the integrated graphics (which would be pointless- people buy expensive Intel CPUs to partner them with expensive GPUs from AMD or Nvidia).

    Intel, of course, were in the same position with the waves of Core2 parts, each of which essentially overlapped each other in performance generation on generation (although power consumption was much improved over the first generation of Core2 i7 parts).

    Intel currently doesn't know exactly where to go in the near future, and is attempting to hedge its bets by trying various things. It is currently undercutting its own HYPER-expensive ULV mobile high-end parts with the new 4-core 'atom' Bay-trail chips that seek to go head-to-head with ARM. Because current high-end ARM is so good, Intel is forced to sell a very dangerously good chip (dangerous to Intel's profits, that is) into low and mid-end tablets, running Android or Windows8.1

    However, even Intel's first decent 'Atom' part ever (after 5+ attempts) is beaten by Nvidia's somewhat lame Tegra 4, and Qualcomm's Snapdragon 800. It is exterminated by Apple's new ARM chip, soon to be seen in Apple's new iPad refresh.

    Intel's 22nm process, and use of FinFETs, has been a total disaster so far. A process advantage, and custom designed chips, doesn't allow Intel to beat ARM parts coming from commodity foundries at TSMC and Samsung in 28nm. Sure, Intel can make its own chips smaller than those on the previous process, and theoretically get more parts per wafer, but the per wafer costs rocket, the yields drop (initially), and insanely expensive new plants have to be built to service the new process.

    What does Intel get from spending all this new money on R+D? At this moment in computer history, almost nothing. The x86 is dying, and everyone BUT Intel builds ARM solutions. Every major player has a GPU (graphics) solution as good as Intel, and Intel isn't within a million miles of matching the AAA-gaming GPU designs from AMD and Nvidia (despite the fact that Intel has spent more money than every graphics company combined, across their combined periods of existence, to create its own GPU solutions).

    Intel simply has no current use for its expensive 14nm process. It has built the factories, so it is engaged in a waiting game- waiting for mobile parts to roll off the 14nm production lines that have clear market advantages over its current mobile chips. It just isn't worth Intel's time launching another round of non-improved parts. The market has changed forever, and on-one wants to buy "this season's Intel" for the brand loyalty reasons previously apparent.

    Intel fanboys want 6-core and 8-core parts, but Intel is extremely loathe to risk introducing better value into the desktop market. If Intel properly sold 6-core solutions, they would have to sell 6-core i5 parts, and these would beat-up their EXTREMELY profitable 4-core i7 parts. Intel is too in love with the status quo.

    If Intel's bay-trail 4-core parts prove good enough for tablets and non-gaming laptops, and they will do having greater performance than the more than adequate mobile 2-core core2 parts used in the first decent cheap laptops years ago, where does most of Intel's mobile biz go from here? Bay-trail parts (unlike those years old mobile 2-core core1/core2 laptop chips) also do all the video decoding in hardware, allowing flawless playback of all current video content (and bay-trail is strong enough to do CPU enhanced decode of 4K video recorded in h264).

    Bay-trail is the part Intel moved Heaven and Earth NOT to produce. Bay-trail is the final step on the race-to-the-bottom for x86 based computers that most non-AAA gamers will need. If the only real money Intel makes ends up from chips lie Bay-trail, Intel is done.

    Think about this. In a few weeks, you

  • Re:Pull an AMD (Score:5, Interesting)

    by 0123456 ( 636235 ) on Thursday October 17, 2013 @06:09PM (#45158233)

    Except the cores are probably small compared to the L3 cache, so most failures will be in the cache, not the cores.

    Back when I worked in the chip business, we designed them so some components could be disabled if they failed the manufacturing tests, but there were very few that we could actually sell that way. Either the fault would be in the components that couldn't easily be disabled, or there'd be multiple faults in too many places to make it viable.

    I have wondered myself whether the low-power CPUs are just the bin that wouldn't work at normal power levels.

It is easier to write an incorrect program than understand a correct one.

Working...