# Framework 13 keeps locking up, almost nonfunctional **URL:** \ **Category:** Linux\ **Tags:** fedora\ **Created:** [April 26, 2025, 2:26pm UTC](https://community.frame.work/t/framework-13-keeps-locking-up-almost-nonfunctional/68263 "2025-04-26T14:26:50Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Spyros\_Heniadis](https://avatars.discourse-cdn.com/v4/letter/s/54ee81/32.png) [@Spyros\_Heniadis](https://community.frame.work/u/Spyros_Heniadis)\ **Post date:** [April 26, 2025, 2:26pm UTC](https://community.frame.work/t/framework-13-keeps-locking-up-almost-nonfunctional/68263/1 "2025-04-26T14:26:50Z")
My 13" DIY edition has become essentially nonfunctional. What happens is after a period of use, the laptop locks up completely, the led in the capslock key starts flashing, and if audio was playing the speaker will repeatedly emit a sort of ticking sound. The only remedy when this happens is to force shutdown the machine with the power button. It started intermittently, in which case I thought it was a one off problem, but as of the last couple of days it’s happening frequently enough that it’s rendering the machine unusable. The last occurrence was this morning approximately 5am local time when I used the laptop to browse the web for approximately ten minutes before the machine locked up again. I’m not sure if this is related or useful, but here is the output of `journalctl -k -b -l -p err` ```auto Apr 26 05:06:00 fedora kernel: ucsi_acpi USBC000:00: unknown error 0 Apr 26 05:06:00 fedora kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5) Apr 26 05:06:01 fedora kernel: ucsi_acpi USBC000:00: unknown error 256 Apr 26 05:06:01 fedora kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5) Apr 26 05:06:01 fedora kernel: ucsi_acpi USBC000:00: unknown error 256 Apr 26 05:06:01 fedora kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5) Apr 26 05:06:03 fedora kernel: failed to load firmware /amdtee/f29bb3d9-bd66-5441-afb88acc2b2b60d6.bin Apr 26 05:06:03 fedora kernel: failed to copy TA binary Apr 26 05:06:03 fedora kernel: Failed to open TEE session err:0x0, rc:-12 Apr 26 05:06:03 fedora kernel: amd-pmf AMDI0102:00: Failed to open TA session (-12) Apr 26 05:06:03 fedora kernel: cros_ec_lpcs cros_ec_lpcs.0: packet too long (4 bytes, expected 0) Apr 26 05:06:03 fedora kernel: cros-usbpd-charger [cros-usbpd-charger.7.auto](http://cros-usbpd-charger.7.auto/): Unexpected number of charge port count Apr 26 05:06:03 fedora kernel: cros-usbpd-charger [cros-usbpd-charger.7.auto](http://cros-usbpd-charger.7.auto/): probe with driver cros-usbpd-charger failed with error -71 ``` The timestamp on these errors correspond with it locking up this morning after the approximately 10 minutes of usage. I’m not sure how useful this is, but [here is a pastebin of the full dmesg output](https://pastebin.com/DL1Kwut3) Below are the system details: # System Details Report * * * ## Report details - **Date generated:** 2025-04-26 07:50:03 ## Hardware Information: - **Hardware Model:** Framework Laptop 13 _AMD Ryzen 7040Series_ - **Memory:** 32.0 GiB - **Processor:** AMD Ryzen™ 5 7640U w/ Radeon™ 760M Graphics × 12 - **Graphics:** AMD Radeon™ 760M - **Disk Capacity:** 1.0 TB ## Software Information: - **Firmware Version:** 03.05 - **OS Name:** Fedora Linux 41 (Workstation Edition) - **OS Build:** (null) - **OS Type:** 64-bit - **GNOME Version:** 47 - **Windowing System:** Wayland - **Kernel Version:** Linux 6.13.12-200.fc41.x86\_64 Any help resolving this would be greatly appreciated ---
**Author:** ![Spyros\_Heniadis](https://avatars.discourse-cdn.com/v4/letter/s/54ee81/32.png) [@Spyros\_Heniadis](https://community.frame.work/u/Spyros_Heniadis)\ **Post date:** [April 26, 2025, 3:06pm UTC](https://community.frame.work/t/framework-13-keeps-locking-up-almost-nonfunctional/68263/2 "2025-04-26T15:06:35Z")
New update. I had booted the machine back up an hour or so after it locked up around 5am, and after using it for a few minutes, I closed the lid to put it in suspend. About 20 minutes ago I picked it up and opened the lid and it was unresponsive. Pressing the power button would cause the button itself to light up, but nothing would appear on the display, and there was no response to keyboard or touchpad input. I held down the power button to force shut it down, waited about a minute, and tried to boot it back up again. The power button lit up, and after sitting for at least a minute, there was no boot activity at all. I again forced shutdown by holding the power button until the light went off, waited around five minutes, and tried again. Same response. Forced shutdown one more time and waited around 20 minutes, and this time it booted up again. I’ll see how long it operates before locking up again. ---
**Author:** ![Spyros\_Heniadis](https://avatars.discourse-cdn.com/v4/letter/s/54ee81/32.png) [@Spyros\_Heniadis](https://community.frame.work/u/Spyros_Heniadis)\ **Post date:** [April 26, 2025, 6:55pm UTC](https://community.frame.work/t/framework-13-keeps-locking-up-almost-nonfunctional/68263/3 "2025-04-26T18:55:35Z")
Now it appears to be bricked. I attempted to upgrade the firmware, and it’s been stuck on the “Please keep AC and battery attached while updating” screen for almost three hours now. The battery was fully charged and the AC was plugged in when I started the upgrade process. ---
**Author:** ![James3](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@James3](https://community.frame.work/u/James3)\ **Post date:** [April 26, 2025, 7:24pm UTC](https://community.frame.work/t/framework-13-keeps-locking-up-almost-nonfunctional/68263/4 "2025-04-26T19:24:28Z")
This forum is for other users and only rarely gets input from FW people. It sounds like you need a new mainboard to me. The way to do that is to contact FW support via their Web site. ---
**Author:** ![Spyros\_Heniadis](https://avatars.discourse-cdn.com/v4/letter/s/54ee81/32.png) [@Spyros\_Heniadis](https://community.frame.work/u/Spyros_Heniadis)\ **Post date:** [April 26, 2025, 8:24pm UTC](https://community.frame.work/t/framework-13-keeps-locking-up-almost-nonfunctional/68263/5 "2025-04-26T20:24:57Z")
Thanks James3. I also suspect I need a new mainboard. I emailed support before posting here, and the autoresponder said they respond quicker to posts in the forums, so I also posted here. I plan to call on Monday. ---
**Author:** ![dimitris](https://avatars.discourse-cdn.com/v4/letter/d/db5fbb/32.png) [@dimitris](https://community.frame.work/u/dimitris)\ **Post date:** [April 26, 2025, 9:50pm UTC](https://community.frame.work/t/framework-13-keeps-locking-up-almost-nonfunctional/68263/6 "2025-04-26T21:50:48Z")
The messages in both of your logs don’t show anything known to be suspicious (amdtee and cros stuff is known and “benign”). There _is_ a known `amdgpu` problem that is causing a lot of pain out there on AMD machines, not exclusive to Framework: > [@Alt+tab induced crashes on FW13 AMD Ryzen 7040 Fedora 42 (amdgpu bug)](https://community.frame.work/t/alt-tab-induced-crashes-on-fw13-amd-ryzen-7040-fedora-42-amdgpu-bug/68214): > > Hi all, I am new to linux, so please don’t judge too harshly. I have recently updated to Fedora 42, and I have noticed a pattern: when I use alt+tab to switch between windows, there is a small chance that the entire system will crash. I haven’t noticed anything specific, but journalctl -b -1 -p3 consistently gives the following last errors: Apr 25 18:04:54 fwrk kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc\_dmub\_srv\_log\_diagnostic\_data: DMCUB error - collecting diagnostic data Apr 25 18:04:54 f… Maybe double check logs for those `amdgpu` errors? `journalctl -b -1 -k` for previous boot’s `dmesg` etc. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/1X/64c81a89f963ddb07633887baceb642a4b056046.png) [@system](https://community.frame.work/u/system)\ **Post date:** [October 23, 2025, 9:51pm UTC](https://community.frame.work/t/framework-13-keeps-locking-up-almost-nonfunctional/68263/7 "2025-10-23T21:51:11Z")
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.