• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Intel Haswell TSX Erratum as Grave as AMD Barcelona TLB Erratum

btarunr

Editor & Senior Moderator
Staff member
Joined
Oct 9, 2007
Messages
46,277 (7.69/day)
Location
Hyderabad, India
System Name RBMK-1000
Processor AMD Ryzen 7 5700G
Motherboard ASUS ROG Strix B450-E Gaming
Cooling DeepCool Gammax L240 V2
Memory 2x 8GB G.Skill Sniper X
Video Card(s) Palit GeForce RTX 2080 SUPER GameRock
Storage Western Digital Black NVMe 512GB
Display(s) BenQ 1440p 60 Hz 27-inch
Case Corsair Carbide 100R
Audio Device(s) ASUS SupremeFX S1220A
Power Supply Cooler Master MWE Gold 650W
Mouse ASUS ROG Strix Impact
Keyboard Gamdias Hermes E2
Software Windows 11 Pro
Intel's "Haswell" micro-architecture introduced the transactional synchronization extensions (TSX) as part of its upgraded feature-set over its predecessor. The instructions are designed to speed up certain types of multithreaded software, and although it's too new for any major software vendor to implement, some of the more eager independent software developers began experimenting with them, only to discover that TSX is buggy and can cause critical software failures.

The buggy TSX implementation on Core "Haswell" processors was discovered by a developer outside Intel, who reported it to the company, which then labeled it as an erratum (a known design flaw). Intel is addressing the situation by releasing a micro-code update to motherboard manufacturers, who will then release it as a BIOS update to customers. The update disables TSX on affected products (Core and Xeon "Haswell" retail, and "Broadwell-Y" engineering samples).

TechReport's Scott Wasson draws a parallel between the TSX erratum, and the infamous translation lookaside buffer (TLB) erratum of AMD's "Barcelona" chips, which caused the company to temporarily halt production of its first single-die quad-core Opteron processors, and release similar "performance-impacting" micro-code updates for its consumer Phenom X4 processors. Expect your motherboard vendor to dish out a BIOS update with Intel's micro-code patch very soon.

View at TechPowerUp Main Site
 
Joined
Feb 8, 2012
Messages
3,012 (0.68/day)
Location
Zagreb, Croatia
System Name Windows 10 64-bit Core i7 6700
Processor Intel Core i7 6700
Motherboard Asus Z170M-PLUS
Cooling Corsair AIO
Memory 2 x 8 GB Kingston DDR4 2666
Video Card(s) Gigabyte NVIDIA GeForce GTX 1060 6GB
Storage Western Digital Caviar Blue 1 TB, Seagate Baracuda 1 TB
Display(s) Dell P2414H
Case Corsair Carbide Air 540
Audio Device(s) Realtek HD Audio
Power Supply Corsair TX v2 650W
Mouse Steelseries Sensei
Keyboard CM Storm Quickfire Pro, Cherry MX Reds
Software MS Windows 10 Pro 64-bit
The patch should disable TSX instructions on the CPU and prevent you from blue screening your PC if you are developing a bleeding edge applications using TSX instructions. It's funny how people who are affected are the ones that don't want TSX disabled.
 
Joined
Sep 7, 2011
Messages
2,785 (0.61/day)
Location
New Zealand
System Name MoneySink
Processor 2600K @ 4.8
Motherboard P8Z77-V
Cooling AC NexXxos XT45 360, RayStorm, D5T+XSPC tank, Tygon R-3603, Bitspower
Memory 16GB Crucial Ballistix DDR3-1600C8
Video Card(s) GTX 780 SLI (EVGA SC ACX + Giga GHz Ed.)
Storage Kingston HyperX SSD (128) OS, WD RE4 (1TB), RE2 (1TB), Cav. Black (2 x 500GB), Red (4TB)
Display(s) Achieva Shimian QH270-IPSMS (2560x1440) S-IPS
Case NZXT Switch 810
Audio Device(s) onboard Realtek yawn edition
Power Supply Seasonic X-1050
Software Win8.1 Pro
Benchmark Scores 3.5 litres of Pale Ale in 18 minutes.
"Intel Haswell TSX Erratum as Grave as AMD Barcelona TLB Erratum"

Seems a bit sensationalist doesn't it?
Barcelona's TLB was producing erroneous results in enterprise workloads from day one. As far as I'm aware the only TSX enabled processors are desktop Haswell and whatever Broadwell samples are being sent around...and the grand total of software applications using TSX totals zero.
 
Joined
Aug 22, 2007
Messages
3,450 (0.57/day)
Location
CA, US
System Name :)
Processor Intel 13700k
Motherboard Gigabyte z790 UD AC
Cooling Noctua NH-D15
Memory 64GB GSKILL DDR5
Video Card(s) Gigabyte RTX 4090 Gaming OC
Storage 960GB Optane 905P U.2 SSD + 4TB PCIe4 U.2 SSD
Display(s) Alienware AW3423DW 175Hz QD-OLED + Nixeus 27" IPS 1440p 144Hz
Case Fractal Design Torrent
Audio Device(s) MOTU M4 - JBL 305P MKII w/2x JL Audio 10 Sealed --- X-Fi Titanium HD - Presonus Eris E5 - JBL 4412
Power Supply Silverstone 1000W
Mouse Roccat Kain 122 AIMO
Keyboard KBD67 Lite / Mammoth75
VR HMD Reverb G2 V2
Software Win 11 Pro
"Intel Haswell TSX Erratum as Grave as AMD Barcelona TLB Erratum"

Seems a bit sensationalist doesn't it?
Barcelona's TLB was producing erroneous results in enterprise workloads from day one. As far as I'm aware the only TSX enabled processors are desktop Haswell and whatever Broadwell samples are being sent around...and the grand total of software applications using TSX totals zero.

this

it reeks of flame bait?
 
Joined
Nov 25, 2012
Messages
246 (0.06/day)
Haswell processors below 45xx as well as R-series and K-series (with unlocked multiplier) SKUs do not support TSX.
 
Joined
Sep 6, 2013
Messages
2,973 (0.77/day)
Location
Athens, Greece
System Name 3 desktop systems: Gaming / Internet / HTPC
Processor Ryzen 5 5500 / Ryzen 5 4600G / FX 6300 (12 years latter got to see how bad Bulldozer is)
Motherboard MSI X470 Gaming Plus Max (1) / MSI X470 Gaming Plus Max (2) / Gigabyte GA-990XA-UD3
Cooling Νoctua U12S / Segotep T4 / Snowman M-T6
Memory 16GB G.Skill RIPJAWS 3600 / 16GB G.Skill Aegis 3200 / 16GB Kingston 2400MHz (DDR3)
Video Card(s) ASRock RX 6600 + GT 710 (PhysX)/ Vega 7 integrated / Radeon RX 580
Storage NVMes, NVMes everywhere / NVMes, more NVMes / Various storage, SATA SSD mostly
Display(s) Philips 43PUS8857/12 UHD TV (120Hz, HDR, FreeSync Premium) ---- 19'' HP monitor + BlitzWolf BW-V5
Case Sharkoon Rebel 12 / Sharkoon Rebel 9 / Xigmatek Midguard
Audio Device(s) onboard
Power Supply Chieftec 850W / Silver Power 400W / Sharkoon 650W
Mouse CoolerMaster Devastator III Plus / Coolermaster Devastator / Logitech
Keyboard CoolerMaster Devastator III Plus / Coolermaster Devastator / Logitech
Software Windows 10 / Windows 10 / Windows 7
It's something that it is on every Haswell. It's not really something minor. It could be even worst than TLB bug on Barcelona considering the market share of AMD back then and the market share of Intel today. TSX affects much more people. The difference here is that in the case of Haswell people just don't give a sh!t because Haswell is anyway the fastest cpu available. So disabling something that we haven't seen yet on a processor that it is the fastest available isn't really something that will make someone lose his sleep. On the other hand Barcelona was something that everyone was expecting like the second coming of AMD. Performance wasn't there and the TLB bug was just the icing on the (bad) cake. Making something that wasn't fast enough perform even slower because of a bug was just terrible.

The title in my opinion is justified. It is the conditions that are totally different. It's how the same thing, because of different condition, we look it at two totally different angles some times.
 
Joined
Jun 11, 2008
Messages
576 (0.10/day)
System Name Epsilon
Processor A12-9800E 35watts
Motherboard MSI Grenade AM4
Cooling Stock
Memory 2x4GB DDR4 2400 Kingston Hyper X
Video Card(s) Radeon R7 (IGP / APU)
Storage Samsung Spinpoint F1
Display(s) AOC 29" Ultra wide
Case Generic
Power Supply Antec Earthwatts 380w
Software Windows 10
Barcelona TLB Bug was nasty, however it triggered in rare occasions for the common user.
Haswell TSX bug is stupid. As if Intel didn't have enough to make their things right... c'mon intel...
 
Joined
Feb 18, 2005
Messages
5,239 (0.75/day)
Location
Ikenai borderline!
System Name Firelance.
Processor Threadripper 3960X
Motherboard ROG Strix TRX40-E Gaming
Cooling IceGem 360 + 6x Arctic Cooling P12
Memory 8x 16GB Patriot Viper DDR4-3200 CL16
Video Card(s) MSI GeForce RTX 4060 Ti Ventus 2X OC
Storage 2TB WD SN850X (boot), 4TB Crucial P3 (data)
Display(s) 3x AOC Q32E2N (32" 2560x1440 75Hz)
Case Enthoo Pro II Server Edition (Closed Panel) + 6 fans
Power Supply Fractal Design Ion+ 2 Platinum 760W
Mouse Logitech G602
Keyboard Logitech G613
Software Windows 10 Professional x64
When I saw the title I had to check if I was on SemiAccurate. I'd expect this sort of fear-mongering click-baiting headline from ol' Charlie, not TPU. Factually, the bug affects far fewer people than the TLB bug ever did, which makes it far less serious.

TSX affects much more people.

Show me a piece of commercial software that uses TSX? Right, you can't, because such software doesn't exist. TSX is too niche and too new to have such support. And it doesn't affect the performance of any applications, except those that are written explictly to use it... which is a very low number.

On the other hand, the Bulldozer TLB bug "fix" affected ALL software - anyone who bought an AMD CPU with the TLB bug, experienced reduced performance overall.

The difference here is that in the case of Haswell people just don't give a sh!t because Haswell is anyway the fastest cpu available.

No, we don't give a s**t because there's no reason to. The ordinary users who make up 99.999999% of Haswell's marketshare will never use TSX, so they won't be affected.

Haswell TSX bug is stupid. As if Intel didn't have enough to make their things right... c'mon intel...

TSX has been around since 2012 and hasn't seen wide adoption. Designing silicon is difficult. Put the two together and it's not difficult to figure out how a bug like this could get into production silicon.
 
Joined
Apr 29, 2014
Messages
4,180 (1.15/day)
Location
Texas
System Name SnowFire / The Reinforcer
Processor i7 10700K 5.1ghz (24/7) / 2x Xeon E52650v2
Motherboard Asus Strix Z490 / Dell Dual Socket (R720)
Cooling RX 360mm + 140mm Custom Loop / Dell Stock
Memory Corsair RGB 16gb DDR4 3000 CL 16 / DDR3 128gb 16 x 8gb
Video Card(s) GTX Titan XP (2025mhz) / Asus GTX 950 (No Power Connector)
Storage Samsung 970 1tb NVME and 2tb HDD x4 RAID 5 / 300gb x8 RAID 5
Display(s) Acer XG270HU, Samsung G7 Odyssey (1440p 240hz)
Case Thermaltake Cube / Dell Poweredge R720 Rack Mount Case
Audio Device(s) Realtec ALC1150 (On board)
Power Supply Rosewill Lightning 1300Watt / Dell Stock 750 / Brick
Mouse Logitech G5
Keyboard Logitech G19S
Software Windows 11 Pro / Windows Server 2016
Things happen and Intel is cleaning it up, not that big a deal...
 

eidairaman1

The Exiled Airman
Joined
Jul 2, 2007
Messages
40,435 (6.61/day)
Location
Republic of Texas (True Patriot)
System Name PCGOD
Processor AMD FX 8350@ 5.0GHz
Motherboard Asus TUF 990FX Sabertooth R2 2901 Bios
Cooling Scythe Ashura, 2×BitFenix 230mm Spectre Pro LED (Blue,Green), 2x BitFenix 140mm Spectre Pro LED
Memory 16 GB Gskill Ripjaws X 2133 (2400 OC, 10-10-12-20-20, 1T, 1.65V)
Video Card(s) AMD Radeon 290 Sapphire Vapor-X
Storage Samsung 840 Pro 256GB, WD Velociraptor 1TB
Display(s) NEC Multisync LCD 1700V (Display Port Adapter)
Case AeroCool Xpredator Evil Blue Edition
Audio Device(s) Creative Labs Sound Blaster ZxR
Power Supply Seasonic 1250 XM2 Series (XP3)
Mouse Roccat Kone XTD
Keyboard Roccat Ryos MK Pro
Software Windows 7 Pro 64
I find it funny that people are downplaying this problem like intel is a saint. This is big enough of a problem that Intel is releasing a patch...
 
Joined
Sep 7, 2011
Messages
2,785 (0.61/day)
Location
New Zealand
System Name MoneySink
Processor 2600K @ 4.8
Motherboard P8Z77-V
Cooling AC NexXxos XT45 360, RayStorm, D5T+XSPC tank, Tygon R-3603, Bitspower
Memory 16GB Crucial Ballistix DDR3-1600C8
Video Card(s) GTX 780 SLI (EVGA SC ACX + Giga GHz Ed.)
Storage Kingston HyperX SSD (128) OS, WD RE4 (1TB), RE2 (1TB), Cav. Black (2 x 500GB), Red (4TB)
Display(s) Achieva Shimian QH270-IPSMS (2560x1440) S-IPS
Case NZXT Switch 810
Audio Device(s) onboard Realtek yawn edition
Power Supply Seasonic X-1050
Software Win8.1 Pro
Benchmark Scores 3.5 litres of Pale Ale in 18 minutes.
I find it funny that people are downplaying this problem like intel is a saint. This is big enough of a problem that Intel is releasing a patch...
No really. The error has been found before any harm was done since no TSX workloads are in use. It comes under the heading of annoying and costly for Intel who will no doubt be sending a lot of Haswell-E CPUs to a recycling facility, but in the end, the consumer is aware of the issue before they ever have cause to be affected by it.
Kind of sucks if you bought Haswell because of the TSX extension, but I'm picking most people don't even know what it is let alone have it on their must have list.
It's something that it is on every Haswell. It's not really something minor. It could be even worst than TLB bug on Barcelona considering the market share of AMD back then and the market share of Intel today.
That doesn't make a great deal of sense to me. Overall market share has nothing to do with it - even market shares comparing Haswell users to Opteron users (while more relevant - I don't believe Haswell owners make up the 14.6% of their market that Opteron did in Q4 2007). AMD had to cease in-progress shipments of flagship enterprise part that was causing errors in current workloads.
TSX affects much more people.
How can it affect more people when there is no software that could take advantage of TSX even if it were available?
The difference here is that in the case of Haswell people just don't give a sh!t because Haswell is anyway the fastest cpu available.
No, they don't (maybe) give a sh!t because they couldn't use TSX in any case.
So disabling something that we haven't seen yet on a processor that it is the fastest available isn't really something that will make someone lose his sleep.
More to the point, disabling something you couldn't use anyway doesn't make the bug a dealbreaker for most people.
On the other hand Barcelona was something that everyone was expecting like the second coming of AMD. Performance wasn't there and the TLB bug was just the icing on the (bad) cake. Making something that wasn't fast enough perform even slower because of a bug was just terrible.
And that is another very large distinction. Disabling TSX doesn't affect performance using other ISA extensions, where the workaround for the TLB bug for Barcelona came at a ~5-20% performance penalty.
 
Last edited:
Joined
Sep 7, 2011
Messages
2,785 (0.61/day)
Location
New Zealand
System Name MoneySink
Processor 2600K @ 4.8
Motherboard P8Z77-V
Cooling AC NexXxos XT45 360, RayStorm, D5T+XSPC tank, Tygon R-3603, Bitspower
Memory 16GB Crucial Ballistix DDR3-1600C8
Video Card(s) GTX 780 SLI (EVGA SC ACX + Giga GHz Ed.)
Storage Kingston HyperX SSD (128) OS, WD RE4 (1TB), RE2 (1TB), Cav. Black (2 x 500GB), Red (4TB)
Display(s) Achieva Shimian QH270-IPSMS (2560x1440) S-IPS
Case NZXT Switch 810
Audio Device(s) onboard Realtek yawn edition
Power Supply Seasonic X-1050
Software Win8.1 Pro
Benchmark Scores 3.5 litres of Pale Ale in 18 minutes.
I wonder if it's too late to fix on Broadwell.
The TSX bug is fixable, it would however need a silicon respin.
For the Broadwell's already circulating (Broadwell-Y) ? No, but I think only OEM's have them for validation at the moment.
From the Intel spokesflunky's wording, the reason for the bug has been found, so it just comes down to how quickly new lithography masks can be set up and the 8-12 weeks for fabbing the chips. Depends on how serious Intel view the bug as to when it's implemented. If it's serious then they'd likely get on to it quickly and the new chips will receive new sSpec codes at the very least.
 
Joined
Jan 12, 2012
Messages
73 (0.02/day)
Location
New York
System Name Build # 5
Processor I9-9900K
Motherboard ASUS-ROG Maximus XI Hero wifi
Cooling Cosair H100i aio
Memory G.SKILL 128GB (4 x 32GB) TridentZ RGB Series DDR4 PC4-21300 2666MHz Intel XMP 2.0
Video Card(s) EVGA RTX-3090 FTW3
Storage XPG S40G 2TB RGB Nand Gen3x4 NVMe
Display(s) LG-65CX-Oled
Case Corsair CC-9011030-WW Carbide Series Air 540 High Airflow ATX Cube Case - Black
Audio Device(s) EVGA Nu Audio card & BOSE Quietcomfort 35 II headphones
Power Supply CORSAIR-HX-1050
Software WIN 10/64

boberino

New Member
Joined
Jan 11, 2014
Messages
3 (0.00/day)
Intel's "Haswell" micro-architecture introduced the transactional synchronization extensions (TSX) as part of its upgraded feature-set over its predecessor. The instructions are designed to speed up certain types of multithreaded software, and although it's too new for any major software vendor to implement, some of the more eager independent software developers began experimenting with them, only to discover that TSX is buggy and can cause critical software failures.

The buggy TSX implementation on Core "Haswell" processors was discovered by a developer outside Intel, who reported it to the company, which then labeled it as an erratum (a known design flaw). Intel is addressing the situation by releasing a micro-code update to motherboard manufacturers, who will then release it as a BIOS update to customers. The update disables TSX on affected products (Core and Xeon "Haswell" retail, and "Broadwell-Y" engineering samples).

TechReport's Scott Wasson draws a parallel between the TSX erratum, and the infamous translation lookaside buffer (TLB) erratum of AMD's "Barcelona" chips, which caused the company to temporarily halt production of its first single-die quad-core Opteron processors, and release similar "performance-impacting" micro-code updates for its consumer Phenom X4 processors. Expect your motherboard vendor to dish out a BIOS update with Intel's micro-code patch very soon.

Source: TechReport

TechReport's Scott Wasson said this:

Also, because the problem is apparently restricted to the use of TSX instructions, this erratum isn't likely to prompt the sort of dire consequences the TLB erratum in AMD's Barcelona chip did. As we exclusively reported at the time, the Barcelona TLB problem caused AMD to stop the shipment of Opteron processors and issue a performance-impacting microcode patch for consumer Phenom CPUs. By contrast, the most unfortunate impact of this TSX erratum may be to slow the development of TSX-capable software.

Any chance you can help my understand why I shouldn't chalk this up to another misrepresentation of a regurgitated article?
 
Last edited:
Joined
Nov 4, 2005
Messages
11,655 (1.73/day)
System Name Compy 386
Processor 7800X3D
Motherboard Asus
Cooling Air for now.....
Memory 64 GB DDR5 6400Mhz
Video Card(s) 7900XTX 310 Merc
Storage Samsung 990 2TB, 2 SP 2TB SSDs and over 10TB spinning
Display(s) 56" Samsung 4K HDR
Audio Device(s) ATI HDMI
Mouse Logitech MX518
Keyboard Razer
Software A lot.
Benchmark Scores Its fast. Enough.
TechReport's Scott Wasson said this:



Any chance you can help my understand why I shouldn't chalk this up to another misrepresentation of a regurgitated article?
http://www.anandtech.com/show/6290/...ll-transactional-synchronization-extensions/4

How about all the companies that may have purchased Haswell hardware with the intention of using it to improve database performance, along with other time sensitive software performance, and now.....can't.

http://www.anandtech.com/show/6290/...well-transactional-synchronization-extensions


Like banks, and like most of all other financial institutions, where consumers are demanding faster deposit, transfer, and availability times, which requires...... you guessed it, faster database processing for millions of transactions per hour.

Good troll post asshat.
 
Joined
Sep 7, 2011
Messages
2,785 (0.61/day)
Location
New Zealand
System Name MoneySink
Processor 2600K @ 4.8
Motherboard P8Z77-V
Cooling AC NexXxos XT45 360, RayStorm, D5T+XSPC tank, Tygon R-3603, Bitspower
Memory 16GB Crucial Ballistix DDR3-1600C8
Video Card(s) GTX 780 SLI (EVGA SC ACX + Giga GHz Ed.)
Storage Kingston HyperX SSD (128) OS, WD RE4 (1TB), RE2 (1TB), Cav. Black (2 x 500GB), Red (4TB)
Display(s) Achieva Shimian QH270-IPSMS (2560x1440) S-IPS
Case NZXT Switch 810
Audio Device(s) onboard Realtek yawn edition
Power Supply Seasonic X-1050
Software Win8.1 Pro
Benchmark Scores 3.5 litres of Pale Ale in 18 minutes.
How about all the companies that may have purchased Haswell hardware with the intention of using it to improve database performance, along with other time sensitive software performance, and now.....can't. Like banks, and like most of all other financial institutions, where consumers are demanding faster deposit, transfer, and availability times, which requires...... you guessed it, faster database processing for millions of transactions per hour.
Like banks? When was the last time you saw a big company server or datacentre using consumer desktop CPUs ?
AFAIK, enterprise systems will continue to be Xeon E5 (Grantley) and E7 (Brickland). The former might initially be affected, but since their launches will be staggered its probably a safe bet that not all will be. The E7 line (Haswell-EX - which is being pushed as the cloud computing big data SKU's) will have TSX enabled.
Good troll post asshat.
Given your argument isn't exactly watertight how about toning down the insults?
 
Joined
Aug 10, 2007
Messages
4,267 (0.70/day)
Location
Sanford, FL, USA
Processor Intel i5-6600
Motherboard ASRock H170M-ITX
Cooling Cooler Master Geminii S524
Memory G.Skill DDR4-2133 16GB (8GB x 2)
Video Card(s) Gigabyte R9-380X 4GB
Storage Samsung 950 EVO 250GB (mSATA)
Display(s) LG 29UM69G-B 2560x1080 IPS
Case Lian Li PC-Q25
Audio Device(s) Realtek ALC892
Power Supply Seasonic SS-460FL2
Mouse Logitech G700s
Keyboard Logitech G110
Software Windows 10 Pro
Guess I'll be holding off on my Haswell purchase. Kind of like when I didn't purchase those Opterons and instead bought Xeon systems :twitch:

The degree of effect these bugs have on computing is only half the discussion as to whether or not they are equally grave. They are not given the circumstances, but in my case resulted in similar ends. That matters most to a bottom-line company such as Intel.

Now, will the bottom-line be affected equally? Probably not, given that Intel has the experience and resources to make a speedy recovery while keeping a happy face about it. Just saying that this this aspect should not be forgotten as other companies are not as lucky as Intel. Their underestimation has lead to much dire consequences.
 

boberino

New Member
Joined
Jan 11, 2014
Messages
3 (0.00/day)
http://www.anandtech.com/show/6290/...ll-transactional-synchronization-extensions/4

How about all the companies that may have purchased Haswell hardware with the intention of using it to improve database performance, along with other time sensitive software performance, and now.....can't.

http://www.anandtech.com/show/6290/...well-transactional-synchronization-extensions


Like banks, and like most of all other financial institutions, where consumers are demanding faster deposit, transfer, and availability times, which requires...... you guessed it, faster database processing for millions of transactions per hour.

Good troll post asshat.

Since you do not appear to comprehend the point and purpose of my post I will clarify instead of reciprocating your "asshat" comment.

btarunr used TechReport as the source and quoted content from the article in his repost. My problem is the fact that the headline doesn't match the article specified and quoted as the source. If btarunr wanted to use that headline he needed to find different/additional reference material. This is not the first time a news piece at TPU has had an unqualified and unrelated headline as clickbait. And like the last time I had already read the source material prior to seeing his repost and was scratching my head as to how someone came up with that headline from the content that was sourced.
 
Joined
Nov 4, 2005
Messages
11,655 (1.73/day)
System Name Compy 386
Processor 7800X3D
Motherboard Asus
Cooling Air for now.....
Memory 64 GB DDR5 6400Mhz
Video Card(s) 7900XTX 310 Merc
Storage Samsung 990 2TB, 2 SP 2TB SSDs and over 10TB spinning
Display(s) 56" Samsung 4K HDR
Audio Device(s) ATI HDMI
Mouse Logitech MX518
Keyboard Razer
Software A lot.
Benchmark Scores Its fast. Enough.
Like banks? When was the last time you saw a big company server or datacentre using consumer desktop CPUs ?
AFAIK, enterprise systems will continue to be Xeon E5 (Grantley) and E7 (Brickland). The former might initially be affected, but since their launches will be staggered its probably a safe bet that not all will be. The E7 line (Haswell-EX - which is being pushed as the cloud computing big data SKU's) will have TSX enabled.

Given your argument isn't exactly watertight how about toning down the insults?
http://www.newegg.com/Product/Product.aspx?Item=N82E16819116908

They are already out, and have the errata.
http://www.pcworld.com/article/2464...enterprise-bug-on-haswell-broadwell-cpus.html

As does Broadwell (E5), so the new enterprise chips are going to have it until Intel finds a hardware fix. OEM's already have the chips. So we have hardware in the wild, production systems being built, that cannot support a new feature that was being pushed. For those who have based their purchasing decision on this, its going to suck, will the OEM or Intel provide new chips to those people, it wouldn't be the first time Intel has had to do that, although the last time was perhaps before you were born.

My asshat comment was about critiquing of an article title, if you find it to be clickbait, go elsewhere, or do research on the topic and realize it is something show stopping for end users and OEM's.

http://techreport.com/news/26911/errata-prompts-intel-to-disable-tsx-in-haswell-early-broadwell-cpus

Intel doesn't have a current timeline for the fix, and really considering how much complexity it takes and improvement it was offering they might not be able to implement an actual full fix, perhaps limiting the number of threads or cores that can use it.

Also, damn that is a long list of broken things, 5 pages

http://www.intel.com/content/dam/ww...cation-updates/xeon-e3-1200v3-spec-update.pdf
 
Joined
Apr 10, 2012
Messages
1,400 (0.32/day)
Location
78°55' N, 11°56' E
System Name -aLiEn beaTs-
Processor Intel i7 11700kf @ 5.055Ghz
Motherboard MSI Z490 Unify
Cooling Corsair H115i Pro RGB
Memory G.skill Royal Silver 4400 cl17 @ 4403mhz
Video Card(s) Zotac GTX 980TI AMP!Omega Factory OC 1418MHz
Storage Intel SSD 330, Crucial SSD MX300 & MX500
Display(s) Samsung C24FG73 144HZ
Case CoolerMaster HAF 932 USB3.0
Audio Device(s) X-Fi Titanium HD @ 2.1 Bose acoustimass 5
Power Supply CoolerMaster 850W v2 gold atx 2.52
Mouse Razer viper 8k
Keyboard Logitech G19s
Software Windows 11 Pro 21h2 64Bit
Benchmark Scores ► ♪♫♪♩♬♫♪♭
Yeah all Haswells and DC and new not yet released Haswell-E will have it disabled with microcode bios update..

Apparently normal Broadwell-DT will be fixed.
 
Top