New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Have a look at some of @yoursunny's academic work and you might rethink that one.
32-bit kernels will not be fixed for Retbleed: https://www.phoronix.com/news/Linux-x86-Retbleed
Cool story, bro.
It was a good story, thanks for sharing it @emg. Shame some people have no experience or respect for those who do.
Not surprised.
Virgin RAM is RAM that hasn't been physically used. The term "virgin" makes your explanation make even less sense AFTER POST and I had assumed you incorrectly referred to uninitialized RAM from power on which would be 00's or FF's and not produce audio. Even random garbage data made everyone bust up? Christ, was this a church meeting? Having it loop out "tit", "fuck" or "shit" would be believable and a good story. But random crap out of a speaker because of poorly written code? Yeah, not so much. I'd expect "shut that shit off" being yelled.
Regardless, terming this as "virgin RAM" means your colleagues were making fun of you behind your back or worse, your company was so shit nobody knew you didn't know what you were talking about or not being embarrassed for writing such bad code.
In summary, you called KNOWN DIRTY USED RAM "virgin RAM" for fuck knows reason. That triggered my BS detectors, yes.
Clearly you have never experienced the pleasures of an SP0256.
And more to the point, you apparently don't know the first thing about how RAM works, but still feel the need to try to explain it to @emg who clearly does.
Have you? That wouldn't change the fact dirty RAM would never be called "virgin RAM" or that a story that is basically "instead of reading out a specific string at boot, it read random garbage and was just garbled noise". Soooooo funny. Great story, one for the times.
How nice of you to inquire! Why yes, my good chap, I have!
Ignoring for the moment that this was his story, and he did in fact call it this, and moreover everyone there understand what he meant by that shows that there was a shared understanding they had, and perhaps if you tried to understand the situation he described rather than immediately trying to denigrate anything beyond your ken, then you might too understand what he meant.
Much as a table freshly tidied of mess with a clean tablecloth placed thereupon might be said to have a "virgin tablecloth", or a freshly washed blackboard (not just erased, actually washed clean) might similarly be referred to as a "virgin blackboard", it is quite clear his meaning was for RAM that the program hadn't yet written to, and was in the state the POST had left it in, moreover a state that was the same on every reboot and so the error would manifest itself in the same way every time.
If you had any experience in programming at all, you'd understand that it's better to fill uninitialised memory with random data rather than initialising it to zero, because it more quickly surfaces bugs where you read uninitalised data.
Again, you're making assumptions. It wouldn't have been garbled noise, although with such a misunderstanding, it is understandable why you might not appreciate it. It would instead have been random phonemes which would have been as hilarious as described. I can't imagine you know what a phoneme is either, but I'll leave that as an exercise for you to google that yourself.
Indeed.
My words stand on their own as written, and I stand by them. I have strived to write what happened as best as I could, described in the terms my coworkers and I used at the time. I was there and they were there and @TimboJones was not.
There is no further value in responding to his embarassing accusations and innuendos. His words speak for themselves. Judge for yourselves.
.
I have bad news for you, TimboJones: All RAM has been physically used ... during and after manufacturing and pre-packaging before one even opens the purchased RAM's package.
That said, I could perfectly well understand @emg 's term "virgin RAM" - as should everyone with a modicum of experience because emg explained really well what he meant. Moreover many people with some experience know that memory is checked by the system using certain patterns.
The problem isn't emg's wording or description, the problem is that you do not have "BS detectors" but rather active search devices looking for things that you can perceive and declare as "BS". The other problem is a rather large gap between your self-perception and the knowledge and experience you actually and really have.