this post was submitted on 24 Jul 2024

232 points (98.3% liked)

Technology

60052 readers

3184 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 2 years ago

MODERATORS

232

AMD delays its Ryzen 9000 launch due to unspecified quality issue — new launch in August; chipmaker pulls back all units shipped globally for quality checks (www.tomshardware.com)

submitted 5 months ago by floofloof@lemmy.ca to c/technology@lemmy.world

31 comments fedilink hide all child comments

top 31 comments

sorted by: hot top controversial new old

[–] ichbinjasokreativ@lemmy.world 80 points 5 months ago (1 children)

Makes sense for two reasons: They show everyone that they don't push faulty hardware, unlike intel and they also delay the launch until after intel push their microcode update to 'fix' their high-end models, which will reduce performance. Ryzen 9000 will look even better in day one performance comparisons.

[–] hohoho@lemmy.world 2 points 5 months ago (2 children)

I’ve been following the Intel story closely. Watched the Gamers Nexus vids. Did I miss it or has it been reported that microcode updates will definitely degrade performance?

[–] bossjack@lemmy.world 8 points 5 months ago (1 children)

It's not confirmed. Its just pessimism, albeit very well argued and precedented.

[–] sugar_in_your_tea@sh.itjust.works 6 points 5 months ago

Yup, the "fix" seems to be to limit boost to 5.3GHz or so, and there may be other mitigations as well. If it has anything to do with branch prediction or other eager optimizations, we could see further degradations like with the fixes for Spectre and other attacks.

[–] Linkerbaan@lemmy.world 1 points 5 months ago

Voltages are probably too high. With lower voltages they very likely won't be able to hit the same clockspeeds.

[–] Peffse@lemmy.world 66 points 5 months ago (1 children)

Intel announces two generations of defective processors and AMD gives up that opportunity to recall their own launch? Must be something very wrong with the batch.

[–] empireOfLove2@lemmy.dbzer0.com 148 points 5 months ago (1 children)

I'd say it's actually a better market signal rather than indications of huge problems. "See, our competitiors send out defective products; we are holding back to make sure ours ship correctly."

That's exactly what enterprise/datacenter customers want to hear: a dedication to stability.

[+] lemmeout@lemm.ee -73 points 5 months ago (4 children)

Nah something fishy

[–] AdamEatsAss@lemmy.world 39 points 5 months ago (1 children)

Any large scale manufacturer like AMD knows about what % of defective returns they get. They're using the heat on Intel to help make their numbers look better.

[–] lemmeout@lemm.ee 24 points 5 months ago (1 children)

Actually, I think it's not about defect numbers. This is about delaying until Intel releases the microcode update. They want to be compared after the (potentially) performance tanking update from Intel. Which is hilarious because Intel gave a date after AMD's initial launch date.

I think it's also fair as a lot of reviewers aren't going to bother retesting after Intel releases updates and comparing with AMD after the 9000 series hype has died down, if they had just recently did so for the AMD launch.

[–] DacoTaco@lemmy.world -4 points 5 months ago* (last edited 5 months ago) (1 children)

... You just contradicted yourself there with the timeline/dates lol.
Wait for intel patch, but release date of cpus is before the expected release date of the microcode patch.

[–] AnyOldName3@lemmy.world 7 points 5 months ago (1 children)

You've misunderstood. The original release date was set, then Intel announced the microcode update, which was after the original release date, then AMD announced that they'd be delaying the release date, and that new release date is after the microcode update.

[–] DacoTaco@lemmy.world 2 points 5 months ago (1 children)

Ah, you meant original release date of the amd cpus.
Ye, makes sense.
I personally think they wanted to verify to have no issues in their cpu's because intel is kinda euh... In a very bad state atm haha. You dont want to be part of that right now xD

[–] AnyOldName3@lemmy.world 3 points 5 months ago

It wasn't me who you replied to originally - I agree that it's most likely AMD are just being super cautious given historically how many times bad news for their competitors has been falsely equated by the press as equivalent to a minor issue they've had, and the delay moving things after the microcode update and therefore making launch-day benchmarking more favourable is just a bonus.

[–] Woovie@lemmy.world 10 points 5 months ago (1 children)

Hanlon's razor, don't overthink it. No need for mindless conspiracy theories based on zero data. If it's aajor concern we'll hear something no doubt.

[–] sugar_in_your_tea@sh.itjust.works 1 points 5 months ago

I think you mean Occam's Razor. AMD signaling responsibility is a simpler explanation as a "dunk" on Intel, them having a similar issue as Intel seems far too coincidental. They're on completely different nodes, so there's no reason their issues would be related.

So my take is that AMD thinks Intel's fix is going to degrade performance significantly, so they want to wait to ensure their launch is as impactful as possible (bigger perf delta, more time to find hardware issues, etc). If AMD can show strength and reliability while Intel suffers, they could snap up much more market share (and improve product availability at launch).

[–] lowleveldata@programming.dev 8 points 5 months ago

no u

[–] DogWater@lemmy.world 1 points 5 months ago

Coincidences are real my guy.

[–] MonkderVierte@lemmy.ml 3 points 5 months ago

Unspecified quality, that's an issue.

[+] tabular@lemmy.world -18 points 5 months ago* (last edited 5 months ago) (2 children)

Would be nice for AMD to say what is the specific problem. They chose to recall, there must be something concrete to say.

[–] partial_accumen@lemmy.world 68 points 5 months ago (3 children)

They did. Its in the article.

A company representative told Tom’s Hardware that the issue doesn’t require a redesign or re-spin of the Ryzen 9000 silicon and will not result in changes to the already-defined specifications for the various models. AMD will re-screen the chips pulled from the field to identify any with potential issues and then return unaffected models to retail channels. This indicates that not all chips suffer from the issue.

An AMD representative told us that the company “identified an issue with our package product testing process for Ryzen 9000 series processors that could result in a small number of products reaching the market that do not meet our quality standards.” AMD specifically cited the package testing process, implying that the issue resides in the packaging implementation (more on that below).

It says nothing is wrong with the silicon. I appears to be a problem in some units where the silicon die is mated with the materials that hold it (fiberglass PCB or its interconnects).

[–] gravitas_deficiency@sh.itjust.works 24 points 5 months ago* (last edited 5 months ago) (1 children)

While annoying, that’s absolutely less of a showstopper than discovering a lithography issue like ~~big blue~~ (that’s IBM) Intel has discovered (and who knows exactly how long ago they knew about the oxidization issues)

[–] Glowstick@lemmy.world 17 points 5 months ago (2 children)

Big blue is a nickname for IBM, but i think you're referring to Intel

[–] gravitas_deficiency@sh.itjust.works 6 points 5 months ago

Ah whoops, you’re right

[–] jlh@lemmy.jlh.name 6 points 5 months ago

To be fair, they're on a similar trajectory.

[–] jlh@lemmy.jlh.name 3 points 5 months ago

It sounds like the issue is specifically with the testing process. Possibly they didn't test some of the packages properly and accidentally shipped out yield defects like missing memory channels, when they normally would have been scrapped at the factory.

[–] tabular@lemmy.world -2 points 5 months ago* (last edited 5 months ago) (1 children)

Notice how you said "a problem with" and the article said "implying that". There is some ambiguity. The issue is narrowed down but still not explicit. Hopefully we will get even more specifics later.

[–] partial_accumen@lemmy.world 6 points 5 months ago (1 children)

Of course there's still some ambiguity. They're likely investigating many things in parallel right now and cautiously assessing impact and scope. Their language suggests they think they've got the full picture, but they're likely still exploring some niche areas to be safe.

They've given public statements on the general area of the issue and its limited scope. I think your expectations on this issue at this point about perfect transparency are a bit unrealistic for a publicly traded company.

[–] tabular@lemmy.world -2 points 5 months ago (1 children)

Less an expectation and more of an ideal standard to strive for. Which I would think it's in our best interest as future customers to have the highest expectations.

[–] partial_accumen@lemmy.world 3 points 5 months ago

Well you're certainly welcome to hold that opinion. I don't think you're recognizing the gravity of what you're expecting them to commit to and also you're setting yourself up for repeated disappointment.

[–] Please_RTFA@slrpnk.net -4 points 5 months ago