Intel Corporation (INTC) Message Board

STOCKTALK

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 : Intel Corporation (INTC)

INTC 45.51

+10.7%

Jan 9 9:30 AM EST

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: pgerassi who wrote (142226)	8/27/2001 7:32:33 PM
From: fingolfen	Read Replies (1) of 186894

Wrong! Remember Tom's hardware and the P3-1.13 Linux kernel compilation bug. A 1GHz P3 compiled it just fine and the P3-1.13 failed. Everyone blamed Tom, yet it was repeated by another site. The problem was found with just the new speed grade failing due to a speedpath issue. I told you in my post that this could be, repeat could be, (not is) something similar. He stated that the benchmarks ran with multiple i850 motherboards with a 1.5GHz P4. So the old bin works and the new bin fails. Complaining that something is FUD is how Intel got into trouble both with the FDIV problem and the P3-1.13 problem. Sticking one's head into the sand doesn't fix the problem. AMD did not stick its head into the sand wrt the JPEG problem. They found out what was wrong, added tests to the verification suite to remove those CPUs that exhibit the problem and offer to replace any CPU found with the problem. Just like they (or Intel) should do in those cases. Typical response, shoot the messenger when not to your liking. The tone of your post was NOT a "could be" post, the tone of the post outright stated that this was another 1.13/FDIV problem by jumping immediately to the worst-case scenario. You are not a "messenger." You are presenting a bias and quickly leapt to conclusion based on limited data. I therefore find it very difficult to believe that your motivation is altruistic... Further complicating your conclusion is the fact that the tester in question doesn't believe it's a hardware problem. Data supporting the conclusion that it's most likely a driver issue includes the fact that other testers have noted a fault in this driver. Another interesting piece of data is that Anand, Tom, Sharkey, and others who have tested this chip and have not discovered any hardware issues. ... and it took AMD over TWO YEARS to admit there was any problem with .jpg emulation... hardly a shining counterexample.

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next