Live data from Hacker News

July 2024 Update on Instability Reports on Intel Core 13th/14th Gen Desktop CPUs

community.intel.com

191–200 of 216 posts

Re: July 2024 Update on Instability Reports on Intel Core 13th/14th Gen Desktop CPUs

#191

Earlier quoted context omitted.

It’s a common strategy for small tasks where the overhead of dispatching the task greatly exceeds the computation of it. It’s also a better way to maximize L1/L2 cache hit rates by improving memory locality. Eg you have 100M rows and you want to cluster them by a distance function (naively), running dist(arr[i], arr[j]) is crazy fast, the problem is just that you have so many of them. It is faster to run it on one co…

It has always been a bad idea to dispatch so naively and dispatch to the same number of threads as you have cores. What if a couple cores are busy, and you spend almost twice as much time as you need waiting for the calculation to finish? I don't know how much software does that, and most of it can be easily fixed to dispatch half a million rows at a time and get better performance on all computers. Also on current C…

> What if a couple cores are busy

If you don't pin them to cores, the OS is still free to assign threads to cores as it pleases. Assuming the scheduler is somewhat fair, threads will progress at roughly the same rate.

Re: July 2024 Update on Instability Reports on Intel Core 13th/14th Gen Desktop CPUs

#192
post #165
post #134

Earlier quoted context omitted.

Why are you downplaying it too? > "The laptops crash in the exact same way as the desktop parts including workloads under Unreal Engine, decompression, ycruncher or similar. Laptop chips we have seen failing include but not limited to 13900HX etc.," Cassells said. > "Intel seems to be down playing the issues here most likely due to the expensive costs related to BGA rework and possible harm to OEMs and Partners," he…

Alderon are the people claiming 100% of units fail which doesn’t seem supported by anyone else either. Wendell and GN seem to have scoped the issue to around 10-25% across multiple different sources. Like they are the most extreme claimants at this point. Are they really credible?

Ok, I take it back, this looks pretty indicative of a low-load problem and evidently failure rates are much higher in that scenario.

https://www.youtube.com/watch?v=yYfBxmBfq7k

Re: July 2024 Update on Instability Reports on Intel Core 13th/14th Gen Desktop CPUs

#193
post #86

Earlier quoted context omitted.

yeah wendell put out a video a few weeks ago exploring a bunch of problems with asrock rack-branded server-market B650 motherboards and basically the ECC situation was exactly what everyone warns about: the various BIOS versions wandered between "works, but doesn't forward the errors", "doesn't work, and doesn't forward the errors", and (excitingly) "doesn't work and doesn't even post". We are a year and a half after…

The new EPYC processors for AM5 though look like they'll be ok for ECC ram though, at least in the coming months onwards.

Yeah I think that’s the bright spot, now that there’s a branded offering for server-flavored Ryzen now maybe there is a permanent justification for doing proper validation.

I just feel vindicated lol, it always comes up that “well works fine for me!” and the reality is it’s a total crapshoot with even server-branded boards often not working. There is zero chance your gigabyte UD3 or whatever is going to be consistently supported across bios and often it will not be.

And AMD is really really tied to AGESA releases, so it’s fairly important on that side. Although I guess maybe we’re seeing now what happens if you let too much be abstracted away… but on the other hand partners were blowing up AMD chips last year too.

If you’re comfortable always testing, and always having the possibility of there being some big AGESA problem and ecc being broken on the new versions… ok I guess.

There is a reason the i3 chips were perennial favorites for edge servers and NASs. And I think it's really, really hard to overstate the long-term damage from reputation loss here. Intel, meltdown aside, was always no-drama in terms of reliability. Other than C2000/C3000, I guess.

Re: July 2024 Update on Instability Reports on Intel Core 13th/14th Gen Desktop CPUs

#194
post #179

Earlier quoted context omitted.

It's most likely both a hardware issue and a microcode issue. Making CPUs is kind-of like sorting eggs. When they're made, they all have slightly different characteristics and get placed into bins (IE, "binned") based on how they meet the specs. To oversimplify, the cough "better" chips are sold at higher prices because they can run at higher clock speeds and/or handle higher voltages. If there's a spec of dust on th…

> If there's a spec of dust on the die, a feature gets turned off and the chip is sold for a lower price. Do you mean that if a 13900KS CPU has a manufacturing defect, it gets downgraded and sold as 13900F or something else according to the nature of the defect?

Yes. It’s called the silicon lottery.

Re: July 2024 Update on Instability Reports on Intel Core 13th/14th Gen Desktop CPUs

#195

Earlier quoted context omitted.

Could you elaborate on the process people versus product people?

It is an old theory that accurately points out Marketing/Sales division people inevitably out-compete product innovation people in a successful firm. https://en.wikipedia.org/wiki/Competitive_exclusion_principl... And yes, the Steve Jobs interview does document how this almost destroyed Apples core business. =)

Just to clarify do you mean employees marketing and selling their innovation skills or people literally in marketing and sales?

Re: July 2024 Update on Instability Reports on Intel Core 13th/14th Gen Desktop CPUs

#196
post #130

Earlier quoted context omitted.

It's complicated. On Raptor lake, there are a few integrated voltage regulators to which provide new voltages for specialised uses (like the E core's L2 cache, parts of DDR memory IO, PCI-E IO), but the current draw on those regulators is pretty low. The bulk of the power comes directly from motherboard VRMs on one of several rails with no internal regulation. Most of the power draw is grouped onto just two rails, Vc…

What's special about the E core's L2 cache such that it gets on-chip regulated voltage?

I suspect it's for one of the low power modes.

Keep in mind that the L2 cache is the last level cache for the E cores, and is shared by the entire cluster of four E cores. (One of the two clusters connects to the ring bus and shares the main L3, the other goes directly to main memory)

I'm guessing Intel can shut down VccCore entirely (which wipes every other cache), while keeping just enough voltage to maintain the E core L2 cache. By keeping valid data in L2, they can resume execution on an E core much quicker.

And as long as the reason for waking is a small periodic housekeeping task, they don't even need to wake up main memory. All the data fits in the 2MB of L2 cache. This makes resuming even faster and saves even more power. Finally, quick resumes allow the task to complete quicker and shut down VccCore again, which saves even more power.

This extreme level of power saving isn't really useful for desktops, but very useful for laptops and tablets. BTW, I'm not talking about a sleep mode here, the CPU will ideally be able to enter this mode anytime there is no tasks to run for at least the next millisecond, so it can save power even when the user is actively using the system.

Re: July 2024 Update on Instability Reports on Intel Core 13th/14th Gen Desktop CPUs

#197

Earlier quoted context omitted.

It has always been a bad idea to dispatch so naively and dispatch to the same number of threads as you have cores. What if a couple cores are busy, and you spend almost twice as much time as you need waiting for the calculation to finish? I don't know how much software does that, and most of it can be easily fixed to dispatch half a million rows at a time and get better performance on all computers. Also on current C…

> What if a couple cores are busy If you don't pin them to cores, the OS is still free to assign threads to cores as it pleases. Assuming the scheduler is somewhat fair, threads will progress at roughly the same rate.

I would not assume it's sufficiently fair to make that a good algorithm.

Even a small bias could turn a 5 minute calculation into a 6 or 7 minute calculation as the stragglers finish up.

Re: July 2024 Update on Instability Reports on Intel Core 13th/14th Gen Desktop CPUs

#198
post #193

Earlier quoted context omitted.

The new EPYC processors for AM5 though look like they'll be ok for ECC ram though, at least in the coming months onwards.

Yeah I think that’s the bright spot, now that there’s a branded offering for server-flavored Ryzen now maybe there is a permanent justification for doing proper validation. I just feel vindicated lol, it always comes up that “well works fine for me!” and the reality is it’s a total crapshoot with even server-branded boards often not working. There is zero chance your gigabyte UD3 or whatever is going to be consistent…

...and puma and i-225V chipsets.

or at least... maybe on the CPU side they were no-drama. Other than C2000/C3000. Granted the powervr graphics on the atoms way back did suck... and meltdown... and avx-512 being rolled back... /phillip j fry counting on his fingers

maybe "blue-chip coded" is a better way to express it ig

but like, there is a notable decline in the quality of execution of intel overall, pretty much across the board, and cpu was always their core vertical, right? That was their business redoubt. intel is blue chip chips, especially CPUs. And now it's falling - really it's been falling for a while. Meltdown I can generally excuse (yes, shush), nobody appreciated sidechannels back then even if they were theoretically known. C2000/C3000 is another fuckup. yeah it's the super-io/serial bus controller... technically not their IP but it happens to be in a critical path, on their node, killing their processor. They fucked up the validation there, evidently.

I-225V had three steppings and I-226V is still not fully fixed (windows/linux have just turned off the EEE/802.11az feature instead). Puma was a god damned mess.

Sapphire rapids was late, still a huge mess, and actually the -W platform had not only insane power draw, but also insaner transients. 750W average, spiking up to 1500W under load, with pretty steep holdup requirements. And actually that was locked behind a "water cooled" bios option, the processor just "refused to all-core turbo" otherwise. And Intel didn't wanna actually say that the "water cooled" behavior was the spec or intentional turbo limits etc. In hindsight hmmm, that all took a bit of a different tone, didn't it?

Supposedly there is going to be a SPR-W refresh with a new stepping to fix this... emerald rapids is also very power-hungry and there were some unconfirmed murmurs suggesting it might have the same crash problems.

(yes, yes, please just listen to the guest here.) https://www.youtube.com/watch?v=_HJu5xt43iQ&t=3603s

https://wccftech.com/intel-xeon-w-3500-w-2500-sapphire-rapid...

Intel's in some real danger especially with AMD ascendant like this. Like it doesn't take very long of this real damage to customers etc and that "we're blue-chip!" thing will cease to be, and that is the last prop keeping intel's finances above the water here. Sure, it will take a while to fully wind down but... this is a great example of how intel's fuckups are driving their clients literally into the arms of the competition. A month or two ago, Asrock Rack didn't give a shit about the B650-2L2T or whatever. Guess what? Now Epyc Mini exists and oems are going to be paying attention to that. Oops.

Re: July 2024 Update on Instability Reports on Intel Core 13th/14th Gen Desktop CPUs

#199
post #198
post #193

Earlier quoted context omitted.

Yeah I think that’s the bright spot, now that there’s a branded offering for server-flavored Ryzen now maybe there is a permanent justification for doing proper validation. I just feel vindicated lol, it always comes up that “well works fine for me!” and the reality is it’s a total crapshoot with even server-branded boards often not working. There is zero chance your gigabyte UD3 or whatever is going to be consistent…

...and puma and i-225V chipsets. or at least... maybe on the CPU side they were no-drama. Other than C2000/C3000. Granted the powervr graphics on the atoms way back did suck... and meltdown... and avx-512 being rolled back... /phillip j fry counting on his fingers maybe "blue-chip coded" is a better way to express it ig but like, there is a notable decline in the quality of execution of intel overall, pretty much acr…

> I-226V is still not fully fixed

Damn, didn't realise that was still being problematic too. :(

And yeah, Intel's current stumble with 13th/14th gen cpus seems like worst possible timing for such an extreme fuck up. That's not going to go well for future planning/purchase decisions by business customers.

Re: July 2024 Update on Instability Reports on Intel Core 13th/14th Gen Desktop CPUs

#200
post #179

Earlier quoted context omitted.

It's most likely both a hardware issue and a microcode issue. Making CPUs is kind-of like sorting eggs. When they're made, they all have slightly different characteristics and get placed into bins (IE, "binned") based on how they meet the specs. To oversimplify, the cough "better" chips are sold at higher prices because they can run at higher clock speeds and/or handle higher voltages. If there's a spec of dust on th…

> If there's a spec of dust on the die, a feature gets turned off and the chip is sold for a lower price. Do you mean that if a 13900KS CPU has a manufacturing defect, it gets downgraded and sold as 13900F or something else according to the nature of the defect?

It's way more extreme than that.

For any named product (such as Raptor Lake) intel only make 1-3 unique silicon dies. Any product in the Alder Lake only had two dies, 8P+8E and 6P+0E [1]. Every single SKU comes from those two dies, if it has E cores, it's the 8P+8E die. Which means Alder Lake-N is actually the 8P+8E dies with all the P cores disabled.

The laptop versions, Alder Lake-P (20w) and Alder Lake-U (9 and 15w) are also the 8P+8E die, they couldn't use the 6P+0E die, because it has no E cores at all.

Raptor Lake is only one die with 8 P cores and 16 E cores, which they sell as every i9 and i7, along with the two top i5 designs. In the 13th generation, the remaining i5s are the Alder Lake 8P+8E die and the i3s are all Alder Lake 6P+0E dies.

The manufacturing defects aren't binary, it's not a simple pass/fail. It's all very analog: Some dies are simply able to reach higher clock speeds, or use more or less power. They test every single die and bin it based on its capabilities. The ones with the best power consumption go to the P and U SKUs. The ones which can reach the highest clock speeds are labeled as 13900KS, dies which just miss that get sold as 13900K, the rest get spread over all remaining SKUs based on their capabilities.

Intel couldn't decide to exclusively make 13900KS dies if they wanted to, because they are simply the top 0.1% of dies. They are forced to make 1000 dies, use the best one and sell the rest as lower SKUs.

[1] Wikichip has photos of the two dies: https://en.wikichip.org/wiki/intel/microarchitectures/alder_...

Post reply on HN