alg7_munif
Supreme [H]ardness
- Joined
- Oct 9, 2006
- Messages
- 5,862
Funny how your "yes" turns to "no" Scali 
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
So what is the point that you wanted to make with this long errata argument?
Tell me how many of those Dell, HP, and other OEM system users that have actually updated their BIOS?
Does this means that someone, who bought an OEM C2D system in the early days before the microcode update was out and he has never flashed the BIOS before, is running a computer with a bigger risk than someone who is running a Phenom without the fix?
Funny how your "yes" turns to "no" Scali![]()
What are the facts? Are the bold part of your post facts? I still don't get what is the point that you want to make with your argument?To bring out the facts.
No, none of the C2D errata are as severe as the Phenom one. They are mostly 'cosmetic' patches... where stability issues are mostly theoretical, or at least related only to certain OS/driver code.
So yes, an unpatched C2D system is less stable than a patched C2D system... But that doesn't make it as unstable as an unpatched Phenom system.
Why not? Well, the OEMs actually refused to sell Opteron systems because they encountered stability issues. The Xeon systems have undergone the same heavy duty test cycle, but they didn't encounter any problems, and the servers were launched on schedule.
So whatever errata the C2D may have, they were never encountered 'in the wild'.
What are the facts? Are the bold part of your post facts? I still don't get what is the point that you want to make with your argument?
Yes, they are facts.
The point is the truth. Death to fanboys, death to lies, death to misinformation, death to FUD. Truth FTW!
Is saying "the bug is so rare that even with the fix disabled, it won't affect most user and shouldn't be much of a concern for most user" is not the truth? Is this misinformation?
Firstly don't you want to back up your facts above (OEM refusal and unstable Phenom)?
Here they are:
Wow, that is all that I can say.I did, had to find the article where I read it. It's in Dutch though, but that's not my problem.
They are facts, but they don't give substance to the hollow terms 'rare', 'most users' or 'much of a concern'.
You really don't know HOW rare the bug is, do you? You've not seen it... Is that just your dumb luck, or perhaps it's not happened yet because it's more rare than the few weeks you could possibly have used a K10 so far... but not rare enough to not happen ever during the ownership of a K10.
As for 'most users'... you quote a handful of Phenom owners on a forum... I doubt they'd quantify for 'most users'. In fact, some people actually report that they have managed to reproduce the bug. Factor those in aswell.
As for 'much of a concern'... If you don't encounter the bug, you don't know what the consequences will be... As I say, it's entirely possible that your entire HDD is wiped out. I think that WILL be much of a concern if that happens to an unlucky user. Even a crash at the wrong time could be a big concern.
So my conclusion on the above facts would be way different: Don't buy the CPU, you don't know what will happen without the fix, and the performance with the fix installed is just too disappointing to consider buying the chip at all.
Can you tell for a certain when will a component fail on you? Forget about your entire HDD being wiped out by the bug, I would be more concerned with the HDD itself failing. Forget about a crash at the wrong time, a power outage during critical timing would more of a concern for me. Even when using an UPS, I would still be concerned with a failing PSU that can take other hardwares as well.
So what are you trying to say Scali2? Do you want to meet every single Phenom owner and ask them to test certain things on their computer to see if the bug manifests? If 'rare' and 'much of a concern' is bothering you, maybe you should take the initiative to exactly see how often this bug appears. As far as Im concerned, you are just beating around the bush and making such a big deal out of something that seems insignificant for the regular consumer, Period.
Is the notion of having a buggy CPU bothering you so much? Face the facts, there is no 100% bug-free CPU. Else, I suggest you wait an eternity for one to come out.
And for the record, read this: http://www.xtremesystems.org/forums/showpost.php?p=2654041&postcount=27
So you never had any hardware failure without a warning? Yet you said that you are a long time computer user. Are sure that your Sata controller is that reliable when doing your backup? Do you get any warning before your RAM fails? Btw what most desktop user? 6 out of 10? What level of reliability?All that can be solved with redundancy. Any half-decent mission-critical system will have a redundant PSU and a RAID mirror HDD setup. So virtually any kind of component failure can be taken care of... add to that hot-pluggability, and you have yourself a pretty much failsafe computing environment.
So well, for server systems, the only choice is to have the TLB fix running, but because of the performance impact (especially with VM-related tasks), this makes the CPU bad value for money, which is why the big OEMs refuse to sell it.
Now most desktop users won't require this level of reliability. However, PSUs, HDDs and various other hardware have well-defined reliability specifications. The manufacturer will just quote you with an MTBF and some other info, so you know more or less what to expect, and you can replace the hardware long before you will enter the 'danger zone'. Namely, it's a wear-and-tear issue. The hardware will gradually degrade over time.
With the addition of SMART on HDDs, you will usually be warned long before the HDD will actually start to lose data.
So yes, there is a risk that the hardware may fail, but it is a 'controlled risk'. And you can do scheduled backups etc to keep your data safe.
Back to the TLB issue... Firstly we have NO data on how often the bug occurs... So far we know that some people have been using the CPU for a few weeks... that's all we can go on.
Secondly, there's no way to predict when the bug is going to strike. You can't just say "Oh, today is the day the bug will strike... I'll just enable the fix, and tomorrow I'll be good, and disable it again".
Thirdly, there's no way of telling how the bug will manifest itself. You could have silent data corruption... So even when you are backing up your data, there's no way to guarantee that your documents were actually saved properly the last time you used them, or that they will be backed up properly.
It's just a much bigger risk than using a system with only one PSU and no mirrored RAID. It's not as predictable.
I would never take the risk, and I wouldn't recommend it to anyone else either, if they are at all concerned about their data. I can imagine that if you use your PC only as a gaming console, you might want to run without the fix. You can always just reinstall your games and such, worst that could happen is that you'll lose your savegames.
But if like me, you use valuable documents and sourcecode on your system, you can't really take the risk of any of that corrupting, can you?
Now I can take a random crash, a failing harddrive or PSU or whatever, because I keep backups and all... But the risk that my documents or backups are useless because my CPU decided to bug without telling me about it... no, I'm not going to take it. It would cost WAY more than just investing in a slightly more expensive, but perfectly reliable Q6600 system.
So you never had any hardware failure without a warning?
Yet you said that you are a long time computer user. Are sure that your Sata controller is that reliable when doing your backup? Do you get any warning before your RAM fails?
Btw what most desktop user? 6 out of 10?
What level of reliability?
So what are you trying to say Scali2? Do you want to meet every single Phenom owner and ask them to test certain things on their computer to see if the bug manifests? If 'rare' and 'much of a concern' is bothering you, maybe you should take the initiative to exactly see how often this bug appears. As far as Im concerned, you are just beating around the bush and making such a big deal out of something that seems insignificant for the regular consumer, Period.
Is the notion of having a buggy CPU bothering you so much? Face the facts, there is no 100% bug-free CPU. Else, I suggest you wait an eternity for one to come out.
And for the record, read this: http://www.xtremesystems.org/forums/showpost.php?p=2654041&postcount=27
But that's exactly it. This discussion is focused on the severity of the bug, which for the OEMs, is too much for them to bare. You must understand that even though rare, this kind of bug cannot be present, otherwise, if it occurs, the OEMs will be held responsible and will need to replace the hardware or provide a full compensation. That's bad rep right there and a risk that no money making company, can take. So yes, regular Joe may not be impacted and not even the big customers, that these OEMs supply, but the risk is there and they just can't take it. Can you imagine having to replace or compensate for 1000 or more workstations, because the bug was reported in just one of them ? Extremely bad rep and probably reason enough to end the contract.
ALL CPU have errata that can trigger in very obscure situations. The vast majority of erratum in CPUs are left unfixed, since they are deemed VERY rare or simply aren't significant enough to warrant a fix. However, it does appear the TLB errata happens to be more severe than your average errata.
What are you on? There is a fix available for OEMs too.
Btw to Scali2, you said that OEM refused to sell opteron systems, where is your link to back it up?
What are you on? There is a fix available for OEMs too.
Btw to Scali2, you said that OEM refused to sell opteron systems, where is your link to back it up?
You can no longer configure K10 Opterons via Dell or HP as of now. It seems to me that the problem for servers is serious enough that Dell and HP (and I'd imagine other vendors) basically issued a stop order for K10 Opterons. They are most likely waiting for a new stepping that is coming out Q2 2008.
AMD man Phil Hughes told InternetNews, "It's only a stop ship if it's shipping in volume, and we're only shipping Barcelona for specific customer commitments, like larger volume deployments."
Btw to Scali2, you said that OEM refused to sell opteron systems, where is your link to back it up?
You can no longer configure K10 Opterons via Dell or HP as of now. It seems to me that the problem for servers is serious enough that Dell and HP (and I'd imagine other vendors) basically issued a stop order for K10 Opterons. They are most likely waiting for a new stepping that is coming out Q2 2008.
So only one site tells the truth? And the article even starts with mentioning about IntelExactly. You think it's AMD's choice? Ofcourse not!
The OEMs can only sell a server system with the fix enabled. And that's where the problem is.
The OEMs originally did their validation with the non-fixed platform. The CPUs failed this validation... then it was back to the drawing board for AMD... AMD came up with the TLB fix. However, the OEMs are not taking chances... So they will AGAIN have to go through the validation process before they can sell systems with the TLB fix.
Now the problem is that the TLB fix degrades performance, and it was available far too late.
So the OEMs have decided not to even bother with this fix at all. They will wait for the later stepping, and then they'll validate that one and start selling it, if it validates okay.
So it is these OEMs that caused AMD to stop shipping Opterons.
Then AMD ofcourse wants to tell the media that *they* found the bug, and that *they* decided to cancel shipment... But this is just their spindoctors at work. Dell, HP and other major OEMs tell a different story.Besides, AMD isn't all that credible when they stop shipping Opterons, but still sell Phenoms with the exact same bug. Do any of the major OEMs sell any Phenoms by the way? I don't think I've seen any Dells or HPs with Phenom yet either.
OEMs just face the big problem that they can't sell systems with the fix disabled because of potential stability problems... and they can't sell them with the fix enabled because the performance wouldn't be good value for money. The Spider platform is not very attractive to OEMs at this point.
I don't know why tweakers.net is one of the few sites that actually dares to mention the truth... Perhaps other sites 'depend' on AMD too much.
So only one site tells the truth? And the article even starts with mentioning about Intel![]()
No, none of the C2D errata are as severe as the Phenom one. [. . .] that doesn't make it as unstable as an unpatched Phenom system.
You contradict yourself at every single turn. It really is ridiculous, Scali.Scali2 said:In a way it's misinformation, or rather misleading information, because it's a very vague statement. It's nothing more than an opinion, not based on any quantitative analysis or fact. Words like 'rare', 'most users', 'much of a concern' really don't say anything, and leave it all up to the reader's interpretation.
You contradict yourself at every single turn. It really is ridiculous, Scali.
You say things like "No, none of the C2D errata are as severe as the Phenom one" and "[the C2D is not] as unstable as an unpatched Phenom system," and then turn around and bash others for using fuzzy language. How much more severe is the outcome of hitting the erratum on Phenom vs. C2D? How much more often does the Phenom run into errata than C2D? 1.1x as bad? 1.5x? 2.0x? You have no clue. You haven't done, and do not have access to "any quantitative analysis or fact," as you put it. You're leaving the severity of the error up to the reader and trying to spin it as bad for AMD as you can possibly get away with. I don't see how everyone here is letting you get away with bashing people for doing the exact same thing you yourself are doing.