Solved KDE crashing on 2GB RAM, kernel doesn't handle OOM right

1000005260.gif
 
A classic moment from programming history; somewhere on an insignificant mote of dust, hanging in the outer spiral arm of a lesser known galaxy, at approximately 13.79 billion years since the hypothesized 'big bang', THIS infinitesimally improbable event occured:-

View: https://youtu.be/qXAubRZ-qjw?t=210

"it's probably something very simple... so why is it not terminating...? It really ought to work!" 😁
 
I hate to break it to OP, but OP's metal is just not enough to run the latest and greatest softwares like KDE and Firefox. It's gonna be a rather clunky game of tradeoffs of what OP is willing to live with. Up-to-date stuff that will run on OP's metal is gonna be missing features that are important to OP, and it won't be the easy and convenient stuff that everyone knows. I've been down that road, I do have old hardware that I played with in my past.

I know what it's like to have the choice of being up-to-date, cheap, fast. Choose two, you can't have all 3.
 
I must admit, being told to delete the entire freebsd installation in order to run at the original clock speed is a bit extreme 😂
Perhaps this is a feature of the new timeline, since CERN performed the Higg's boson experiment?
 
Well, it's irrelevant now. I think this desktop computer is haunted. BIOS is acting completely not to specification. I just flashed it too, and nothing's changed. It was reporting weird frequency levels, now it's completely not reporting frequency levels.

Is there anything to be done except flashing BIOS in such a case? Other than that, it's probably the source of symptoms I was observing. If there were some clock mismatches of some sort happening, it could've corrupted memory...
 
Removed CMOS battery, the freq_levels are back, but they are still all wrong as they were earlier. I tried everything - resetting CMOS via the pins, flashing BIOS, changing BIOS settings... I think the motherboard/BIOS have gone sour (integrated LAN is broken). It's an 16 year old Foxconn motherboard. It can still do basic stuff that doesn't require the full 2GB RAM, which is nice, but since it's constaoverclocked in some weird way, it corrupts swap data, I think is what's happening.
 
loveydovey said:
Removed CMOS battery, the freq_levels are back, but they are still all wrong as they were earlier. I tried everything - resetting CMOS via the pins, flashing BIOS, changing BIOS settings... I think the motherboard/BIOS have gone sour (integrated LAN is broken). It's an 16 year old Foxconn motherboard. It can still do basic stuff that doesn't require the full 2GB RAM, which is nice, but since it's constaoverclocked in some weird way, it corrupts swap data, I think is what's happening.
Click to expand...
This sounds like a somewhat pathological case for trying to test backwards compaibility! 😂
 
The OP put a stick into the front wheel of their bicycle. He went flying and hurt himself. Sadly, he was not wearing a helmet. He is asking us about the smallest front wheel that will function on a bicycle. And he is complaining that his current bicycle is not going straight, makes funny noises every revolution of the wheel, and his head hurts.

If someone really wants to determine the minimum amount of memory required to run with a GUI on FreeBSD, that person has to perform the experiments carefully and systematically. And without prior notions about things like overclocking or corruption.
 
ralphbsz said:
The OP put a stick into the front wheel of their bicycle. He went flying and hurt himself. Sadly, he was not wearing a helmet. He is asking us about the smallest front wheel that will function on a bicycle. And he is complaining that his current bicycle is not going straight, makes funny noises every revolution of the wheel, and his head hurts.

If someone really wants to determine the minimum amount of memory required to run with a GUI on FreeBSD, that person has to perform the experiments carefully and systematically. And without prior notions about things like overclocking or corruption.
Click to expand...
Well, it was an interesting investigation. A puzzle to be solved. And frankly I wouldn't have diagnosed it faster on any OS other than FreeBSD. That's one thing I noticed switching to this beautiful OS - the speed with which I accomplish everything - from simple to complex. It's just the most jaw dropping OS.
 
You must log in or register to reply here.
Back
Top