this post was submitted on 14 Jul 2024

37 points (95.1% liked)

Linux

4924 readers

96 users here now

A community for everything relating to the linux operating system

Also check out !linux_memes@programming.dev

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

founded 1 year ago

MODERATORS

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

37

[Weekly thread] GNU+Linux help: ask anything! (programming.dev)

submitted 1 month ago by anzo@programming.dev to c/linux@programming.dev

14 comments fedilink hide all child comments

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

[–] anzo@programming.dev 1 points 1 month ago (1 children)

Replace markdown oxide for another tool for some time, try breaking the correlation to find causation

[–] sxan@midwest.social 1 points 1 month ago

Yeah, I've disabled markdown-oxide for the moment, so I'll see what my uptimes look like for a bit.

I honestly can't imagine how a userspace program could cause this behavior, though. There's no memory pressure, and there are 16 cores in this CPU, fer chrissake. Even trying to peg the CPU, I didn't notice the md-oxide correlation until I started watching top; the temps weren't going up, performance wasn't impacted.

I thought for sure it was a memory (hardware) issue, but I've run several memtests and they come back clean. No odd kernel module crashes in the logs; no indication anything is wrong until - poof. Reboot.