Created attachment 1377395 [details] Logs from shutdown sequence (journalctl -b -1 -n250) Description of problem: Just installed and updated Fedora 27 on XPS 15 9550. Shutdown of the system takes around 3 minutes, every time I try. Version-Release number of selected component (if applicable): [pawel@localhost]$ /usr/lib/systemd/systemd --version systemd 234 +PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN default-hierarchy=hybrid How reproducible: Just shutdown the system. Steps to Reproduce: 1. Shutdown the system using Gnome UI or shutdown now Actual results: Fedora shutdown logo shows for ~3minutes Expected results: System shutdown in seconds. Additional info: Attached logs from shudown prodecure.
From the logs it looks like firewalld is attempting to unload kernel modules, but the command is hanging. This could be due to a kernel bug. Can you provide the kernel version (uname -a)?
*** Bug 1546445 has been marked as a duplicate of this bug. ***
pawel@localhost:~$ uname -a Linux localhost.localdomain 4.15.3-300.fc27.x86_64 #1 SMP Tue Feb 13 17:02:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Can verify on Fedora 29 on a Dell XPS 15 9550. This is really annoying. When can I expect a fix? This bug has existed at least since Fedora 26/27 (just do a Google search). I had the same issue on 28, which I was hoping 29 would resolve.
(In reply to Evan Washkow from comment #4) > Can verify on Fedora 29 on a Dell XPS 15 9550. This is really annoying. When > can I expect a fix? firewalld unloads modules when it is stopped. Your laptop has the BCM43602 wireless chip, which seems to cause hangs when the nf_conntrack module is unloaded. You can make firewalld avoid unloading modules (and flushing rules) by setting CleanupOnExit=no in /etc/firewalld/firewalld.conf to avoid the issue, but this is not recommended as it will leave rules laying around if you intentionally stop firewalld. I'm reassigning this bug to the kernel, because it appears to be a module/driver issue as per bug 1294415.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.