Slashdot Mirror


Intel Core 2 Updates, QX6850 and E6750

An anonymous reader writes "As AMD's Barcelona approaches, the price war between AMD and Intel continues. To spice things up a bit this week, Intel is throwing into the ring a number of new processors, refreshing the Core2 line-up. HEXUS reviews the high-end QX6850 and mid-range E6750: 'Now is a golden time for anyone looking to buy a new CPU, whether Intel or AMD. The latest round of price cuts means you can now get an incredible level of processing performance for little more than £100. But if your need to buy is not urgent, remember that Intel and its big rival are each promising new processors before the end of the year — AMD with K10 quad-core and Intel with 45nm Penryn-derived CPUs.'"

3 of 105 comments (clear)

  1. Unasked, unanswered question by ceeam · · Score: 4, Insightful

    Have they fixed those bugs?

    1. Re:Unasked, unanswered question by Kjella · · Score: 3, Insightful

      Unasked, unanswered, uninteresting question. It has bugs, and so's every consumer CPU since before the infamous Pentium floating point bug because as the fix some, they get some new. Most of those are worked around in BIOS or in basic OS routines, and the Core 2 processors are neither worse nor better than the rest (AMD or Intel). I'm happy to keep AMD around for competition but this is just FUD against Intel.

      --
      Live today, because you never know what tomorrow brings
    2. Re:Unasked, unanswered question by kestasjk · · Score: 4, Insightful

      So, I suppose you will blame the BIOS or the OS or anything _but_ _your_choice_ of CPUs when the security-related bugs that promise to allow any script kid to compromise your servers in unprecedented ways are exploited.

      For me, choosing any CPU that has known security bugs to be used on any connected computer is reason enough to be fired. What security bugs? I don't know where people get the idea that there were security bugs in the errata Intel released. Theo said that out of 50 bugs "2-3" were "potentially exploitable", but as far as I know no-one has given so much as a proof of concept.

      Saying that these bugs "allow any script kid to compromise your servers in unprecedented ways" is totally over the top.
      • No-one has shown that any of the bugs contain any sort of vulnerability,
      • no-one has shown that any of the hypothetical vulnerabilities allow remote code execution,
      • no-one has shown that any of the hypothetical remote code execution vulnerabilities could be exploited in realistic scenarios,
      • certainly nothing has been made available to script kids,
      • and I don't even know what "in unprecedented ways" means in this context.

      It is just FUD, until someone can actually point out a realistic code execution vulnerability, or even a PoC, even one that could be exploited in unrealistic scenarios, even a DoS, an idea, anything!
      --
      // MD_Update(&m,buf,j);