# Regression: Framework 13 Ryzen 340 doesn't wake from suspend on v6.15-rc4 works fine on v6.14.4

**URL:** <https://community.frame.work/t/regression-framework-13-ryzen-340-doesnt-wake-from-suspend-on-v6-15-rc4-works-fine-on-v6-14-4/68514>\
**Category:** Linux\
**Tags:** arch\
**Created:** [April 30, 2025, 8:53pm UTC](https://community.frame.work/t/regression-framework-13-ryzen-340-doesnt-wake-from-suspend-on-v6-15-rc4-works-fine-on-v6-14-4/68514 "2025-04-30T20:53:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Niklas\_Schnelle](https://avatars.discourse-cdn.com/v4/letter/n/c77e96/32.png) [@Niklas\_Schnelle](https://community.frame.work/u/Niklas_Schnelle)\
**Post date:** [April 30, 2025, 8:53pm UTC](https://community.frame.work/t/regression-framework-13-ryzen-340-doesnt-wake-from-suspend-on-v6-15-rc4-works-fine-on-v6-14-4/68514/1 "2025-04-30T20:53:11Z")

</div>

A bit of a PSA and warning. Looks like there is an issue with the upcoming Linuv v6.15 kernel.  
I’m on Arch Linux and apart from the WiFI IPv6 issue in my other post the official v6.14.1 kernel works great. Built a fresh v6.15-rc4 release candidate for testing (I’m a Linux Kernel developer) and it was running ok.

Just noticed however that when waking from suspend the system gets stuck. I still saw my mouse pointer but it’s not moving anymore. Haven’t set up an SSH server yet so not sure if it’s just the graphics stack or the whole system. Might have to bisect this but will have to find the time. So if anyone including folks from Framework want to go on a good bug hunt…

Thanks,  
Niklas

---

<div class="post-metadata">

**Author:** ![Niklas\_Schnelle](https://avatars.discourse-cdn.com/v4/letter/n/c77e96/32.png) [@Niklas\_Schnelle](https://community.frame.work/u/Niklas_Schnelle)\
**Post date:** [May 1, 2025, 9:47am UTC](https://community.frame.work/t/regression-framework-13-ryzen-340-doesnt-wake-from-suspend-on-v6-15-rc4-works-fine-on-v6-14-4/68514/2 "2025-05-01T09:47:15Z")

</div>

Good news, I found an LKML [thread](https://lore.kernel.org/lkml/CADDYkjR0JG_JTQeQMAvUJvtb9RxFH6_LzV2Fr_1cnqPTgV_Z8w@mail.gmail.com/) for what sounded like a similar issue. Reverting the broken commit mentioned in the thread works for me too, so hopefully this should still get fixed before v6.15 is released 🙂

---

<div class="post-metadata">

**Author:** ![Mario\_Limonciello](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mario_limonciello/32/19277_2.png) [@Mario\_Limonciello](https://community.frame.work/u/Mario_Limonciello)\
**Post date:** [May 1, 2025, 1:56pm UTC](https://community.frame.work/t/regression-framework-13-ryzen-340-doesnt-wake-from-suspend-on-v6-15-rc4-works-fine-on-v6-14-4/68514/3 "2025-05-01T13:56:14Z")

</div>

Here’s the correct fixes:

> **[\[PATCH 1/3\] ASoC: amd: acp: Fix NULL pointer deref on acp resume path -...](https://lore.kernel.org/linux-sound/20250425060144.1773265-1-venkataprasad.potturu@amd.com/)**

They should make it in before 6.15 final.

---

<div class="post-metadata">

**Author:** ![Niklas\_Schnelle](https://avatars.discourse-cdn.com/v4/letter/n/c77e96/32.png) [@Niklas\_Schnelle](https://community.frame.work/u/Niklas_Schnelle)\
**Post date:** [May 1, 2025, 9:22pm UTC](https://community.frame.work/t/regression-framework-13-ryzen-340-doesnt-wake-from-suspend-on-v6-15-rc4-works-fine-on-v6-14-4/68514/4 "2025-05-01T21:22:15Z")

</div>

Will test this, thanks. I had to go back to 6.14.4 because I was still getting a crash also in the sound system, looked possibly related, so I was already waiting for a proper fix. Also nice to see AMD kernel maintainers here!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/1X/64c81a89f963ddb07633887baceb642a4b056046.png) [@system](https://community.frame.work/u/system)\
**Post date:** [October 28, 2025, 9:22pm UTC](https://community.frame.work/t/regression-framework-13-ryzen-340-doesnt-wake-from-suspend-on-v6-15-rc4-works-fine-on-v6-14-4/68514/5 "2025-10-28T21:22:41Z")

</div>

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.
