8 points

My AMD apu and arch linux is so stable that it’s starting to get boring /j

permalink
report
reply
13 points

Intel crashes?

permalink
report
reply
19 points
5 points

AFAIK the current drama is not about a bug but manufacturing problems

permalink
report
parent
reply
7 points
*

Oh well… that is not nice for the new Novacustom coreboot laptops!

Edit: doesnt matter, as they ship new revisions.

permalink
report
parent
reply
4 points

Not only do the 13th and 14th gen crash, but vendors ask for about 1000 dollars more for supporting servers with those chips.

permalink
report
parent
reply
28 points

Yeah… Their desktop CPUs are in all the news right now for crashing linke crazy

permalink
report
parent
reply
7 points

Oxidation in the fab process. They have simultaneously claimed that oxidation isn’t causing any issues, and that it’s caused only “some” crashing issues. Because they’ve been so wishy washy, it’s probably safe to assume that any 13th or 14th gen CPU that experiences any kind of crash or BSOD is degraded and should be RMA’ed immediately, otherwise you risk getting stuck with a permanently physically degraded CPU.

Intel says they identified the issue sometime in 2023 and fixed the fab process. So the good news is that any newly manufactured Raptor Lake CPU shouldn’t have this issue. The bad news is that Intel won’t give a date range of when the fab issue occurred, or exactly what CPUs it affected (by date code), so really the only choice consumers have at this point (before we get to the inevitable class action lawsuit) is to RMA at the slightest sign of instability.

Intel is also planning to release a microcode update in August, but there’s a lot of doubt that this can be fixed via microcode.

This was affecting 50% of Raptor Lake CPUs in data centers, and it’s become clear via video game telemetry that it has also affected a significant number of consumer chips.

https://youtu.be/OVdmK1UGzGs

permalink
report
parent
reply
37 points
*

Im sure these guys are fiends, that’s why they are at the pub together.

There definitely was some computer with an overvolted Intel just about to crash whilst Crowdstrike was just about to crash the system on that very PC, the same PC that was running all the primary systems on a Boeing plane that was just about to crash for its own separate reasons.

permalink
report
reply
23 points

And somehow, all those crashes stabilised each other, allowing the plane to land safely. Only the pilot needed to change their pants afterwards.

permalink
report
parent
reply
18 points

The pilots pants crashed??

permalink
report
parent
reply
6 points

The one thing that escaped the stabilising crash loop.

permalink
report
parent
reply
8 points

I guess it’s a great time to be Linux / AMD user muhaha.

I’m kidding. I also run Windows and MacOS.

permalink
report
reply
1 point

The debian edition of croudstrike crashed some weeks earlier but it was not used in that many critical environments 🤷🏻‍♀️

permalink
report
parent
reply
2 points

That makes the windows one so much crazier really, they didn’t learn jack shit from the first one.

permalink
report
parent
reply

no way, bog.

permalink
report
parent
reply
5 points

Run everything, and you can always be smug about something ;D

permalink
report
parent
reply
2 points

You bet.

permalink
report
parent
reply
2 points

I have to reset the bios sometimes to Start the PC, its perfectly stable when its on, DDR5 and Intel 13gen what could go wrong

permalink
report
reply

linuxmemes

!linuxmemes@lemmy.world

Create post

I use Arch btw


Sister communities:
Community rules
  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

Community stats

  • 7.4K

    Monthly active users

  • 910

    Posts

  • 15K

    Comments