# \[RESPONDED\] AMD 7040 Linux - Boiling hot, stuck in sleep(?) **URL:** \ **Category:** Linux\ **Tags:** arch\ **Created:** [November 14, 2023, 4:04pm UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102 "2023-11-14T16:04:30Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Brod8362](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/brod8362/32/18542_2.png) [@Brod8362](https://community.frame.work/u/Brod8362)\ **Post date:** [November 14, 2023, 4:04pm UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/1 "2023-11-14T16:04:30Z")
Yesterday, I came back to my laptop absolutely boiling hot, too hot to touch. It was plugged in on a desk, fully charged. When I opened it, the LED blinking indicated sleep mode, but it did not wake on its own. I forcefully powered off by holding the button, then powered back on, and it booted normally with the fan blasting until things came down to temp. I don’t really have any reproduction steps, but after looking at other forum posts, I suspect I may have plugged it in after putting it to sleep - which is a known issue currently with the 7040 series. It seemed to stay in a half sleep/half running state, such that the fan did not turn on. I’m more or less just starting to document this in case other people experience it. If it happens again then I might be able to produce more specific reproduction steps. I’m not going to purposefully _try_ to reproduce this (for risk of hardware damage). Once I got into my OS I saw my SSD reading temperatures \> 60°C - I’m sure it was higher before, since that was after the fan was running for at least a minute or so. Didn’t catch CPU temperatures until they got into reasonable ranges (~55-60). - Arch Linux, kernel 6.6.1-arch1-1 - R5 7640U ---
**Author:** ![nadb](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/nadb/32/12102_2.png) [@nadb](https://community.frame.work/u/nadb)\ **Post date:** [November 14, 2023, 5:19pm UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/2 "2023-11-14T17:19:53Z")
> [@Brod8362](#): > > Arch Linux, kernel 6.6.1-arch1-1 Can almost guarantee this is the issue. I would never run a kernel on my daily before the 5th release. Try the lts or a kernel that is not on the first release revision. The other potential issue is an incorrectly configured sleep. Are you using LUKS encryption and have you made the necessary modification to allow for sleep? ---
**Author:** ![Brod8362](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/brod8362/32/18542_2.png) [@Brod8362](https://community.frame.work/u/Brod8362)\ **Post date:** [November 14, 2023, 5:33pm UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/3 "2023-11-14T17:33:57Z")
I’ve ran Arch linux as my main OS for years - rarely an issue. Especially on 7040 series, Framework themselves are pushing to run the newest kernels we possibly can. (Though that’s on Ubuntu/Fedora). However, I _am_ running LUKS encryption. I’ll double check and make sure I made that necessary change. Its worth noting I’ve been using the laptop just fine for ~ 2 weeks now, sleep and all. This is the first time this specific thing has occurred. The more I think about it, the more I think it’s the bug regarding plugging in a charger after already in sleep. I don’t think I’ve done that before last night. I just want to reiterate I’m not particularly concerned about it right now, I just wanted to document in case other people are looking/searching. ---
**Author:** ![tlvince](https://avatars.discourse-cdn.com/v4/letter/t/f05b48/32.png) [@tlvince](https://community.frame.work/u/tlvince)\ **Post date:** [November 14, 2023, 6:45pm UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/4 "2023-11-14T18:45:21Z")
> [@Brod8362](#): > > I suspect I may have plugged it in after putting it to sleep - which is a known issue currently with the 7040 series Sounds like you’re already aware, but you likely hit this: > [@\[TRACKING\] Framework AMD Ryzen 7040 Series lid wakeup behavior feedback](http://community.frame.work/t/tracking-framework-amd-ryzen-7040-series-lid-wakeup-behavior-feedback/39128): > > I configure my machines to not suspend on lid close, I only suspend on power button press. Nothing is plugged in except expansions. The issue is that after I suspend my machine and close the lid, it wakes up due to the lid close event. And besides that bug, personally I don’t want my suspend/resume to be controlled by the lid. For instance, I carry two laptops in my backpack, I don’t want the speaker magnet in one triggering the lid-open/close event on the other. This is happening at a BIOS/E… Currently, if you close the lid (to suspend the system) and plug in AC, the system will re-wake despite the lid still being closed. Fingers crossed this will be addressed in a firmware update, but in the meantime there’s a workaround (for Linux users): > [@\[TRACKING\] Framework AMD Ryzen 7040 Series lid wakeup behavior feedback](http://community.frame.work/t/tracking-framework-amd-ryzen-7040-series-lid-wakeup-behavior-feedback/39128/45): > > I put in the `/dev/rules.d/` folder: > > `/etc/udev/rules.d/20-suspend-fixes.rules` > > ```auto > ACTION=="add", SUBSYSTEM=="acpi", DRIVERS=="button", ATTRS{hid}=="PNP0C0D", ATTR{power/wakeup}="disabled" > ACTION=="add", SUBSYSTEM=="serio", DRIVERS=="atkbd", ATTR{power/wakeup}="disabled > > ``` > > The second line disables the keyboard from waking the PC, which fixes the lid waking the machine (along with the first line) _AND_ the AC being plugged in (which sends a keyboard wakeup as well). You lose the keyboard wake-ups but the touchpad and everything else work fine. Remove the first line to preserve wake on open. ---
**Author:** ![Matt\_Hartley](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/matt_hartley/32/13623_2.png) [@Matt\_Hartley](https://community.frame.work/u/Matt_Hartley)\ **Post date:** [November 14, 2023, 11:28pm UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/5 "2023-11-14T23:28:43Z")
First thing to note for others reading this (not OP, you are aware, this is for other readers): > [@Officially Supported vs Compatible Community Supported Linux Distributions](http://community.frame.work/t/officially-supported-vs-compatible-community-supported-linux-distributions/40041): > > Just a reminder as I see we have a lot of newcomers (welcome!). This was written to clarify how we support Linux and what that means to Framework users. Officially Supported Linux Distributions: Official support means we work with the Ubuntu and Fedora teams to do our best to avoid bugs and regressions. We provide official support for Ubuntu [22.04 LTS](https://guides.frame.work/Guide/Ubuntu+22.04+LTS+Installation+on+the+Framework+Laptop/109?lang=en) (OEM C kernel) release. We provide official support for [Fedora 38](https://guides.frame.work/Guide/Fedora+38+Installation+on+the+Framework+Laptop+13/165) (Intel) and [Fedora 39](https://guides.frame.work/Guide/Fedora+39+Installation+on+the+Framework+Laptop+13/217) (Intel, AMD). We provide consistently updat… That said, I’d see about adding this in GRUB: ```auto rtc_cmos.use_acpi_alarm=1 ``` You can run this script to dig into things a bit deeper. > **[scripts/amd\_s2idle.py · master · drm / amd · GitLab](https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/amd_s2idle.py)** > > amd (amdgpu, amdkfd, radeon) drm project, currently for issues only. ---
**Author:** ![Brod8362](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/brod8362/32/18542_2.png) [@Brod8362](https://community.frame.work/u/Brod8362)\ **Post date:** [November 15, 2023, 1:05am UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/6 "2023-11-15T01:05:02Z")
I’ll try setting that kernel parameter (as well as the second udev rule above) and report back if it happens again. Thanks for offering some help even for ‘unsupported’ distros. 🙂 ---
**Author:** ![Matt\_Hartley](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/matt_hartley/32/13623_2.png) [@Matt\_Hartley](https://community.frame.work/u/Matt_Hartley)\ **Post date:** [November 15, 2023, 5:07pm UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/7 "2023-11-15T17:07:57Z")
> [@Brod8362](#): > > I’ll try setting that kernel parameter (as well as the second udev rule above) and report back if it happens again. > > Thanks for offering some help even for ‘unsupported’ distros. 🙂 Happy to help! With a team of 2 people for Linux support, we do what we can. But we are focused on select distros due people power, time and a variety of other factors. Appreciate the update. ---
**Author:** ![denials](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/denials/32/18840_2.png) [@denials](https://community.frame.work/u/denials)\ **Post date:** [December 10, 2023, 11:04pm UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/8 "2023-12-10T23:04:55Z")
Thanks for posting this. I run into this today on Fedora 39 (13" AMD 7640). BIOS 3.3, 1TB SN850 SSD, DIY edition. Fully updated from the Fedora repos as of yesterday. Kernel = 6.5.6-300.fc39.x86\_64. Full disk encryption via LUKS. The only tweaks that I’ve made are to enable UMA\_GAME\_OPTIMIZED in the BIOS and to disable scatter/gather as a boot option (`amdgpu.sg_display=0`) to defend against the white screen corruption. Today I booted up, started up a GNOME session and Firefox, checked some mail, and left to go do some other chores. It was plugged into an Anker Prime 737 100w GaN wall charger (which has been working fine) on the back right USB-C port. There was a Logitech G903 unifying receiver plugged into the USB-A port on the front right. Nothing was plugged into the USB-C or USB-A ports on the left side. About two hours later, I came back to a black screen and the power button slowly flashing at me. It had gone into sleep mode on its own. Tapping keys, the power button, etc would wake not it up. The bottom was hot, as @Brod8362 reported, and the fan was not running. I tried closing the lid and plugging in an external monitor via USB-C to see if that would wake it up, but no dice. Like @Brod8362, I also had to long-press the power button to forcefully stop it, and on reboot the fan was blasting. Upon reboot, I checked **`Settings -> Power -> Automatic Suspend`** in GNOME Settings and it was set to automatically suspend after 15 minutes of inactivity even while plugged in. This is [a new default that Fedora set starting with Fedora 38](https://discussion.fedoraproject.org/t/gnome-suspends-after-15-minutes-of-user-inactivity-even-on-ac-power/79801). Note that changing it in the settings GUI doesn’t affect the behaviour of the login screen, which will continue to suspend after 15 minutes even while plugged in (per the linked post, `gdm` commands are required to affect that behaviour). However, that doesn’t explain why it wouldn’t wake back up, or why the temperature would rise so much while suspended. ---
**Author:** ![denials](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/denials/32/18840_2.png) [@denials](https://community.frame.work/u/denials)\ **Post date:** [December 11, 2023, 12:53am UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/9 "2023-12-11T00:53:13Z")
> [@denials](#): > > Fully updated from the Fedora repos as of yesterday. Kernel = 6.5.6-300.fc39.x86\_64. And now I’ve noticed that the default boot kernel is the oldest one, while the most recently installed kernel is 6.6.4-200.fc39.x86\_64. Weird, I’m used to Fedora automatically booting into the most recent kernel. Guess I’ll switch that up and see if it resolves these issues. Looks like the problem with the [default kernel not being the most recently installed kernel is a known issue with a resolution](http://community.frame.work/t/fedora-39-on-the-framework-laptop/37465/82). ---
**Author:** ![Matt\_Hartley](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/matt_hartley/32/13623_2.png) [@Matt\_Hartley](https://community.frame.work/u/Matt_Hartley)\ **Post date:** [December 11, 2023, 10:02pm UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/10 "2023-12-11T22:02:01Z")
> [@denials](#): > > Guess I’ll switch that up and see if it resolves these issues. Please do keep us posted. Thank you ---
**Author:** ![Thomas\_Weissschuh](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/thomas_weissschuh/32/19628_2.png) [@Thomas\_Weissschuh](https://community.frame.work/u/Thomas_Weissschuh)\ **Post date:** [February 20, 2024, 4:24am UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/11 "2024-02-20T04:24:21Z")
I have experienced the same behavior on `6.7.4-arch1-1`. ---
**Author:** ![Matt\_Hartley](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/matt_hartley/32/13623_2.png) [@Matt\_Hartley](https://community.frame.work/u/Matt_Hartley)\ **Post date:** [February 20, 2024, 6:33pm UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/12 "2024-02-20T18:33:55Z")
> [@Thomas\_Weissschuh](#): > > I have experienced the same behavior on `6.7.4-arch1-1`. Has this been tested with an earlier kernel? A release or two earlier for example? I’d also get this in front of [other arch users](http://community.frame.work/t/arch-linux-on-the-framework-laptop-16/44854/14) who may have some similar experiences. ---
**Author:** ![Thomas\_Weissschuh](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/thomas_weissschuh/32/19628_2.png) [@Thomas\_Weissschuh](https://community.frame.work/u/Thomas_Weissschuh)\ **Post date:** [February 20, 2024, 6:58pm UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/13 "2024-02-20T18:58:24Z")
> [@Matt\_Hartley](#): > > Has this been tested with an earlier kernel? I have been suspending this machine multiple times every day since I got it and never experienced this issue. (1st batch AMD). > [@Matt\_Hartley](#): > > I’d also get this in front of [other arch users](http://community.frame.work/t/arch-linux-on-the-framework-laptop-16/44854/14) who may have some similar experiences. For the record I’m on a 13’ 7840U device, without any peripherals. To be honest, if somebody experiences this I would expect them to report it. It is fairly scary, “boiling hot” is an apt description. ---
**Author:** ![Matt\_Hartley](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/matt_hartley/32/13623_2.png) [@Matt\_Hartley](https://community.frame.work/u/Matt_Hartley)\ **Post date:** [February 20, 2024, 8:20pm UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/14 "2024-02-20T20:20:44Z")
> [@Thomas\_Weissschuh](#): > > > [@Matt\_Hartley](#): > > > > Has this been tested with an earlier kernel? > > I have been suspending this machine multiple times every day since I got it and never experienced this issue. (1st batch AMD). > > > [@Matt\_Hartley](#): > > > > I’d also get this in front of [other arch users](http://community.frame.work/t/arch-linux-on-the-framework-laptop-16/44854/14) who may have some similar experiences. > > For the record I’m on a 13’ 7840U device, without any peripherals. > > To be honest, if somebody experiences this I would expect them to report it. > It is fairly scary, “boiling hot” is an apt description. As I am not experiencing this on Fedora, and I cannot repo it there. I wanted to better understand specific kernel releases as I feel like suspend isn’t happening at all. > [@Thomas\_Weissschuh](#): > > To be honest, if somebody experiences this I would expect them to report it. > It is fairly scary, “boiling hot” is an apt description. Ideally we work to get this done before it starts heating up. This means do not put the laptop into sleep. Instead, run this. I have seen this before when suspend is not happening correctly. Following this below, you should not see the heat issue. - Disconnect everything from the laptop. No docks, attached peripherals, just power is left attached. - Let’s start by looking at what the outcome [of this script](https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/amd_s2idle.py?ref_type=heads) happens to be. `sudo python3 amd_s2idle.py` I’d like to see the output of this specifically. A friendly reminder, Arch is a community support distro. So ideally, we would test this by installing an officially supported distro and seeing if the behavior happens there. If it does, we’d suggest opening a ticket, linking to this thread and we now suspect hardware. If works correctly on a fully installed, fully updated install of Fedora, this is an Arch bug that would need to be reported. ---
**Author:** ![ryanpetris](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/ryanpetris/32/6963_2.png) [@ryanpetris](https://community.frame.work/u/ryanpetris)\ **Post date:** [February 20, 2024, 8:51pm UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/15 "2024-02-20T20:51:45Z")
I actually don’t usually let my machines sleep. When I’m not using them, I power it off. It’s a habit I got into a long time ago in college when I came home to a hot macbook (a core 2 duo pre-unibody) that had been cooking in my backpack for a while. After that I’ve never trusted sleep. I _can_ put my machine to sleep and it appears to be sleeping, but I haven’t left it long enough like that to see if it goes into egg cooker mode. ---
**Author:** ![Edward\_Gray](https://avatars.discourse-cdn.com/v4/letter/e/c4cdca/32.png) [@Edward\_Gray](https://community.frame.work/u/Edward_Gray)\ **Post date:** [February 21, 2024, 4:18pm UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/16 "2024-02-21T16:18:46Z")
> [@ryanpetris](#): > > I actually don’t usually let my machines sleep. When I’m not using them, I power it off. My first actual computers were Atari 800’s and 286 PC-DOS PC’s. No opportunity to sleep or hibernate on either of those. I learned to save work, exit applications and shut them down when done. Still do that today. My FW13 Batch 1 11th Gen boots fast enough for me, and I do a variety of things, so I don’t want it to come up with other than a home screen. ---
**Author:** ![denials](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/denials/32/18840_2.png) [@denials](https://community.frame.work/u/denials)\ **Post date:** [March 16, 2024, 12:14am UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/17 "2024-03-16T00:14:26Z")
Sorry, I should have responded much earlier that booting into the newer kernel on Fedora resolved the issue. ---
**Author:** ![Matt\_Hartley](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/matt_hartley/32/13623_2.png) [@Matt\_Hartley](https://community.frame.work/u/Matt_Hartley)\ **Post date:** [March 20, 2024, 6:48pm UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/18 "2024-03-20T18:48:12Z")
> [@denials](#): > > Sorry, I should have responded much earlier that booting into the newer kernel on Fedora resolved the issue. Fantastic! Delighted to hear this. Mark this one for Fedora. Arch users, how is testing on [linux-lts](https://archlinux.org/packages/core/x86_64/linux-lts/) going for testing? ---
**Author:** ![pyguydev](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/pyguydev/32/4101_2.png) [@pyguydev](https://community.frame.work/u/pyguydev)\ **Post date:** [May 26, 2024, 7:00pm UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/19 "2024-05-26T19:00:03Z")
I’m on the most recent Kernel for Fedora 39 and I still continue to have this problem. I ran the aforementioned script and everything is where it should be. I was working in IntelliJ doing some work and left it for 30 or so minutes, came back, boiling hot. This behavior also happens when I’m running Windows, once it goes to sleep and stays in sleep for any significant amount of time, I can flip it upside down and cook my breakfast on it…kinda scary! ---
**Author:** ![namelivia](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/namelivia/32/27049_2.png) [@namelivia](https://community.frame.work/u/namelivia)\ **Post date:** [June 17, 2024, 10:26pm UTC](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102/20 "2024-06-17T22:26:48Z")
Same here, using Archlinux and the most recent kernel, I was running out of battery so I put the computer in sleep mode, plugged in the charger and walked away. I forgot about it and walked back several hours later and the laptop was hot to touch, really really hot /,and the fan was off. It didn’t resume so I just held the power button to turn it off. [Next page](https://community.frame.work/t/responded-amd-7040-linux-boiling-hot-stuck-in-sleep/40102.md?page=2)