Created attachment 1602561 [details]
Result of running journalctl -b -1 > previous_boot.txt
1. Please describe the problem:
The system doesn't always finish shutting down or rebooting. It just hangs. I have to force it using the power button
2. What is the Version-Release number of the kernel:
3. Did it work previously in Fedora? If so, what kernel version did the issue
*first* appear? Old kernels are available for download at
It works fine with the 5.1 series. The latest I have on my machines and which I decided to pin is "kernel-5.1.20-300.fc30.x86_64". The problem started with the 5.2 kernels. I have these installed:
4. Can you reproduce this issue? If so, please provide the steps to reproduce
the issue below:
If I start the system and then reboot it, it seems it does it just fine. After using it for many hours, something seems to happen and it always triggers after many hours (for example, when I shutdown the system before going to sleep)
5. Does this problem occur with the latest Rawhide kernel? To install the
Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
``sudo dnf update --enablerepo=rawhide kernel``:
I don't know.
6. Are you running any modules that not shipped with directly Fedora's kernel?:
Yes. The nvidia driver, version 430.40
7. Please attach the kernel logs. You can get the complete kernel log
for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
issue occurred on a previous boot, use the journalctl ``-b`` flag.
Created attachment 1602562 [details]
result of running journalctl --no-hostname -k > dmesg.txt
Same issue here.
GPU Intel UHD Graphics 630
Created attachment 1602627 [details]
basic system info output from inxi
Created attachment 1602933 [details]
Result of running journalctl -b -1 with kernel 5.2.7
Last night it did the same thing. I decided to wait more (like more than 3 minutes) and eventually I heard the mechanical drive in my system shutdown. However, the screen was still on and so were the fans.
Problem still happens with 5.2.7-200.fc30.x86_64
Same problem here.
I also have a Gigabyte mobo (also a Z390) but upgrading bios to F8 seems to have solved the problem.
(In reply to Norman Davidson from comment #5)
> Same problem here.
> I also have a Gigabyte mobo (also a Z390) but upgrading bios to F8 seems to
> have solved the problem.
Interesting. The only change they list on their page is microcode updates which usually get picked up by distros anyway, regardless of mobo manufacturers.
Do you also boot using UEFI mode?
Hmm... not looking forward to re-doing my fan curves :/
(In reply to Silviu C. from comment #6)
> (In reply to Norman Davidson from comment #5)
> > Same problem here.
> > I also have a Gigabyte mobo (also a Z390) but upgrading bios to F8 seems to
> > have solved the problem.
> Interesting. The only change they list on their page is microcode updates
> which usually get picked up by distros anyway, regardless of mobo
> Do you also boot using UEFI mode?
> Hmm... not looking forward to re-doing my fan curves :/
Yes, I do boot using UEFI and yes on the microcode point. But, so far, so good!
There's a discussion going on here with similar issues: https://devtalk.nvidia.com/default/topic/1057524/linux/system-seems-locked-while-rebooting-with-linux-5-2-1-and-nvidia-drivers-430-34-or-430-26/1
No conclusion has been drawn yet
(In reply to Silviu C. from comment #8)
> There's a discussion going on here with similar issues:
> No conclusion has been drawn yet
Thanks for that.
I forgot to mention that my gpu is actually an AMD.
My mobo is HD3P/Z370 latest bios F12.
Problem still happens with 5.2.8-200.fc30.x86_64.
Created attachment 1604296 [details]
Photos of tty output during shutdown
I logged off, switched to tty2, logged in and then issues a ''sudo shutdown - h now" command.
As Norman Davidson suggested, a BIOS update fixed the problem for me as well. I wonder whether the actual BIOS had anything new or if simply loading the default settings "Load optimized defaults" did something to fix whatever got b0rked.
Same issue on 5.4.8
FYI, I had the same issue with all 5.4 Fedora kernel series. Lately, my motherboard provider (Asus) launch a new BIOS version, updating Intel ME, microcode, and mitigations stuff. Reboot and voilá, problem solved.
*********** 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.
Same issue here.
Board: ASUSTeK H170M-PLUS
BIOS-firmware: 3805 (newest)
GPU-drivers: asus_wmi, i915, nouveau
As described by the reporter, the problem only arises after the system has been up for a longer time.
Please update the version of the bug report to "Fedora 31"!
Created attachment 1668983 [details]
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
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 '30'.
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 30 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 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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
Thank you for reporting this bug and we are sorry it could not be fixed.