# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 23
# self = https://watcher.sour.is/conv/fv2iaoa
Uhhhh … A RAM *slot* just died. 🤔 Not the actual memory chips but the slot itself. I haven’t touched my RAM in years. 🤨
Uhhhh … A RAM *slot* just died. 🤔 Not the actual memory chips but the slot itself. I haven’t touched my RAM in years. 🤨
Uhhhh … A RAM *slot* just died. 🤔 Not the actual memory chips but the slot itself. I haven’t touched my RAM in years. 🤨
@movq brush it out? could be bit of dust on the gold contacts 🤔
@movq brush it out? could be bit of dust on the gold contacts 🤔
@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. 🤔
@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. 🤔
@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. 🤔
After more testing: I’m beginning to think that I’m hit by an issue in memtest86 itself:
- https://pixelworkbench.com/2018/07/17/memtest-freezing-test-7-block-move/
- http://linerate.blogspot.com/2014/03/memory-errors-in-memtest86-and.html
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.
After more testing: I’m beginning to think that I’m hit by an issue in memtest86 itself:
- https://pixelworkbench.com/2018/07/17/memtest-freezing-test-7-block-move/
- http://linerate.blogspot.com/2014/03/memory-errors-in-memtest86-and.html
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.
After more testing: I’m beginning to think that I’m hit by an issue in memtest86 itself:
- https://pixelworkbench.com/2018/07/17/memtest-freezing-test-7-block-move/
- http://linerate.blogspot.com/2014/03/memory-errors-in-memtest86-and.html
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.
(Not that kernel bugs like those were acceptable. But it’s better than broken hardware.)
(Not that kernel bugs like those were acceptable. But it’s better than broken hardware.)
(Not that kernel bugs like those were acceptable. But it’s better than broken hardware.)
@movq I'll keep my fingers crossed. Which (ancient?) kernel version were you using?
@movq I'll keep my fingers crossed. Which (ancient?) kernel version were you using?
@lyse Errr, this is on my current machine running Linux 5.18.16. 😅 (The challenge was about limiting/tracking your online time: https://dataswamp.org/~solene/2022-07-10-old-computer-challenge-v2-day1.html )
(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.)
@lyse Errr, this is on my current machine running Linux 5.18.16. 😅 (The challenge was about limiting/tracking your online time: https://dataswamp.org/~solene/2022-07-10-old-computer-challenge-v2-day1.html )
(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.)
@lyse Errr, this is on my current machine running Linux 5.18.16. 😅 (The challenge was about limiting/tracking your online time: https://dataswamp.org/~solene/2022-07-10-old-computer-challenge-v2-day1.html )
(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.)
@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.
@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. 🙄
@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. 🙄
@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. 🙄