Hey all, I’ve got a really strange and frustrating problem. I strongly suspect it’s hardware-related, but figuring out which hardware has been very difficult because the nature of the lock-up means the kernel doesn’t get a chance to write any logs (have logs set to be persistent and they always just abruptly end with no errors at all, then the next reboot logs begin).
Framework 13 first gen (DIY build with Fedora Linux)
The slightest bump of the computer, even just from typing sometimes, will cause it to immediately freeze and never recover on its own. I let it run for several hours once. I have to hold the power button to force it off and reboot.
Theories and attemped fixes:
The laptop did take a hard fall, but that was over 10 months ago and I would have expected trouble sooner if the fall was the cause. Initially I suspected maybe the RAM needed reseating, but that did not fix it. I also checked the connection for other components (wifi module, nvme drive, even web cam).
Questions I would love help with:
Has anybody experienced this before?
Any suggestions/theories about what could be the problem?
Are there any clever hacks I could try to get some logs out of the kernel or systemd?
Something you can do while you work through the ticket process to speed this along.
Test this on a live USB stick (sounds ridiculously based on the symptoms, I know - trust me, get this tested and report it back on the ticket. Shows support results on an older kernel, default settings on an unchanged environment.
Provide this link and what you did thus far to support.
This sounds typical of a physical vibration-induced temporary short or disconnect; most likely caused by one or more hairline cracks, solder-pad lifts, or pin disconnects. If there are ball-grid-array components it could be a crack in one of the balls under the component (not an uncommon event a decade ago when switching from lead solder and having frequent thermal expansion and contraction) which can often be cured with a reflow.
It is sometimes possible to narrow down the region where the damage is if pressing keys can invoke the issue - testing by methodically pressing each key to find out if a particular key, or area, of the keyboard seems to cause it. That can correlate either to something directly under that area or it causing leverage that affects something elsewhere - knowing and having access to the hardware components should make it easier to deduce where to look.