# Intermittent failure to suspend Framework 13 AMD Ryzen

**URL:** <https://community.frame.work/t/intermittent-failure-to-suspend-framework-13-amd-ryzen/54656>\
**Category:** Linux\
**Tags:** debian\
**Created:** [July 16, 2024, 6:47pm UTC](https://community.frame.work/t/intermittent-failure-to-suspend-framework-13-amd-ryzen/54656 "2024-07-16T18:47:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Paul\_LeoNerd\_Evans](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/paul_leonerd_evans/32/27153_2.png) [@Paul\_LeoNerd\_Evans](https://community.frame.work/u/Paul_LeoNerd_Evans)\
**Post date:** [July 16, 2024, 7:31pm UTC](https://community.frame.work/t/intermittent-failure-to-suspend-framework-13-amd-ryzen/54656/2 "2024-07-16T19:31:28Z")

</div>

Hah - wow, and just after I wrote that I managed to make it suspend correctly. This was during the same session, without having rebooted inbetween. This time the messages are:

```auto
[34137.910376] Freezing user space processes
[34137.917759] Freezing user space processes completed (elapsed 0.007 seconds)
[34137.917768] OOM killer disabled.
[34137.917771] Freezing remaining freezable tasks
[34137.919068] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[34137.919072] printk: Suspending console(s) (use no_console_suspend to debug)
[34138.489532] ACPI: EC: interrupt blocked
[36379.313944] ACPI: EC: interrupt unblocked
[36379.507573] nvme nvme0: 16/0/0 default/read/poll queues

```

And in particular, the last message before suspend was the “ACPI: EC: interrupt blocked”, and much later (by timestamps) the “ACPI: EC: interrupt unblocked” with no complaint about not reaching deepest state inbetween.

This does suggest that’s where the problem lies, though doesn’t point at what might fix it.

---

_[View the full topic](https://community.frame.work/t/intermittent-failure-to-suspend-framework-13-amd-ryzen/54656)._