Framework laptop 12 suspected hardware level instability across multiple kernels and Linux distros

Framework Laptop 12 Linux
, ,
1

So recently my Framework Laptop 12 has developed severe stability issues that appear to be hardware‑level rather than software‑related. The system crashes randomly every few minutes across multiple Linux distributions and kernels, and the errors occur before userland loads.

summary of the symptoms:

  • Random crashes and reboots with no kernel panic (backlight is still on but screen is black)

  • Occurs across multiple distros (Mint, Fedora, Arch) and clean installs

  • Occurs across multiple kernel versions

  • Occurs even with no expansion cards connected

  • Occurs immediately during or after boot

Key hardware‑level errors from journalctl:

  • ucsi_acpi USBC000:00: unknown error 256

  • ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)

  • ucsi_acpi USBC000:00: failed to register partner alt modes (-5)

  • ACPI BIOS Error (bug): Could not resolve symbol … AE_NOT_FOUND

These errors appear consistently and I think its instability in the USB‑C PD controller, EC firmware, or ACPI tables. Because they occur before the OS fully loads, they do not appear to be caused by software configuration.

CPU: 13th Gen Intel Core i5-1334U @ 12x 4.6GHz

GPU: Mesa Intel(R) Graphics (RPL-U)

Kernel: x86_64 Linux 7.3.0-rc2+

OS: Debian 13 trixieOS: Debian 13 trixie

I would appreciate assistance diagnosing this issue and figuring out if a mainboard replacement is required.

2

I assume this is the same issue as your last thread:

Have you raised a support ticket about this? The support folks will have a definitive way of determining if you have a hardware problem.

Are you still in warranty? Where are you based? (Your location determines the length of your warranty).

3

Can you check your mesa version? I had a problem just like this and it seems to be upstream Making sure you're not a bot!

Opening this website in Firefox has crashed every time for me: https://thelibre.news/no-really-dont-use-brave/

Updating to mesa 26.2.2 seems to do the job for me.

4

When did this start? There was a new bios for the 12 about a week ago.

5

when i said “recently” it was a stretch, probably about like, 6-ish months ago?

6

it is! i am in the US, and no support ticket yet, i wanted to try to find the problem on my own and with community help first to make sure im not just being stupid and the answer was right there the whole time and wasting support’s time lol

1 Like
7

i tried that once a while ago, i will try again when i have time though, i will probably post back here if it worked or not

8

OK, super. In the US you’ll have a one-year warranty. If you are in the latter part of that year, there may be value in getting a ticket in pronto, so you don’t run out of warranty while trying to figure it out! However if you’re not in warranty, then of course there is no major rush.

It sounds like you’ve tried a lot of things already. One more cheap thing to try is to order a new NVMe module - I found the other day that small capacity ones are not expensive at all. That would rule out disk image corruption or disk hardware faults.

Also, put memtest86 on a memory stick and test your RAM. I would tend not to suspect this in your case, but this also doesn’t use your OS or main drive, and it is easy enough to do, so I would still recommend it.

9

i already ran memtest, and ive wiped the current NVME multiple times, and ive tried booting from liveISO, still no, but yeah, i will try to get that warrenty thing in as soon as possible

1 Like