Thanks for the recap. Missed the first 30 minutes or so.
0x0
I'm fresh off ruling out the RAM via memtest. I'll let it do a longer soak overnight to see if anything fails then, but I'm now on to bisecting the kernel from what I believe is the last release of 6.6 (6.6.13) to hopefully whatever the offending commit is. Been a while since I've had to mess around with manually building the kernel without the aid of linux-tkg, but I'm off to learn it anyway. Thanks for the help!
This is what I'll try next. I do think memory is the problem now that I've had a few more hours of research. Kernel 6.7 has issues with elevated RAM usage, so it's absolutely doing something funky with memory that might be exposing underlying hardware issues. I also realized my stable kernel was a version or two away from 6.6.13 (6.6.10), so I'm running it now to see if the issue was introduced late in the 6.6 release cycle, which would be easier to bisect than 6.7.
Yeah, the qemu idea was brought up earlier in the thread and it's very interesting. Glad you confirmed you could repro real issues there in the test environment, so it's at least a little likely I'll be able to do the same. Makes sense that it would work and is way better than letting the real system crash and burn. My kernel compile time is pretty short so it shouldn't be too bad to bisect, I'm just not sure how many commits separate my stable kernel from the bugged 6.7. TBH I'm not that familiar with kernel dev., so maybe it's way simpler than that.
I was afraid of that. Since I'm not the only one, maybe someone else is doing it already. But if it's still an issue in a few weeks, maybe I'll take it on as a weekend project. As for the motherboard, I believe the latest version is currently on it (2022 or 2023.)
Fixed the link. Thanks!
I've also tried linux-tkg, which I believe rolls in the Zen patches. If it doesn't, I'll definitely try it.
That's an interesting idea. I'll have to look into whether it's a viable option first, though.
This will be my last resort mostly because I'm fairly certain it's a kernel issue, but yes, I've never ran an extended memtest on this build and should probably let it run overnight at some point just to make sure.
If you want to do a bit of engineering: CalDAV supports todo lists. I forget what server software I've got running, but I sync the list to my android phone via DAVx5 and tick off/add items via tasks. For other platforms you can just look for CalDAV-supported programs (most email apps.)
This was a solved problem on other sites via wikis and weekly threads. There's no value in another "what distro should I use?" post. It's great that people want to contribute, but there should be a more centralized resource we can refer people to where people can focus this energy.
As for the Windows threads, they've been a staple of every Linux-focused community for as long as I've been browsing them. I guess if it makes people feel better then I suppose that's enough of a reason to keep them around.
Can't you just put the key in? Do they even have physical keys?
I started doing this after my phone number got into some kind of crazy scam call database. At the height of it I was getting somewhere in the neighborhood of 30 calls a day, basically rendering the phone unusable.
So I started actually picking up and running these jokesters through the ringer. I'm talking 15+ minutes of pointless conversation, false info, tons of backtracking, and general bullshit. I refined my craft over a few months and would time how quickly I could make them scream at me for fucking with them. At the end of it my phone got taken off at least one of the bigger lists because the calls went to down only 10 or so a day. Now it's one or two a day at the most, probably from me not answering like I used to.
Favorite call was one guy who figured out I was messing with him and it turned into this general question and answer thing about life in the US. Dude wanted to know how easy it was to pick up chicks and whether or not I'd dated a lot/was married. Great guy, really into Counter-Strike.