Any Linux friends know what this means?

January 29, 2026 - 03:36 UTC

18
0
44
not enough RAM maybe? try more swap?
1
0
1
I may be running from a floppy disk... 😅
1
0
11
Are you trying to cram 64 bit stuff into 32 bit blocks?
0
0
0
I seem to remember a failing hard drive throwing errors like this on boot.

Back in 2004ish though so more than two decades old memory I'm calling back on.
0
0
0
I don’t know anything about Linux, but I’ll take a stab at it: it means there’s something wrong. Hope that helps!
0
0
0
i think its out of memory trying to execute a program

or its expecting a certain amount of memory that it can't access

www.man7.org/linux/man-pages/man2/brk.2.html
0
0
0
No
0
0
3
I think the first bit is an abreviation for system is borked.
0
0
0
The computer brked at you.
0
0
0
you doing i386 linux shenanigans? because only reference i've found to sys_brk 7 is in a library that references it for i386... deals with memory allocation but it's above my pay grade.
0
0
3
You have to descromble your parambulators driving the flux capacitor.
0
0
1
it means you need to sudo the apt get and some cat nanoing with GRUB config while holding this specific golden amulet and eating spagetti with a sense of regret.
0
0
0
Memory problems? MMC failure somehow?
0
0
0
It shit a brk
1
0
8
(apparently it is failing to allocate memory. looks like overflows.)
0
0
4
So... you thought you could play with your heap eh?

That's all I've got, sys_brk is a call to modify the heap size directly, and it's failing.
0
0
8
Computer for:

All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy...
0
0
0
I think your computer is sad
0
0
2
you smashed your stack
0
0
1
Can't help because I average re-installing Linux at least 3 times a week and that's why I keep quiting at Linux.

And, I STILL don't know how to install Linux!
0
0
0