Linux

7226 readers

232 users here now

A community for everything relating to the GNU/Linux operating system

Also check out:

Original icon base courtesy of [email protected] and The GIMP

founded 2 years ago

MODERATORS

[email protected]

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

submitted 9 months ago by [email protected] to c/[email protected]

15 comments fedilink hide all child comments

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

[–] [email protected] 2 points 9 months ago (1 children)

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

[–] [email protected] 1 points 9 months 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.