Adventures of putting 16 GB of RAM in a motherboard that doesn’t support it

Re:Adventures of putting 16 GB of RAM in a motherboard that ... by duxup on Thursday April 04, 2019 @01:17PM (#19574760)

In another career I sat on a conf call where an engineering manager was really upset and went off on a tangent about how X code should not "freak out" every time it sees something unexpected.

I was not writing code at the time and had nothing to contribute.

So apparently they fixed it later.... then came the security issues, unexpected behavior, shit going sideways.

Sometimes a straight crash is not such a bad thing.

[ Parent | on HN ]

Re:Adventures of putting 16 GB of RAM in a motherboard that ... by voidfunc on Thursday April 04, 2019 @03:13PM (#19576022)

I would rather something crash and log than continue silently most of the time, especially with backend and server systems.

One of the things I like about Kubernetes is that the ecosystem (generally) tries to adhere to the "Not healthy? Then crash and keep crashing" mantra when something doesn't work. If I see something is in a CrashLoopBackoff I at least know its b0rked. Stuff that reports its up and running when it's actually hosed is really annoying.

[ Parent | on HN ]

Re:Adventures of putting 16 GB of RAM in a motherboard that ... by duxup on Thursday April 04, 2019 @03:20PM (#19576108)

I'm inclined to agree.

The worst sort of thing to track down is working ... but not. God knows when it started or what it has impacted.

Worse if it impacts real data or data goes where it shouldn't.

[ Parent | on HN ]

Re:Adventures of putting 16 GB of RAM in a motherboard that ... by olliej on Thursday April 04, 2019 @01:25PM (#19574848)

Indeed - and increasingly deterministic crashes are being put in release builds (see RELEASE_ASSERT in webkit, and similar elsewhere)

[ Parent | on HN ]