Yet another arch system not shutting down (it's the Network Manager)

\hbar · 2015-10-09 12:08:26

Why not try to isolate the issue: disable as much as you can (GUI, network manager, power management daemon, ...) and try to shutdown, then enable the services one by one to figure out what's stopping the shutdown process. Alternatively, you could install a fresh minimal system (maybe on a USB stick), with no more than what is needed to boot, and do the same. By the way, can you shut down the live ISO?

fakemoth · 2015-10-16 06:10:30

I already did most of what you are recommending, no sddm/x/gui, power management (here maybe you have some advice as I am not sure what to do?), no network, no catalyst, killed all the processes ever recommended - still have no idea. I will also try with a live ISO.

Last edited by fakemoth (2015-11-07 05:43:40)

ukhippo · 2015-10-16 19:43:21

Does your system load the mei_me kernel module? If so, try blacklisting that module. That module caused ACPI problems for me, and since I don't use Intel AMT there was no need to load it.

Another suggestion is to compare what kernel modules are loaded by Arch and the distribution that does work. Any differences would give you a list of modules to investigate to see whether they can be loaded or blacklisted.

fakemoth · 2015-10-18 16:36:40

No such module loaded

[root@PC modprobe.d]# lsmod
Module                  Size  Used by
cfg80211              475136  0
ipt_REJECT             16384  3
nf_reject_ipv4         16384  1 ipt_REJECT
xt_tcpudp              16384  3
nf_conntrack_ipv4      20480  5
nf_defrag_ipv4         16384  1 nf_conntrack_ipv4
xt_conntrack           16384  5
nf_conntrack           90112  2 xt_conntrack,nf_conntrack_ipv4
iptable_filter         16384  1
eeepc_wmi              16384  0
asus_wmi               24576  1 eeepc_wmi
sparse_keymap          16384  1 asus_wmi
led_class              16384  1 asus_wmi
rfkill                 24576  4 cfg80211,asus_wmi
mxm_wmi                16384  0
x86_pkg_temp_thermal    16384  0
coretemp               16384  0
sch_fq_codel           20480  2
raid1                  36864  1
snd_hda_codec_hdmi     53248  2
kvm_intel             155648  0
amdkfd                 77824  1
kvm                   438272  1 kvm_intel
radeon               1581056  0
crct10dif_pclmul       16384  0
snd_hda_intel          28672  4
nfs                   204800  0
crc32_pclmul           16384  0
snd_hda_controller     28672  1 snd_hda_intel
crc32c_intel           24576  0
snd_hda_codec          98304  3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_controller
ghash_clmulni_intel    16384  0
lockd                  90112  1 nfs
snd_hda_core           24576  3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_controller
grace                  16384  1 lockd
aesni_intel           172032  0
sunrpc                274432  2 nfs,lockd
snd_hwdep              16384  1 snd_hda_codec
e1000e                221184  0
snd_pcm                90112  4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
aes_x86_64             20480  1 aesni_intel
fscache                53248  1 nfs
snd_timer              28672  1 snd_pcm
lrw                    16384  1 aesni_intel
ttm                    81920  1 radeon
md_mod                126976  2 raid1
gf128mul               16384  1 lrw
glue_helper            16384  1 aesni_intel
snd                    69632  14 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel
ablk_helper            16384  1 aesni_intel
drm_kms_helper        106496  1 radeon
soundcore              16384  1 snd
joydev                 20480  0
cryptd                 20480  3 ghash_clmulni_intel,aesni_intel,ablk_helper
psmouse               122880  0
mousedev               20480  0
ptp                    20480  1 e1000e
pcspkr                 16384  0
serio_raw              16384  0
pps_core               20480  1 ptp
drm                   282624  3 ttm,drm_kms_helper,radeon
i2c_i801               20480  0
i2c_algo_bit           16384  1 radeon
shpchp                 36864  0
tpm_tis                20480  0
fan                    16384  0
thermal                20480  0
tpm                    32768  1 tpm_tis
wmi                    20480  2 mxm_wmi,asus_wmi
battery                20480  0
fglrx               13303808  184
video                  24576  1 asus_wmi
i2c_hid                20480  0
acpi_cpufreq           20480  0
acpi_pad               16384  0
processor              28672  9 acpi_cpufreq
evdev                  20480  31
mac_hid                16384  0
button                 16384  1 fglrx
amd_iommu_v2           20480  2 fglrx,amdkfd
ip_tables              28672  1 iptable_filter
x_tables               28672  5 ip_tables,xt_tcpudp,xt_conntrack,iptable_filter,ipt_REJECT
ext4                  512000  2
crc16                  16384  1 ext4
mbcache                20480  1 ext4
jbd2                   90112  1 ext4
hid_roccat_isku        16384  0
hid_roccat_koneplus    16384  0
hid_roccat             16384  2 hid_roccat_isku,hid_roccat_koneplus
hid_roccat_common      16384  2 hid_roccat_isku,hid_roccat_koneplus
sr_mod                 24576  0
sd_mod                 36864  9
cdrom                  53248  1 sr_mod
hid_generic            16384  0
usbhid                 49152  1
hid                   110592  5 i2c_hid,hid_generic,hid_roccat_isku,hid_roccat_koneplus,usbhid
atkbd                  24576  0
libps2                 16384  2 atkbd,psmouse
ahci                   36864  5
libahci                28672  1 ahci
xhci_pci               16384  0
libata                204800  2 ahci,libahci
xhci_hcd              155648  1 xhci_pci
usbcore               200704  5 hid_roccat_common,usbhid,xhci_hcd,xhci_pci
scsi_mod              147456  3 libata,sd_mod,sr_mod
usb_common             16384  1 usbcore
i8042                  20480  1 libps2
serio                  20480  6 serio_raw,atkbd,i8042,psmouse

einhard · 2015-10-18 20:51:39

I think it may be related to systemd long known bug https://github.com/systemd/systemd/issues/867 . I have similar issue (more unpredictable, sometimes it shutdowns properly sometimes not) from systemd 222 and it's still going in 227.

What you want to try is setting

Storage=none

or

Storage=volatile

in /etc/systemd/journald.conf

with default Storage option my system also never shuts down. Same as you I didn't encounter this problem with Fedora and Debian, it may be totally exclusive to Arch. Other distributions probably patch their systemd or their filesystem arrangement differs, especially /var

Last edited by einhard (2015-10-18 20:56:34)

fakemoth · 2015-10-22 06:39:56

Forgot to post, this is not helping. I did some tests. Besides I don't have that error in the logs. But thank you anyway for your interest! I will be moving again back to openSUSE, when they will launch Leap, as this seems unsolvable and... well my system must be perfectly functional. I have quite a few more problems see here https://bbs.archlinux.org/viewtopic.php … 2#p1570962 but I suspect this is just Plasma 5.

But I will report back. Thanks once again.

fakemoth · 2015-11-07 05:12:11

I figured why it is happening! It's the damn Network Manager, incredible! I switched to openSUSE, they launched Leap (42.1) this week, and no problems there. All fine, but I noticed in Leap I don't have an icon for the networks connections. Going through Yast I see in the networks section that the method selected is "Wicked" (really have no idea what is it, I will start to read about it). So I switched to Network Manager to easily manage my networks. Lucky me, it was late, didn't do anything else at that time with the system so it was quite easy to connect the dots; when trying to shutdown - guess what? The system doesn't stop, with exactly the same sounds and steps... I tested it and it's the Network Manager, both in openSUSE and Arch.

So the only thing we can do is to disable Network Manager. Maaaan, hated that shit for years, and when I start to love it... Is there any chance we can fix this, where should this be reported, and how can I get more info?

fakemoth · 2015-11-14 17:01:38

Anyone else with the same problem? Is this not interesting, an isolated case, not a bug or what?

Last edited by fakemoth (2015-11-14 17:05:37)

hayer44 · 2015-11-15 09:37:15

fakemoth wrote:

Anyone else with the same problem? Is this not interesting, an isolated case, not a bug or what?

I have the same problem. I tried to substitute NM with wicd, but it had resulted in no gains at all. I also tried to switch to stable kernel, to disable laptop mode tools and it has gave me nothing. I regularly try to find a solution or just to sharply define the problem and I still don't understand anything.

ukhippo · 2015-11-15 13:33:56

fakemoth wrote:

Anyone else with the same problem? Is this not interesting, an isolated case, not a bug or what?

I don't use Network Manager, so can't help you there. Maybe if you change the thread title to more accurately reflect the problem (Network Manager preventing shutdown), people who know about NM may read this thread.

hayer44 wrote:

I have the same problem. I tried to substitute NM with wicd, but it had resulted in no gains at all.

It seems you have a different cause, as fakemoth's is with NM. I suggest you open your own “system won't shutdown” thread where you can detail info about your system/post relevant logs/list what you've tried etc. Link to this thread, and point out the solution doesn't work for you.

fakemoth · 2015-11-15 15:19:42

@hayer44 Sorry to hear this is a more of a problem I would have thought. But please note that wicd is not the same animal with wicked, I guess? Also I am on the LTS kernel for a long time and had quite a few updates, nothing helped.
@ukhippo Changed the subject to reflect the NM issue.

Last edited by fakemoth (2015-11-15 15:22:26)

der_joachim · 2015-11-15 19:42:33

fakemoth wrote:

Anyone else with the same problem? Is this not interesting, an isolated case, not a bug or what?

I occasionally have the same problem as fakemoth. The easiest way to reproduce it, is to botch an NFS operation, like cancelling rsync. If my action succeeds, I can shutdown just fine, otherwise, I am gently caressed sideways with a chainsaw.

That being said, I just updated journald.conf as per the Github issue linked above. This may be helpful in my case, since my logs are mounted in memory. If not, I'll just experiment with shutting down NM manually first.

BTW: I am not trying to hijack this thread (which has already been helpful to me, thanks). I am just assuring fakemoth that he's not the only one.

hayer44 · 2015-11-16 18:56:06

ukhippo wrote:

fakemoth wrote:
Anyone else with the same problem? Is this not interesting, an isolated case, not a bug or what?
I don't use Network Manager, so can't help you there. Maybe if you change the thread title to more accurately reflect the problem (Network Manager preventing shutdown), people who know about NM may read this thread.
hayer44 wrote:
I have the same problem. I tried to substitute NM with wicd, but it had resulted in no gains at all.
It seems you have a different cause, as fakemoth's is with NM. I suggest you open your own “system won't shutdown” thread where you can detail info about your system/post relevant logs/list what you've tried etc. Link to this thread, and point out the solution doesn't work for you.

My thread: https://bbs.archlinux.org/viewtopic.php … 1#p1579091
I have problem that is similar to fakemoth's

\hbar · 2015-11-19 06:11:16

Have you tried to stop the network manager service by hand without shutting down? What does the log say when you do that?

fakemoth · 2015-11-28 07:23:57

Just wanted to be clear - this is not working. I did stop the network, first thing I tried to no avail - the logs are silent in this regard, it seems it has nothing to do with it; but it does as my experiments suggest. Here is my network card for further investigation:

FakeMoth-PC:/home/fakemoth # lspci
00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 07)
00:01.1 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x8) (rev 07)
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
00:17.0 SATA controller: Intel Corporation Device a102 (rev 31)
00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev f1)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii HDMI Audio
02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290]
02:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii HDMI Audio
04:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller

BTW: is this forum still apropiate now that the cause has been identified as somehow network related? Feel free to move it to the Network stuff if you think it is not.

Last edited by fakemoth (2015-11-28 07:30:12)

fakemoth · 2016-06-10 05:20:24

Just an update, problem is SOLVED. In an effort to make it work I updated on openSUSE:
-the kernel to 4.6;
-xorg - other reasons;
-dropped Catalyst and I am using Gallium - other reasons.
It was doing the same thing on both openSUSE and Arch as stated. After the update to kernel 4.6 I can properly shutdown the station, all hail Zalmoxis So it was the kernel in the end and not systemd.

fakemoth@FakeMoth-PC:~> uname -a 
Linux FakeMoth-PC 4.6.0-4.g779b2fc-default #1 SMP PREEMPT Fri May 27 20:15:14 UTC 2016 (779b2fc) x86_64 x86_64 x86_64 GNU/Linux
fakemoth@FakeMoth-PC:~> zypper lr
#  | Alias                               | Name                                    | Enabled | GPG Check | Refresh
---+-------------------------------------+-----------------------------------------+---------+-----------+--------
 1 | download.opensuse.org-non-oss       | Main Repository (NON-OSS)               | Yes     | (r ) Yes  | Yes     
 2 | [url=ftp://ftp.gwdg.de]ftp.gwdg.de[/url]-suse                    | Packman Repository                      | Yes     | (r ) Yes  | Yes     
 3 | geeko.ioda.net-amd-fglrx            | AMD/ATI Graphics Drivers                | Yes     | (r ) Yes  | Yes     
 4 | http-download.opensuse.org-44d0b71f | X11:XOrg                                | Yes     | (r ) Yes  | Yes     
 5 | http-download.opensuse.org-49e9bece | X11:XOrg                                | Yes     | (r ) Yes  | Yes     
 6 | http-download.opensuse.org-758c3606 | home:mhnovell                           | Yes     | (r ) Yes  | Yes     
 7 | http-download.opensuse.org-8986ce35 | games:tools                             | Yes     | (r ) Yes  | Yes     
 8 | http-download.opensuse.org-95e969c9 | home:mhnovell                           | Yes     | (r ) Yes  | Yes     
 9 | http-download.opensuse.org-c7d96e69 | home:pontostroy:X11                     | Yes     | (r ) Yes  | Yes     
10 | linuxdownload.adobe.com-linux       | Adobe Flash Plugin                      | Yes     | ( p) Yes  | Yes     
11 | new-kernel-repo                     | new-kernel-repo                         | Yes     | (r ) Yes  | Yes     
12 | packman.inode.at-suse               | Packman Repository                      | Yes     | (r ) Yes  | Yes     
13 | repo-debug                          | openSUSE-Leap-42.1-Debug                | No      | ----      | Yes     
14 | repo-debug-non-oss                  | openSUSE-Leap-42.1-Debug-Non-Oss        | No      | ----      | Yes     
15 | repo-debug-update                   | openSUSE-Leap-42.1-Update-Debug         | No      | ----      | Yes     
16 | repo-debug-update-non-oss           | openSUSE-Leap-42.1-Update-Debug-Non-Oss | No      | ----      | Yes     
17 | repo-non-oss                        | openSUSE-Leap-42.1-Non-Oss              | Yes     | (r ) Yes  | Yes     
18 | repo-oss                            | openSUSE-Leap-42.1-Oss                  | Yes     | (r ) Yes  | Yes     
19 | repo-source                         | openSUSE-Leap-42.1-Source               | No      | ----      | Yes     
20 | repo-update                         | openSUSE-Leap-42.1-Update               | Yes     | (r ) Yes  | Yes     
21 | repo-update-non-oss                 | openSUSE-Leap-42.1-Update-Non-Oss       | Yes     | (r ) Yes  | Yes

Arch Linux

#26 2015-10-09 12:08:26

Re: Yet another arch system not shutting down (it's the Network Manager)

#27 2015-10-16 06:10:30

Re: Yet another arch system not shutting down (it's the Network Manager)

#28 2015-10-16 19:43:21

Re: Yet another arch system not shutting down (it's the Network Manager)

#29 2015-10-18 16:36:40

Re: Yet another arch system not shutting down (it's the Network Manager)

#30 2015-10-18 20:51:39

Re: Yet another arch system not shutting down (it's the Network Manager)

#31 2015-10-22 06:39:56

Re: Yet another arch system not shutting down (it's the Network Manager)

#32 2015-11-07 05:12:11

Re: Yet another arch system not shutting down (it's the Network Manager)

#33 2015-11-14 17:01:38

Re: Yet another arch system not shutting down (it's the Network Manager)

#34 2015-11-15 09:37:15

Re: Yet another arch system not shutting down (it's the Network Manager)

#35 2015-11-15 13:33:56

Re: Yet another arch system not shutting down (it's the Network Manager)

#36 2015-11-15 15:19:42

Re: Yet another arch system not shutting down (it's the Network Manager)

#37 2015-11-15 19:42:33

Re: Yet another arch system not shutting down (it's the Network Manager)

#38 2015-11-16 18:56:06

Re: Yet another arch system not shutting down (it's the Network Manager)

#39 2015-11-19 06:11:16

Re: Yet another arch system not shutting down (it's the Network Manager)

#40 2015-11-28 07:23:57

Re: Yet another arch system not shutting down (it's the Network Manager)

#41 2016-06-10 05:20:24

Re: Yet another arch system not shutting down (it's the Network Manager)

Board footer