If it happens again and you have Magic Sysrq enabled, you can do Magic Sysrq-t, which may give you some idea of what the system is doing, since you’ll get stack traces. As long as the kernel can talk to the keyboard, it should be able to get that.

https://en.wikipedia.org/wiki/Magic_sysrq

You maybe can’t see anything on your monitor, but if the system is working enough to generate the stack traces and log them to the syslog on disk (like, your kernel filesystem and disk systems are still functional), you’ll be able to view them on reboot.

If it can’t even do that, you might be able to set up a serial console and then, using another system running screen or minicom or something like that linked up to the serial port, issue Magic Sysrq to that and view it on that machine.

Some systems have hardware watchdogs, where if a process can’t constantly ping the thing, the system will reboot. That doesn’t solve your problem, but it may mitigate it if you just want it to reboot if things wedge up. The watchdog package in Debian has some software to make use of this.

I’m not sure that memory — and I’m speaking more-broadly than HBM, even — optimized for running neural nets on parallel compute hardware and memory optimized for conventional CPUs overlap all that much. I think that, setting aside the HBM question, that if we long-term wind up with dedicated parallel compute hardware running neural nets, that we may very well wind up with different sorts of memory optimized for different things.

So, if you’re running neural nets, you have extremely predictable access patterns. Software could tell you what its next 10 GB of accesses to the neural net are going to be. That means that latency is basically a total non-factor for neural net memory, because the software can request it in huge batches and do other things in the meantime.

That’s not the case for a lot of the memory used for, say, playing video games. Part of the reason, aside from hardware vendors using price discrimination that PCs (as opposed to servers) don’t use registered memory (which makes it easier to handle more memory) is because it increases latency a little bit, which is bad when you’re running software where you don’t know what memory you’re going to need next and have a critical path that relies on that memory.

On the other hand, parallel compute hardware doing neural nets are extremely sensitive to bandwidth. They want as much as they can possibly get, and that’s where the bottleneck is today for them. Back on your home computer, a lot of software is oriented around doing operations in serial, and that’s more prone to not saturate the memory bus.

I’d bet that neural net parallel compute hardware does way more reading than writing of memory, because edge weights don’t change at runtime (on current models! That could change!).

searches

Yeah.

https://arxiv.org/html/2501.09605v1

AI clusters today are one of the major uses of High Bandwidth Memory (HBM). However, HBM is suboptimal for AI workloads for several reasons. Analysis shows HBM is overprovisioned on write performance, but underprovisioned on density and read bandwidth, and also has significant energy per bit overheads. It is also expensive, with lower yield than DRAM due to manufacturing complexity.

But there are probably a lot of workloads where your CPU wants to do a ton of writes.

I’d bet that cache coherency isn’t a huge issue for neural net parallel compute hardware, because it’s going to be a while until any value computed by one part of the hardware is needed again, until we reach the point where we can parallel-compute an entire layer at one go (which…I suppose we could theoretically do. Someone just posted something that I commented on about someone making an ASIC with Llama edge weights hard-coded into the silicon, which probably is a step in that direction). But with CPUs, a big problem is making sure that a value written by one CPU core reaches another CPU core, that the second doesn’t use a stale value. That’s gonna impact the kind of memory controller design that’s optimal.

I think that it’s fair to say that AI is not the only application for that hardware, but I also think that carpelbridgesyndrome’s point was that they aren’t really well-suited to replace conventional servers, where all local computing just moves to a server, which is the sort of thing that ouRKaoS was worried about. Maybe for some very specialized use cases, like cloud gaming in some genres. I’d also add that the physical buildings have way more cooling capacity than is necessary for conventional servers, so they probably wouldn’t be the most-cost-effective approach even if you replaced the computing hardware in the buildings.

For example, maybe once a week or once a month?

Generally-speaking — and there are some specific situations where this doesn’t apply — your computer cannot start using a new kernel unless you reboot the thing, and there will be kernel updates. And some of those are security updates. So, yeah, you should reboot at some point.

It’s not really a “your computer will perform more-slowly if you don’t reboot occasionally” concern, though.

Once all of those who objected to the government and presented possible opposition have been eliminated one way or another, society will be harmonious.

You have to have a thin client device to access the servers out on the Internet, which is…kind of what a sub-$500 low-end PC or budget smartphone would be.

I suspect that it’s more that a lot of people are going to defer upgrades at the low end of the scale, use an older device for longer than they otherwise would have.

Might not be great for security; smartphone OSes won’t get security updates after N years, and Windows 10 is EOL.

Without a buyer for the cannery in Modesto, which employed up to 1,800 people including seasonal workers, the cooperative lacks the capacity to buy, can and market all the fruit soon to grow from the blooming peach orchards.

The last remaining processor, with plants in Lodi and Oroville, has offered one-year contracts to buy fruit from some of the orchards tied to canceled Del Monte contracts, granting a lifeline of sorts to some of the out-of-luck farmers. But the California Canning Peach Association estimated that the processor has offered deals for 24,000 tons of peaches — roughly a third of the 74,000 tons delivered last year to Del Monte — leaving growers to weigh the pros and cons of taking the short-term relief, or whether to rip out their orchards and start over.

“Two thirds of the growers are going to be, basically, just left out to dry,” Johl said.

“They’re the only player left. What are you going to do?” Johl said. “In the peach business, you do what the processor wants you to do. And what variety they want you to grow, you just grow it. You’re growing it for their needs. If they don’t need it — and that’s what we’re faced with now — they just don’t need all these peaches.”

I was thinking that maybe it’d be possible to ship peaches to another cannery — there are other states that grow peaches, and I’m sure that there are canneries that service them — but it looks like:

https://worldpopulationreview.com/state-rankings/peach-production-by-state

• The great bulk of US peach production is done in California.

• Almost all of the other production happens east of the Mississippi, with the exception of a small amount in Colorado. I don’t know how economical it’d be to ship to the other side of the country. Maybe another country. checks Canada also doesn’t do much, and virtually all of that is in Ontario, so any Canadian canneries probably can’t take much either. It does look like Mexico does substantial production, and the Mexican states that apparently specialize in it are Chihuahua and Coahuila, which are comparatively near, so maybe that could be a sink if shipping to Mexican canneries is viable.

The HC1 chip doesn’t load model weights from memory. It etches them directly into the transistors. Every weight becomes a physical circuit.

That’s one way to avoid memory bandwidth constraints!

Well, not all forms. The State of New York runs a lottery itself, for example:

https://en.wikipedia.org/wiki/New_York_Lottery

On November 8, 1966, New Yorkers voted to approve a constitutional amendment authorizing a government-run lottery.

checks

The 5700X3D looks like it goes for about $350 on eBay. The 5800X3D looks like about $450.

• Start with the comprehensive link collection from Cyb3rNexus’s GitHub Gist – it already contains hundreds of pre-filtered thread links!
• For more recent stories, navigate to NSFW Creative Writing

If your interest is in bulk download of erotic stories and you don’t specifically care about that forum (which I assume is the case, if you just want to dump the entire thing) — like, you’re looking for a training corpus to fine-tune an LLM to generate material along those lines or something in that neighborhood — I suspect that there are considerably-more-substantial archives than “hundreds”.

checks

It looks like ftp.asstr.org is still running an anonymous-access public FTP server. They’ll have years of archives from the relevant text erotica Usenet groups. You won’t need to screen-scrape that; just use any client that can recursively download from an FTP server.

I sat down to log into a couple MUDs yesterday. Didn’t stick with it — the combat still hasn’t evolved enough for me — but you could play that on anything capable of displaying text on a screen and running telnet.

It looks like some crazy person has been doing a TCP/IP stack for the 128K Mac, the first Macintosh ever released, from 1984, as well as a telnet client. So you can technically lug a 42-year-old computer out of an antique store and play currently-being-developed Internet games…though you won’t be getting color, since that came a while down the road.

If you get some device that can expose a serial console on some system to TCP/IP — not sure how far back you need to go for that — you could technically play it on a teletype from the 1930s.

The “some device” will have to be later, though, so that’s maybe kinda cheaty.

Technically, Debian Linux has been run on an Intel CPU from 1971, but it isn’t fast enough to be a practical host for such a teletype in that environment. Even stripped down forms of Linux are going to be “too big” to be such a host.

It does sound like the Commodore 64 has a package, Novaterm 10, that runs TCP/IP and telnet, but I don’t know whether it can output to the C64’s serial port rather than video display; you could play locally on one of those, but probably not run on a teletype. That being said, it probably shows that it’s technically-possible, since I’m sure that if it can run a virtual terminal program, it has the resources to just dump the text to an actual terminal via a serial port. I’d guess that there’s probably some system out there circa 1980 that someone has probably built that can both run a TCP/IP stack and expose a serial console to a 1930s teletype to play current Internet games.

I agree with you that it’s a good game, and it’s very playable on an older computer, but it’s actually not the lightest-weight game from a CPU standpoint. I mean, realistically, that thing should be able to get by with very little CPU usage and essentially none if you’re not pushing buttons, but it actually uses a fair bit of CPU time when you’re just sitting there staring at the screen. It’s actually kind of bugged me, because while it’s irrelevant on a desktop, it really consumes more battery on a not-plugged-in-to-wall-power laptop than is necessary, and it’d otherwise be such a phenomenal game for disconnected laptop use.

Go run top and just leave the game sitting there and it’ll be keeping an average of multiple cores hot on my laptop at 240 Hz running at vsync rate. And the world state isn’t changing – the game is turn-based.

You can constrain the framerate down to 10 FPS — and that significantly reduces CPU usage, down to an average of 37% of a core, on my system, at the cost of limiting the speed at which the game runs autoexplore, since it will always draw at least one frame in a given state, and at the cost of making the game feel sluggish and unresponsive.

And you’ll get that CPU usage even if you turn off all the graphical “glitz” have it just showing ASCII.

My guess is that they probably could probably benefit by (a) having a lightweight visual “display” thread that doesn’t do anything expensive, just update any animations and draw that to the screen, and if there are no animations, not even run a refresh at all, and (b) having a separate “heavyweight” thread for game logic that only runs if the world state has changed (autoexplore, automove, resting, or the player has pressed a key).

Cataclysm: Dark Days Ahead, which is a similar game (internally a turn-based game that’s basically generating an ASCII grid that can provide some light graphical glitz and tiles) also consumes a lot of CPU time when idle.

If you want another game of a similar sort that uses a surprising amount of CPU time, Dwarf Fortress. That being said, Dwarf Fortress is real time, so one can’t beat it up as much for consuming CPU time while the player is idle.

It’s still running. I submitted an article last month about how Micron was buying a facility that had actually just opened quite recently and was apparently producing DDR4 to refit it to make HBM; faster than building a new memory factory from scratch.

But as I point out in another comment in this thread, my guess is that this is more about being able to tap the already-manufactured used memory market. There’s a lot of DDR4 already in computers, and as those computers get disposed of, as long as it’s not thrown out and goes back on the market, that makes DDR4 available.

My guess — without trying to dig up statistics — is that the single component most-likely to fail in an old PC is gonna be rotational hard drives. Virtually all of my rotational drives have eventually died, aside from a few that were just so small and taking up space where I could mount other things that I no longer bothered using them.

I’ve seen fans die (not necessarily completely wedge up, but have the bearings go and become increasingly-obnoxious in sound).

And those are basically the only mechanical components in a computer.

Behind that, there’s input devices with keyswitches wearing out, but unless you’re using a laptop, replacing the input device is just unplugging the old one and plugging in a new one.

I’m not gonna say that motherboards don’t fail, but I can’t immediately think of something that would die. Decades back, I remember that there was a spate of bad capacitors that made their way to a bunch of motherboards and would eventually fail, but I haven’t seen anything like that recently.

searches

Looks like it was 1999–2007:

https://en.wikipedia.org/wiki/Capacitor_plague

The capacitor plague was a problem related to a higher-than-expected failure rate of non-solid aluminium electrolytic capacitors between 1999 and 2007, especially those from some Taiwanese manufacturers,[1][2] due to faulty electrolyte composition that caused corrosion accompanied by gas generation; this often resulted in rupturing of the case of the capacitor from the build-up of pressure.

High failure rates occurred in many well-known brands of electronics, and were particularly evident in motherboards, video cards, and power supplies of personal computers.

A 2003 article in The Independent claimed that the cause of the faulty capacitors was due to a mis-copied formula. In 2001, a scientist working in the Rubycon Corporation in Japan stole a mis-copied formula for capacitors’ electrolytes. He then took the faulty formula to the Luminous Town Electric company in China, where he had previously been employed. In the same year, the scientist’s staff left China, stealing again the mis-copied formula and moving to Taiwan, where they created their own company, producing capacitors and propagating even more of this faulty formula of capacitor electrolytes.[3]

Those would probably be from the DDR/DDR2 era, though.

I do think that it’s probably possible that some motherboard components might age out. Like, people may want to use newer versions of radio stuff, like WiFi or Bluetooth. You can maybe do that via USB, but the on-motherboard stuff might become more of a liability than the CPU or something.

I don’t think that I’ve ever personally had other computer components just up and fail other than the 13th and 14th gen Intel CPUs that internally destroyed themselves. It’s always been non-solid-state stuff, things with moving parts, that fail for me. I mean, I’ve damaged solid-state components myself via things that I’ve done, but it’s always damage that I incurred.

thinks

Oh, CMOS batteries eventually fail, but they’re usually — not always — mounted on motherboards with holders that permit replacement. I’ve had to replace those.

I did have a headphones amplifier that was attached to my computer where some solder joints got a bad connection and I had to open it and resolder it, but I don’t know if I’d call that a “computer component” just because it was plugged into a computer.

thinks more

I did have the power supply used for a fluorescent backlight in a laptop display start to fail once. But, honestly, my experience has been that unless you actively go in and damage something, most solid state parts will just keep on trucking.

I also kind of think that the strongest argument for console gaming is competitive multiplayer, not single player.

The fact that the consoles are closed and locked down inherently provides resistance to cheating and such, where the open PC world tries to (poorly) replicate a closed environment via kernel anti-cheat stuff. The console world having (well, more-or-less) one option when it comes to hardware means that everyone playing against each other has a fairly-level playing field — same input hardware, and people don’t get an edge from having fancier rendering hardware.

For single-player gaming, those console strengths become weaknesses — for single-player games, it’s preferable for the player to be able to do things like freely mod games, upgrade hardware to get fancier graphics, provide a lot of options as to what input stuff to use, etc. It doesn’t hurt anyone else for me to have the game running however I want, so I should be able to do so. On the PC, a player gets to enjoy all that.

If I were a console vendor and I were worried about the PC as a competing platform, I’d think that I’d try to emphasize my competitive multiplayer games, not single-player games.

The real problem with this sort of thing is that there’s no legal way to avoid it. If you’re operating a motor vehicle on public roads, you need to have a plate visible. You can’t obscure it.

The laws requiring that visibility were made in an era where it wasn’t possible for someone like Flock to enable anyone who can aim a camera at a road to mass-log and aggregate and data-mine the movement it provides.

The only real technical solution would be to back out the laws requiring license plates to be visible (and it wouldn’t be perfect, since Flock will still look for identifying oddities on a vehicle and try to log that too, like collision damage). But if you do that, then you lose an important tool for dealing with motor vehicle theft and finding vehicles involved in crimes.

And there aren’t restrictions on selling or doing whatever companies want with the data. Or with data that they get from facial recognition/gait data in the future, or that sort of thing.

My own personal preference would be for ALPRs to be generally illegal, outside of maybe some areas where logging is normally done by the government, like at border crossings. That’d be hard to enforce – someone could always run a rogue ALPR and it’d be hard to find — but it’d probably keep the scale down, avoid the mass deployment that makes the surveillance omipresent.

And I think that it’s worth remembering that even if you are comfortable with, say, Flock’s policy on dealing with data, there’s no guarantee that they aren’t compromised — a lot of very sensitive databases have been compromised in the past.

In the past, technical limitations permitted a certain level of privacy in society. It just wasn’t technically possible to build mass surveillance at scale, so it didn’t happen. But…as those technical barriers that some of us just took for granted go away, I think it’s worth asking whether we want to engineer in legislative barriers, to ensure that there is a certain amount of privacy provided members of society.

Yeah, honestly, if it becomes enough of an issue, maybe eBay and similar should create separate sections for machines with memory and those without. I mean, there are reasons people would want to get a system without memory too, especially if one’s looking for other parts, but I do totally get that it’s super-obnoxious if there isn’t a way to filter those out and one is looking for one with memory.

checks

It doesn’t look like eBay has a “0 GB” memory category, annoyingly enough, but they do have a “Not specified” category with a ton of listings. That’s not absolutely the same thing, since if you filter “Not specified” out, I’m sure that it might also exclude some listings that have an unknown amount of memory, but I’d guess that that’d get you most of the way there, and I do see people clearly listing machines with no memory in that category.

EDIT: Honestly, the rate of mis-classified listings there by users is pretty bad, even aside from eBay not providing a “0 GB” category. I was very surprised to see that there were a bunch of 512 GB listings. Looks like that’s essentially all people selling machines with 512 GB SSDs and choosing the wrong option.

I don’t know of a pre-wrapped utility to do that, but assuming that this is a Linux system, here’s a simple bash script that’d do it.

#!/bin/bash

# Set this.  Path to a new, not-yet-existing directory that will retain a copy of a list
# of your files.  You probably don't actually want this in /tmp, or
# it'll be wiped on reboot.

file_list_location=/tmp/storage-history

# Set this.  Path to location with files that you want to monitor.

path_to_monitor=path-to-monitor

# If the file list location doesn't yet exist, create it.
if [[ ! -d "$file_list_location" ]]; then
    mkdir "$file_list_location"
    git -C "$file_list_location" init
fi

# in case someone's checked out things at a different time
git -C "$file_list_location" checkout master
find "$path_to_monitor"|sort>"$file_list_location/files.txt"
git -C "$file_list_location" add "$file_list_location/files.txt"
git -C "$file_list_location" commit -m "Updated file list for $(date)"

That’ll drop a text file at /tmp/storage-history/files.txt with a list of the files at that location, and create a git repo at /tmp/storage-history that will contain a history of that file.

When your drive array kerplodes or something, your files.txt file will probably become empty if the mount goes away, but you’ll have a git repository containing a full history of your list of files, so you can go back to a list of the files there as they existed at any historical date.

Run that script nightly out of your crontab or something ($ crontab -e to edit your crontab).

As the script says, you need to choose a file_list_location (not /tmp, since that’ll be wiped on reboot), and set path_to_monitor to wherever the tree of files is that you want to keep track of (like, /mnt/file_array or whatever).

You could save a bit of space by adding a line at the end to remove the current files.txt after generating the current git commit if you want. The next run will just regenerate files.txt anyway, and you can just use git to regenerate a copy of the file at for any historical day you want. If you’re not familiar with git, $ git log to find the hashref for a given day, $ git checkout <hashref> to move where things were on that day.

EDIT: Moved the git checkout up.

I mean, there was a pre-existing used memory market, so some scavenging was already happening, but yeah, I’m not saying that increases in scavenging will fully cover the shortage. Just reduce it, which will reduce the degree to which prices rise relative to the scenario where the only memory available is newly-manufactured.