Linux

11649 readers

544 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago

MODERATORS

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

Dealing with faulty RAM modules in 2026 (blog.kumio.org)

submitted 3 weeks ago by kumi@feddit.online to c/linux@programming.dev

6 comments fedilink hide all child comments

How to test and safely keep using your janky RAM without compromising stability using memtest86+ and the memmap kernel param.

you are viewing a single comment's thread
view the rest of the comments

[–] Corbin@programming.dev 1 points 3 weeks ago (1 children)

Well done. I recently revived the BadRAM kernel patch in order to do something similar; memtest86+ supports that functionality too, using , , , .

[–] kumi@feddit.online 4 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

I'm curious: What's motivating you to do that when the memmap param can do the same without patching?

[–] Corbin@programming.dev 1 points 1 week ago

BadRAM specifiers can apply to stripes of memory corresponding to certain physical hardware failures. The memmap hack only allows for contiguous allocations. BadRAM's intended for repurposing consumer-grade RAM that might normally be thrown out, not for reconfiguring motherboards that have strange layouts.