Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

10% of Firefox crashes are caused by bitflips

mas.to

Post reply on HN
Print view View original

491–495 of 495 posts

Re: 10% of Firefox crashes are caused by bitflips

#491

Post by altairprime »

antonkochubey wrote: post #488
altairprime wrote: post #482

Earlier quoted context omitted.

288-pin ECC is, I believe, available on any X670E/X870E platform boards so long as the motherboard builder hasn’t expressly interfered with it (and probably other chipsets as well?). Windows 10+ reports it as full ECC (multi-bit / 72-bits). AMD pushed that enable in an AGESA three or four years ago iirc. The CAS latency for ECC is about double what gaming RAM offers, but in practice other more costly factors tend to…

>The CAS latency for ECC is about double what gaming RAM offers Ironically, overclocking ECC memory is much easier than overclocking non-ECC DIMMs, because you know exactly at which point you start encountering instability and need to dial back, instead of relying on.. application crashes and BSOD's to know that you're running way too optimistic clocks/timings. Meanwhile I overclocked 'low clock / loose timing' ECC D…

Yeah! A stick of 5600 can generally reach 6000 with geardown off and that’s as far as I’ve seen cause to dial it. But certain parameters that are popular to lower for latency reduction can be, how would I put it, slightly less flexible — tREFI comes to mind as one that nearly any lowering of (on the enterprise sticks I’m using anyways) tends to cause DFE/MBIST training failures no matter what, even with direct airflow, before it ever boots far enough for memtest to expose ECC errors.

(For those out there following along with PCs, if you aren’t tuning with MBIST maxed out in your BIOS, you might want to revisit that.)

Re: 10% of Firefox crashes are caused by bitflips

#492

Post by monster_truck »

iamflimflam1 wrote: post #272
monster_truck wrote: post #178

Earlier quoted context omitted.

If you look around you'll see people already putting the new, chinese made DDR4 through its paces, it's holding up far better than anyone expected. Every single time I've had someone pay me to figure out why their build isn't stable, it's always some combination of cheap power supply with no noise filtering, cheap motherboard, and poor cooling. Can't cut corners like that if you want to go fast. That is to say, I've…

The danger is we’ll start to see more QA rejects coming into the market. The temptation to mix in factory rejects into your inventory is going to get very high for a lot of resellers.

Nobody would deliberately sell QA rejected memory. I do not think you understand what this would result in, even in markets with relatively dogshit consumer protection laws.

Re: 10% of Firefox crashes are caused by bitflips

#493

Post by seanw444 »

jodrellblank wrote: post #457
seanw444 wrote: post #447

Earlier quoted context omitted.

> It’s in popular culture and HN comments most often as spyware and mass surveillance of people, and that’s a bit of a shame. I don't know whether you mean it's a shame that people consider it spyware, or if you meant that it's a shame that it manifests as spyware typically. I agree with the latter, not the former. It usually is spyware. If companies went for simple opt-in popups with a brief description of the reaso…

I mean what you did is a shame. I asked to put the spyware aside for one sub-thread and focus on the astonishing worldwide sensor array, and you talked about the spyware and nothing else.

People don't want to be exploited for the greater good just because it's astonishing technology. That's why it always gets brought up.

Re: 10% of Firefox crashes are caused by bitflips

#494

Post by funcDropShadow »

cestith wrote: post #389
funcDropShadow wrote: post #358

Earlier quoted context omitted.

OMG no. Politician have no business making technological decisions. They make it harder to innovate, i.e. to invent the next generation of ECC with a different name.

ECC is like Ethernet. The name doesn’t have to change for the technology to update.

If companies are allowed to change the meaning of terms in legislation we are in even more trouble.

Re: 10% of Firefox crashes are caused by bitflips

#495

Post by cestith »

funcDropShadow wrote: post #494
cestith wrote: post #389

Earlier quoted context omitted.

ECC is like Ethernet. The name doesn’t have to change for the technology to update.

If companies are allowed to change the meaning of terms in legislation we are in even more trouble.

Ethernet was once carried over thick coax at like 2 then 3 megabits per second. By the time it was standardized as IEEE 802.3 it was at 10 megabits. 802.3 was thin coax. 802.3e took a step back in speed to 1 megabit, but over phone-type wire. 10 base T, Ethernet over twisted pair at 10 megabits per second, wasn’t until 802.3i in 1990. Then 10 base F (fiber) in 1992.

Then there are various speeds of 100 M, 1000 M / 1G, 2.5 G, 5 G, 10 G, 25 G 40 G, 50G, 100 G, 200 G, and 400 G. Some of the media included twisted pair, single mode fiber, multimode fiver, twinax cable, Ethernet over backplanes, passive fiber connections (EPON), and over DWDM systems.

There have also been multiple versions of power over Ethernet using twisted pair cable. Some are over one pair, some two pairs, and some over the data pairs while other use dedicated pairs for power.

There are also standards for negotiation among multiple of these speeds. There have been improvements to timestamping. There have been standards to bring newer speeds to fewer pairs or current speeds over longer distances.

There’s currently work on 1.6 Tbps links up to 30 or possibly 50 meters. There has been work on the past to use plastic optical fibers instead of glass ones. Oh, and there are standards specific to automative Ethernet.

Ethernet itself, the name and the first implementation of a network with that name, were from 1972 and 1973. It was on the market in 1980 and first standardized in 1983 as ECMA-82.

Ethernet supports in its different configurations direct host-to-host connections, daisy chains, hubbed networks, switched networks, tunnels over routed protocols like TCP or UDP, bridges over technologies like MOCA or WiFi, and even being tunneled across the open Internet.

All of these are Ethernet. They have a common lineage. They are all derived from the same origin. Token Ring, FDDI, ATM, and SONET have all been more than one thing over time too. So has WiFi. 802.11a is very little like 802.11be, but those are also similar enough to carry the same family name.

The IEEE 802.3 series has a lot of history buried in those documents.

Post reply on HN