Created attachment 260777 [details] output of lspci -vvv This bug was introduced in my jump from the 4.9 kernel to the 4.12 kernel. What seems to happen is that it will enter the correct CPU state initially, but then seems to enter a slightly higher CPU state after a few seconds. The laptop stays warm, instead of cooling down during the suspend state like it used to. I have attached the contents of `lspci -vvv`. If more information is required. I would be more than happy to help. Just give me the commands to run and I am on it. General specs of laptop: OS: Solus x86_64 Host: 20C0S19700 ThinkPad S1 Yoga Kernel: 4.13.15-34.current CPU: Intel i7-4600U (4) @ 3.300GHz GPU: Intel Integrated Graphics
Please provide the full dmesg across the suspend/resume, with no_console_suspend appended in the grub command line, both under 4.9 and the failing one. BTW, are you using suspend to mem or suspend to idle?
ping
I believe I am using suspend to idle, but I am not completely sure. I am sorry for the lack of communication. Been focused on school work recently. I am including a text file of things I saw in dmesg. I grepped for suspend, resume, and sleep. Along with those I have also included any red error messages from when my computer first booted up. Interesting point to note is that when I put my laptop to suspend the Bluetooth comes on regardless of the setting I am using pre-resume. I have also included relevant lines for that. Let me know if you are missing something or would like a full log. These are the 4.14 logs. I went ahead and included the full dmesg as well. I will work on getting the 4.9 logs.
Created attachment 261099 [details] full dmesg
Created attachment 261101 [details] grepped error messages
(In reply to Tristan Partin from comment #4) > Created attachment 261099 [details] > full dmesg It resumed from S3 normally according to the log: [10625.489887] ACPI: Waking up from system sleep state S3 Please describe a little more about: "it will enter the correct CPU state initially, but then seems to enter a slightly higher CPU state after a few seconds." Does "enter higher CPU state" mean "wake up from suspend to mem"? How about unloading the wifi/bluetooth driver
Ok so, its hard to explain, but I'll try. My laptop is a ThinkPad. On the lid of my ThinkPad, there is a light. Up until my upgrade to 4.12, when I put my laptop to suspend, this light would pulsate very slowly on and off. Now that light just stays on forever while in suspend. The CPU no longer goes to the state it used to go to. My laptop will feel like it never went to suspend because it is still warm, while in the 4.9 days my CPU temperature would cool down to almost room temp. Any ideas? The Bluetooth issue has been going on for as long as I have had this laptop. Just thought I would include it anyway, so I know that is not the issue.
(In reply to Tristan Partin from comment #7) > Ok so, its hard to explain, but I'll try. My laptop is a ThinkPad. On the > lid of my ThinkPad, there is a light. Up until my upgrade to 4.12, when I > put my laptop to suspend, this light would pulsate very slowly on and off. this sounds like ACPI S3. > Now that light just stays on forever while in suspend. and this sounds like ACPI S0. so please attach the output of "grep . /sys/power/*" in both kernels.
Created attachment 261105 [details] ouput of grep sys power 4.14
Added an attachment. I am currently in talks with my distribution maintainers on how I can best proceed with booting the 4.9 kernel. I'll need a little time to receive feedback, but I should be able to get those to you soon.
(In reply to Tristan Partin from comment #10) > Added an attachment. I am currently in talks with my distribution > maintainers on how I can best proceed with booting the 4.9 kernel. I'm confused, I think everything works well on 4.9, and you got suspend failure in 4.12. please try echo {core, processors, platform, devices, freezer} > /sys/power/pm_test and wait for like 5 seconds, and see if the system resumes back properly,
Getting a write error. Invalid argument. I don't know what to tell you. 4.9 used to suspend properly except for the bluetooth issue.
(In reply to Zhang Rui from comment #11) > (In reply to Tristan Partin from comment #10) > > Added an attachment. I am currently in talks with my distribution > > maintainers on how I can best proceed with booting the 4.9 kernel. > > I'm confused, I think everything works well on 4.9, and you got suspend > failure in 4.12. > > please try > echo {core, processors, platform, devices, freezer} > /sys/power/pm_test you need to run echo core > /sys/power/pm_test and see if the system resumes automatically afte around 10 seconds, if no, please try echo processors > /sys/power/pm_test if still fails, try echo platform > /sys/power/pm_test if still fails, try echo devices > /sys/power/pm_test if still fails, try echo freezer > /sys/power/pm_test
None of these provided any significant changes. core made the light blink for 10 seconds then go solid. processors made the light solid for about 10 seconds then it started blinking for a bit.
(In reply to Tristan Partin from comment #14) > None of these provided any significant changes. core made the light blink > for 10 seconds then go solid. what does "go solid" mean? does the machine resume successfully or not, when you say the light go solid? ? processors made the light solid for about 10 > seconds then it started blinking for a bit. then does the system resume successfully?
And please attached the dmesg after each run.
ping ...
Bug closed as there is no response from the bug reporter. Please feel free to reopen it if you can provide the information requested in comment #15 and #16.