Which Framework Laptop 13 model are you using? (AMD Ryzen™ AI 300 Series, AMD Ryzen™ 7040 Series, Intel® Core™ Ultra Series 1, 13th Gen Intel® Core™ , 12th Gen Intel® Core™, 11th Gen Intel® Core™) AMD Ryzen AI 9 HX 370 w/ Radeon 890M
Hello, first time poster, but first time having issues, and this really surprised me.
I got two kernel panics in the span of 10 minutes yesterday. The first one just had the whole screen freeze, with the caps lock LED blinking. After a reboot and starting to code again, it locked up a second time, which I got on video.
For the time being, I’ve just booted off of an older kernel via the GRUB boot menu, and I’m currently running 6.17.6 without issues, but I’ll report back if I encounter any.
I attempted to grab the kernel log using journalctl -b-1 -k, which I’ve attached here: The Zig Pastebin
I’m not quite sure what to do next, aside from just continuing to run kernel 6.17.6 for the time being.
what bios version is this? also please tell us which laptop gen you’re using?
i also dont think having a 100+ lines of this is good? but i will check my kernel logs (please note that i have a fwl16)
Nov 15 15:12:16 flawless-fedora-laptop kernel: xhci_hcd 0000:c3:00.0: Refused to change power state from D0 to D3hot
Nov 15 15:12:17 flawless-fedora-laptop kernel: pcieport 0000:00:08.3: PME: Spurious native interrupt!
Nov 15 15:12:17 flawless-fedora-laptop kernel: xhci_hcd 0000:c3:00.0: Refused to change power state from D0 to D3hot
Nov 15 15:12:18 flawless-fedora-laptop kernel: xhci_hcd 0000:c3:00.0: Refused to change power state from D0 to D3hot
Nov 15 15:12:20 flawless-fedora-laptop kernel: xhci_hcd 0000:c3:00.0: Refused to change power state from D0 to D3hot
Nov 15 15:12:21 flawless-fedora-laptop kernel: xhci_hcd 0000:c3:00.0: Refused to change power state from D0 to D3hot
Nov 15 15:12:25 flawless-fedora-laptop kernel: xhci_hcd 0000:c3:00.0: Refused to change power state from D0 to D3hot
yeah i only see this as a concern on my fwl16 ucsi_acpi USBC000:00: unknown error 0
Nov 16 18:00:14 fwl16-laptop16 kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
but i see that on every boot and it can usally charge also could be that i dont have an expansion card in one slot and the -5 is the slot that i have nothing in (slot 5)
That’s the bios version shown by fwupdmgr, for my Framework 13, 2025 edition.
None, at least none connected to the expansion cards. Perhaps those messages for coming from the connected expansion card slots. I’ve got two of the USB-C expansion slots plugged in, one of the USB-A, and the mini SD card.
Update: I narrowed down the source of the xhci_hcd 0000:c3:00.0: Refused to change power state from D0 to D3hot errors. It’s the left hand side, closest (to the user) expansion port. The one closest to the audio jack. I’ve plugged in both a USB-A adapter and my SD card adapter to that adapter port, and both start spamming the kernel log. But if I plug them into the same port on the right hand side, there are no such errors.
Update 2: The error doesn’t appear to happen if I have the USB-C expansion card plugged into that slot. I’ve simply swapped the SD Card expansion so that it’s in the back left adapter, and placed the USB-C expansion into the front left adapter. Kernel logs seem to have stopped and all the same devices are plugged in, just in a different order.
However, those errors (while annoying) might be a red herring for the crashes, as they also show up on the 6.17.6 kernel, but I’m not experiencing any crashes.
I don’t think your journalctl output contains info about the kernel panic(s). Depending on how bad the kernel is crashing, it may not have any ability to output an error.
Given that it was able to put something on the screen, you can look in /sys/fs/pstore/ or /var/lib/systemd/pstore/ (you may need to lookup if fedora has configured pstore capability - it likely has - and where the pstore directory is located). Directories under pstore may contain dmesg.txt files with some debugging info from prior crashes.
If you do find some dmesg.txt files, look through those for kernel panics. If you find something, try searching through fedora’s forums as you may find others have experienced similar issues.
Waiting it out on a older kernel until the next kernel update is likely the easiest thing to do.
In short, it seemed stable for a few hours of work. I closed the laptop lid, thereby putting it into sleep. When I opened the lid again a few hours later, it was frozen on the lock screen. No response from any key presses, including the power button, which I pressed multiple times.
Finally had to hold down the power button for a long period (actually twice, since it kinda “bounced” as in the screen went black then back to the frozen login screen) in order to get the laptop to shut down properly.
So I’m back on 6.17.6.
Interestingly, Fedora reported some crashes when I first booted into 6.17.8, and then when I rebooted back into 6.17.6. I submitted reports, and the reporter tool was able to find some existing known issues: