2
22
u/OptimalAnywhere6282 7d ago
that QR says your hardware is broken. try checking if the RAM sticks are loose or something.
14
u/Hour_Sell3547 20 years with Linux 7d ago
I haven't seen this in 20 years. But windows shows me bluescreens more than 20 times a year.
1
u/ApprehensiveRest9696 6d ago
I saw this while powering down a Hyper-V Linux VM a few days ago.
Same day that windows black screened twice.
0
u/evadingsomething 6d ago
Recently older brother got a second hand sound interface for his guitar. Plugged in and tested out works fine.
He was like yeah works good let me unplug the guitar and boom bsod I told him most likely some audio driver issue don't worry about.
Audio really fucks Windows, it's also complicated in Linux too but at least it doesn't raise these major errors.
1
u/DirectorDirect1569 6d ago
I have two audio interfaces on windows. I have never had these issues by unpluging my guitars. It's probably a DAW problem.
2
u/evadingsomething 6d ago
Idk know much about it, I thought it probably needed its own driver and Windows Update most likely installed a generic driver so it's acting up. Either way probably solvable.
27
u/OriginalLow7910 7d ago
Acting like windows blue screens of death dont exist
-23
u/Secure_Moment_1064 7d ago
Loonix can't handle low memory scenarios just as well as Windows lol
17
u/StupitVoltMain 7d ago
Linux actively combats memory shortage
-9
u/Secure_Moment_1064 7d ago
It shits the bed and waits too long with reclamation.
10
u/StupitVoltMain 7d ago
It shuts down processes like immediately when memory is super tight????
-7
u/Secure_Moment_1064 7d ago
No it doesn't. Default OOM killer for too long.
7
u/StupitVoltMain 7d ago
OOM killer works instantly from my experience
1
u/Secure_Moment_1064 7d ago
If it's tuned by your distro it might. The default behaviour sucks though.
Also it doesn't help that popular distros default to ZRAM and skip setting proper swap.
2
u/StupitVoltMain 7d ago
Ohhh I see what's going on here
I use zswap soo.....
2
u/Inevitable-Self-2702 7d ago
Even in Debian stable everything works well. On systems with 8GB ram (DDR3 and 4 at that). Windows user will hate this; Linux just works.
3
u/Independent_Blood559 7d ago
I had no problem with OOM killer yet. I am using cachy os for 6 months now. Though use cases might differ, and ram config too.
7
u/hailstorm11093 Nix ❄️ BTW 7d ago
0
3
2
u/RandomDude9943 7d ago
Except its actually the opposite, ive never seen OOM killer taking too long to decide what to kill
1
u/Voltagepeanutbutter7 I Love Linux 7d ago
My laptop crashes for about 3 minutes just to kill some process that will rebuild itself eventually
1
u/RandomDude9943 7d ago
Strange, never ever heard of that lol. What distro?
1
u/Voltagepeanutbutter7 I Love Linux 7d ago
Mint, but happens in general
1
u/RandomDude9943 7d ago
Never happened to me on debian or artix, at most my de freezes for like 5 secs
1
11
4
u/GenericFoodService Linux is free if your time isn't valuable 7d ago
The log makes it seem like you have some kind of hardware issue. You're getting page faults, which means your RAM might be loose or misconfigured.
Honestly, I love how information dense these things are, but I wish there was more plain-text information on the screen, too. I shouldn't need to depend on a QR reader.
1
u/reav11 7d ago
Holy fuck, even the Linux QR codes look like they're full of a ton of data.
Can Linux not post an error message that isn't like reading a book?
4
u/Zeedith- 7d ago
It's larger/more dense as the link it contains has all the info in about the crash in the query params so it can be actually be debugged/fixed instead of just something generic like "Memory failure" that tells you very little about what caused the crash nor how to fix it so it doesn't happen again.
1
u/reav11 7d ago
Why can't it be debugged with "Memory failure at (address)".
I mean, that does it for me. Time to run Memtest.
It most certainly can be done with less information.
4
u/Zeedith- 7d ago
Because many times it's not a simple hardware issue like "the ram is bad", it contains an entire stack trace (the calls that led up to the error) so you can find the root cause instead of the result.
Here's the literal example of what the QR code links to
TL;DR: It allows it to contain the cause of the error, not just the effect.
0
u/reav11 7d ago
Yea, so if I see memory failure I can debug it too.
I don't need a 9 page write up of every address involved. I can just run some tests and get the same result without looking at stack traces.
5
u/DetermiedMech2 7d ago
I must say ive never seen someone want less information from a crash
1
u/reav11 6d ago edited 6d ago
I need the amount of information about the crash that helps me diagnose the issue. Not 10 times more, but enough to point me in the correct direction to identify and solve the root cause of the issue.
This is the same problem with CLI in Linux, it gives you an 8 page error message to tell you that you're missing a dependency. The extra information isn't helpful it's harmful. I'll spend more time reading through that error message to find what's wrong than I will actually solving the problem.
So since you've never seen someone who doesn't want more information, I guess you've never seen anyone skilled with computers that can actually troubleshoot and needs only the information that lets them run the correct diagnostics.
The best part about your argument is the actual fault that caused this cascade doesn't even appear in the QR code link, the critical component of what you'd actually need to diagnose this issue.
2
1
u/Lucien1299 7d ago
Is it real?
1
u/evadingsomething 6d ago
Yeah this a kernel panic. If your hardware is fine you won't see it as frequent as Windows bsod.
-2
u/ChecksOutIndeed 7d ago
skill issue
0

3
u/dumbasPL I don't hate Windows, I just like Linux more. 7d ago
perfect screenshot, "xen" in the back trace. Suggests a VM, a xen VM. What are you doing? And why not on KVM? Or did you just steal a random image from Google?