(#fv2iaoa) @lyse Errr, this is on my current machine running Linux 5.18.16. 😅 (The challenge was about limiting/tracking your online time: ) (Actually using old computers and old *software* for every day life is not that much fun, I’ve found. You can’t do anything related to the Internet, basically: None of the old crypto works anymore. So you can do Gopher and visit websites of enthusiasts who still offer HTTP, but that’s it.)

(#fv2iaoa) (Not that kernel bugs like those were acceptable. But it’s better than broken hardware.)

(#fv2iaoa) @lyse Oh, yeah, JS is a no-go, as is most of CSS. You can at least do something without CSS and sometimes pages still work without JS, but without crypto, nothing works. Not even IRC anymore. 🙄

(#fv2iaoa) After more testing: I’m beginning to think that I’m hit by an issue in memtest86 itself: - - Only the test called “block move” failed and only when the SMT mode was set to “all cores”. So far, no issues with “round robin”. Oh, and I’ve now seen the issue on *all* slots and *all* modules. So why was I seeing kernel panics then? There’s another possibility: My issues started right when I started that “old computer challenge”. I was starting/stopping my networking interface a lot and almost all freezes happened while starting it (one kernel panic happened while the system was shutting down and I unplugged some USB device). So it’s at least possible that these are just kernel bugs. 🤔 Since the “old computer challenge” wasn’t very enlightening anyway, I’m going to abort that now and see if the system stabilizes. And/or run isolated tests to see if starting/stopping the NIC repeatedly causes kernel panics.

(#fv2iaoa) @movq brush it out? could be bit of dust on the gold contacts 🤔

(#fv2iaoa) @movq Oh, I see. I just somehow assumed you went the extra mile to also use the equipment from back in the good old days. :-) Right, totally forgot about crypto. But also all the JS crap probably breaks down.

(#fv2iaoa) @prologic Thought so, too, but how would it have gotten there in the first place? I saw a couple of weird kernel panics, so I ran memtest86 and it showed errors. Only then did I even open the computer’s case. 🤔

(#fv2iaoa) @movq I'll keep my fingers crossed. Which (ancient?) kernel version were you using?