[RESPONDED] Linux Kernel Panic [AMD Framework 13, Ubuntu]

Framework Laptop 13 Linux
1

Hi all,

I installed Ubuntu 22.04 (I believe) on my Framework 13 AMD laptop (latest gen), and have been encountering kernel panics on every other startup. I’ll post my setup and a picture of what happened below.

I’m a newcomer to Linux (and using the Terminal), so please bear with me–if I have left something out or don’t know how to do something, please let me know.

Thank you all, I appreciate the help!

Specifications:
Framework 13 Laptop

AMD Ryzen 5 7640U

RAM: Crucial CT2K16G56C46S5 (32GB, 5600-SODIMM), taken from the supported RAM list.

Memory: WD Black SN850X 2TB

Linux version: Ubuntu 22.04

OEM: 6.5.0-1015 (I ran the uname -r command as instructed by the Ubuntu guide).

If it helps, here is the picture of the error message. It only shows up every other reboot.

PXL_20240226_025914851
PXL_20240226_0259148511920×1446 313 KB

1 Like
2

Welcome to the community!

1 Like
3

Welcome to the community! Sounds like you have done everything right. Can you walk me through any changes or updates that brought you to this state?

  • At what stage did this take place? Was this immediately after you setup the OEM kernel and ran updates? Did this happen later on merely after running updates? Did anything with hardware change anywhere along the line?

  • Do you have access to another NVMe drive to test against? I have a sneaking suspicion the drive is related here, but it would be interesting to see if there is different behavior here. If not, I can look and see find one in my office and see if I can replicate. I don’t think I have one readily available to test against myself.

4

Hey Matt, thanks so much for getting back to me so promptly.

IIRC, I think this happened some time after I finished the the completion guide and then installed updates. The first few boots were fine.

I think this started happening probably on my fourth or fifth time rebooting, and since then, it’s been happening every other time. Also, I haven’t done anything to the hardware after the initial setup.

I don’t have another NVMe drive, but I can order another one to test it against, if you think it makes sense. Or do you think I should go through the drive installation process again? Maybe take out the drive and slot it back in and see if that changes anything?

Thanks again for the help! Very cool to get an answer directly from Matt himself :smile:

5

Hello,

Don’t know if it helps but I think that maybe I have the same issue. I have been using this laptop for a while now (part of the 1st batch) so I don’t think it’s an hardware issue. I mindlessly update everything and I often reboot when I see a kernel updates so maybe it’s not related but that’s when I saw this kernel panic for the first time. Seems to be very consistent i.e. reset, warm boot, panic, hard reset, cold boot, OK, restart, warm boot, panic, hard reset, cold boot, OK…

It only happens when I select “ubuntu” after a reset but I never saw a panic when I select a specific kernel. I do not always get the exact same error (see both pictures) but because one seems to be related to the efi_store, I checked the content here but I am unsure of what I see or if it could be related:

$ sudo find efi
efi
efi/EFI
efi/EFI/ubuntu
efi/EFI/ubuntu/grubx64.efi
efi/EFI/ubuntu/shimx64.efi
efi/EFI/ubuntu/mmx64.efi
efi/EFI/ubuntu/BOOTX64.CSV
efi/EFI/ubuntu/grub.cfg
efi/EFI/ubuntu/fw
efi/EFI/ubuntu/fw/fwupd-b5f7dcc1-568c-50f8-a4dd-e39d1f93fda1.cap
efi/EFI/ubuntu/fwupdx64.efi
efi/EFI/BOOT
efi/EFI/BOOT/BOOTX64.EFI
efi/EFI/BOOT/fbx64.efi
efi/EFI/BOOT/mmx64.efi
efi/EFI/UpdateCapsule

small_1
small_1806×605 164 KB

small_2
small_2806×605 226 KB

6

Hi, did you solve your problem? I have the same issue here…

7

Having the same issue. Ubuntu 22.04.4. very similar behavior to what @Eric_Robert described

8

I’m also seeing this issue intermittently. I think it started after upgrading to the latest kernel version (6.5.0-1022-oem). @Matt_Hartley Any ideas how to debug the issue?

9

Appreciate everyone’s efforts.

If you are able to get booted into things after the second attempt, let’s make sure we can get logs.

journalctl --disk-usage

if you see something like “Archived and active journals take up, blah, blah, blah” we’re ready to get those logs even if it was a failed boot. This should still work.

journalctl -b -1 > previous_boot.log && tar -czvf previous_boot_logs.tar.gz previous_boot.log && rm previous_boot.log

Then open a support ticket, when support replies to you asking for logs, use the previous_boot_logs.tar.gz and also link to this thread.

10

Hi All,

I have a Framework 13 with an AMD Ryzen 7 7840U chipset running Pop!_OS only (which is an Ubuntu-based Linux distro).

It is a constant up and down with this machine.
In the beginning, the machine worked more or less flawlessly (a few times the screen had some weird patterning and was freezing, but that went away over time, most likely through an OS or BIOS update).
Then I had huge troubles with the AMD MediaTek wifi card that shipped with the machine.
I tried to update with the newest firmware as suggested in some post, but that only solved the problem for a while before it came back. So I replaced the wifi card with an Intel AX210 wifi card, which definitely seems to work better. However, the basic problem persists. The wifi card acts like a “capacitor“. The card works fine for one, two, or three weeks. Then it stops working. Then I have to shut the laptop totally down, unplug all expansion cards, open the laptop, unplug the wifi card, plug the wifi card back in, and screw and plug the laptop together again, and the laptop works fine for one, two, or three weeks.
Now, recently (most probably after an OS update), the machine started to have kernel panics with a purple screens and random shutdowns. Ah yes, and I had trouble connecting it to HDMI. This weekend I already planned to take the whole laptop apart to properly plug it together again, in the hope all of this might have been caused by a hardware connection issue. However, two days ago, I did another sudo apt update sudo apt upgrade, in the hope that maybe a new kernel was out. There was only one library to update, and it was bind9 (bind9-host, bind9-libs, and libc-bin) and magically this seems to solve for the moment all problems I have. No more kernel panic, no more random shutdowns, no more wifi problems. (ok, I have not yet checked if the HDMI plug now works again).

These are my current coordinates (maybe helpful):

  • Framework 13 with an AMD Ryzen 7 7840u
  • Firmawre 0.0.3.16 (2025-07-25)
  • Intel AX210 no vPro wifi card
  • Pop!_OS 22.04 LTS
  • Linux kernel: 6.16.3-76061603-generic
  • bind9-[host|libs]:amd64 1:9.18.39-0ubuntu0.22.04.1
  • libc-bin:amd64 2.35-0ubuntu3.11

Additionally, I had an issue with a cracked keyboard key that was not my fault and got replaced by Framework after a back-and-forth emailing and sending several pictures of the cracked keyboard. And I had an issue with a cracked display that was totally my fault and replaced by myself.

So, what is it? I hardly had so much different trouble running a Linux machine.
Is it the hardware / chipset?
Is it how the hardware is plugged together?
Is it a software issue?
I not really can pin it down. I really don’t get it.
I need my machine for work. It is a very powerful machine, and I love this machine when everything works smoothly! But when it has its hiccup time and you should finish some work with a deadline or give a presentation or what ever …
Several times my boss recommended I get an off-the-shelf Windows11 machine, and I played with the thought of getting once again a Lenovo T series, the classic choice from back in the day. But hej, I run this Framework 13 with an AMD Ryzen 7 7840u for about 2 years. Shelf life should really not be over for this machine. As I bought it, I expected to run it for at least 4, if not 5 years :”(.
For the moment I just pray that the machine will now keep running smoothly for a while again, hopefully longer than short.

Best, Elmar