Bug 1467289

The problem is still present even after the upgrade to Fedora 26.

Created attachment 1326117 [details]
system log

this is the log from when I press the power button in order to suspend. until it resumes and crashes. I cannot find anything very strange but the problem is still here even after several updates.

I've downgraded the kernel to the version 4.8.16-300.fc25.x86_64 and here everything works fine. I don't have the time now to try every version from 4.8.16-300 to the 4.11.6-201 to see where started the problem. But it is clearly a kernel issue.

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Hi, I have still this problem even after the update to Fedora 27.
Is there any news about it? 
I would like to remark the fact that with older kernel everything works pretty good. Only with new ones it has problem with full-speed fans after resume from stand-by.

Thank you.

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  As kernel maintainers, we try to keep up with bugzilla but due the rate at which the upstream kernel project moves, bugs may be fixed without any indication to us. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs.
 
Fedora 27 has now been rebased to 4.15.3-300.f27.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you experience different issues, please open a new bug report for those.

Thank you very much Laura. I updated the kernel and everything now works fine!
I think this bug can be closed now..?

Thank you for letting us know.

Hi, I need to reopen this bug because it reappeared.

Everything was fine until 4.16.12-200.fc27 kernel version.
From the version 4.16.13-200.fc27 the problem started again.

I tried to wait some new version but the problem is still present.

I know that Fedora 28 is out but I don't have time now to update it and I think it should work anyway even if I don't update, am I right? Or the support is ended and if I want some results I will need to update? 

Thank you in advance for your help.

I would let you know that the but is still here even after system upgrade, with kernel version 4.17.3-200.fc28.x86_64

Hi, this problem is becoming really annoying. It seems impossible for me to change the priority from medium to high, but for a short period of time in which I didn't need to move a lot around with my laptop it was not a big issue, but now I have to choose to keep an old version of the kernel or to keep the most recent one but without the possibility to use the standby function, and this is not very good.. even because the last working version is becoming old. And what is even stranger is that the problem was solved and then it reappeared.

Any chance to solve it soon? Thank you.

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.
 
Fedora 28 has now been rebased to 4.18.10-300.fc28.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29.
 
If you experience different issues, please open a new bug report for those.

Hi, I have Fedora 28 and I've received the update to kernel 4.18.10-200.fc28 (and not 300), in which the bug is still present. I can't find online the version you've mentioned. I can find it only for fc29.

And I didn't understand what you said about Fedora 29. Should I update to Fedora 29 or not? And if yes, should I do it even if it has not been released officially yet, or wait for the official release at the end of the month?

Thanks.

Hi, the problem is still here even after the upgrade to Fedora 29. Now I have kernel 4.18.16-300.fc29.x86_64, I've changed the version on the bug information above.

Hi, the problem is still here. I've find out that this bug: Bug 1512275 is the same as mine. Should I close mine and keep only one open?
Are there some news about the fix of this problem?

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs.
 
Fedora 29 has now been rebased to 4.19.5-300.fc29.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you experience different issues, please open a new bug report for those.

Hi, the problem is still here even after the update to kernel 4.19.5-300.fc29

Hi, I'm currently on kernel 4.19.13-300.fc29.x86_64, I'm keeping it updated to check if the problem is solved.
Right now the problem is still here and it's becoming really uncomfortable to have a laptop without the possibility to use the standby feature to move it around without closing everything I'm working on.

I've tested some workarounds I've found online, in particular:
 - some in which was suggested to reset value in "/sys/devices/virtual/thermal/cooling_deviceX/cur_state" files.
 - some fan speed control programs like in particular thinkfan (but also fancontrol from lm-sensors)

But sadly nothing worked. Insted I've discovered that checking the speed of the fan from "/proc/acpi/ibm/fan" file always return a speed of 0rpm.

In addition I've tested kernel-vanilla-fedora repo and also kernel-vanilla-stable repo, I don't know if it can be useful to you but none of those kernel works properly:
 - 4.19.13-350.vanilla.knurd.1.fc29.x86_64 (from vanulla-fedora)
 - 4.20.0-1.vanilla.knurd.1.fc29.x86_64 (from vanilla-stable)
both of them have the same issue with fans at max speed after standby.

If at least a workaround have existed it would be awesome, but I didn't manage to find any until now (besides keeping an outdated kernel).

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs.

Fedora 29 has now been rebased to 4.20.5-200.fc29.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Hi, I've just tested the kernel 4.20.5-200.fc29 but the same problem is still here.

Hi, I've just find out an interesting thing that maybe can be useful:

If I disable dedicated graphics card from BIOS (Config > Display > Graphics Device, and select "Integrated Graphics" instead of "NVIDIA Optimus"), the problem about fans at full speed after standby disappear. Everything works well, but of course system doesn't recognize my NVIDIA graphics card and I can't use it. Since I don't use it a lot, this workaround is good for me, but it can't be a permanent solution.

Let me know if there's something else I can do to help you understand the problem.

Another interesting fact (but maybe is not related with this bug) is that if I keep enabled the NVIDIA graphics and I enable secure-boot, then I'm no longer able to use it from gnome with the menu option "launch using dedicated graphics card", because the option disappear. This should be related with the service switcheroo-control that crash only when secure-boot is enabled. By the way I've performed some tests and secure-boot is not related with my problem for which I opened this bug, so maybe this information is useless.

Moreover, I use nouveau drivers, I never installed proprietary drivers.

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs.

Fedora 30 has now been rebased to 5.2.9-200.fc30.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31.

If you experience different issues, please open a new bug report for those.

Hi, I've just tested the kernel 5.2.9-200.fc30 but the same problem is still here.

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs.

Fedora 30 has now been rebased to 5.5.7-100.fc30.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31.

If you experience different issues, please open a new bug report for those.

Hi, I've just tested the kernel 5.5.7-200.fc31.x86_64 (I already have Fedora 31), and finally everything works fine!!!

Thank you for the support.

Thanks for the update