You are not logged in.

#1 2015-10-01 14:48:53

fakemoth
Member
From: Transylvania
Registered: 2015-09-23
Posts: 23

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

Hello - this is my first Arch install so bear with me. Google doesn't help, and the topics found here in the forums don't seem to solve anything, at least in my case.

I have a few problems this being the one that I hate more. The system doesn't shutdown. I tried quite a few kernels (well... 3) and had on update for systemd, the behavior is the same. I don't know how to diagnose this as it happens after everything is in fact stopped, except that the system is not and the fans are blowing like crazy - have to push the power button for seconds to stop it. Never had such a problem (using openSUSE, Fedora, CentOS). Seems pretty common for Arch though.

So:

[root@PC fakemoth]# journalctl -p err -b
-- Logs begin at Lu 2015-09-21 15:27:48 EEST, end at Jo 2015-10-01 17:27:12 EEST. --
oct 01 17:11:09 PC kernel: kvm: disabled by bios
oct 01 17:11:09 PC systemd[339]: mdmonitor.service: Failed at step EXEC spawning /usr/lib/systemd/scripts/mdadm_env.sh: No suc
oct 01 17:11:10 PC kernel: vgaarb: this pci device is not a vga device
oct 01 17:11:10 PC kernel: vgaarb: this pci device is not a vga device
oct 01 17:11:10 PC kernel: vgaarb: this pci device is not a vga device
oct 01 17:11:10 PC kernel: vgaarb: this pci device is not a vga device
oct 01 17:11:10 PC kernel: vgaarb: this pci device is not a vga device
oct 01 17:11:10 PC kernel: vgaarb: this pci device is not a vga device
oct 01 17:11:10 PC kernel: vgaarb: this pci device is not a vga device
oct 01 17:11:10 PC kernel: vgaarb: this pci device is not a vga device
oct 01 17:11:10 PC kernel: vgaarb: this pci device is not a vga device
oct 01 17:11:10 PC kernel: vgaarb: this pci device is not a vga device
oct 01 17:11:10 PC kernel: vgaarb: this pci device is not a vga device
oct 01 17:11:10 PC kernel: vgaarb: this pci device is not a vga device
oct 01 17:11:10 PC kernel: vgaarb: this pci device is not a vga device
oct 01 17:11:10 PC kernel: vgaarb: this pci device is not a vga device
oct 01 17:11:10 PC kernel: vgaarb: this pci device is not a vga device
oct 01 17:11:10 PC kernel: vgaarb: this pci device is not a vga device
[root@PC fakemoth]# dmesg | grep -iE 'warn|fail|taint|disa'     
[    0.000000] NX (Execute Disable) protection: active
[    0.000000]   6 disabled
[    0.000000]   7 disabled
[    0.000000]   8 disabled
[    0.000000]   9 disabled
[    0.000000] ACPI: Early table checksum verification disabled
[    0.000000] tsc: Fast TSC calibration failed
[    0.016184] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150410/dswload-210)
[    0.289811] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[    0.347292] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
[    0.347913] pci 0000:00:01.0: System wakeup disabled by ACPI
[    0.348014] pci 0000:00:01.1: System wakeup disabled by ACPI
[    0.348226] pci 0000:00:14.0: System wakeup disabled by ACPI
[    0.348661] pci 0000:00:1b.0: System wakeup disabled by ACPI
[    0.348801] pci 0000:00:1c.0: System wakeup disabled by ACPI
[    0.348943] pci 0000:00:1d.0: System wakeup disabled by ACPI
[    0.349671] pci 0000:00:1f.6: System wakeup disabled by ACPI
[    0.349776] pci 0000:01:00.0: System wakeup disabled by ACPI
[    0.369732] pci 0000:02:00.0: System wakeup disabled by ACPI
[    0.389836] pci 0000:04:00.0: System wakeup disabled by ACPI
[    0.444030] pnp 00:01: [dma 0 disabled]
[    0.458723] pci 0000:04:00.0: xHCI BIOS handoff failed (BIOS bug ?) 00010401
[    0.525596] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    0.591180] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS01._PLD] (Node ffff880455907d48), AE_AML_NO_OPERAND (20150410/psparse-536)
[    0.591559] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS02._PLD] (Node ffff880455907d98), AE_AML_NO_OPERAND (20150410/psparse-536)
[    0.591934] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS03._PLD] (Node ffff880455907de8), AE_AML_NO_OPERAND (20150410/psparse-536)
[    0.592309] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS04._PLD] (Node ffff880455907e38), AE_AML_NO_OPERAND (20150410/psparse-536)
[    0.592685] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS05._PLD] (Node ffff880455907e88), AE_AML_NO_OPERAND (20150410/psparse-536)
[    0.593060] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS06._PLD] (Node ffff880455907ed8), AE_AML_NO_OPERAND (20150410/psparse-536)
[    0.593434] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS07._PLD] (Node ffff880455907f28), AE_AML_NO_OPERAND (20150410/psparse-536)
[    0.593807] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS08._PLD] (Node ffff880455907f78), AE_AML_NO_OPERAND (20150410/psparse-536)
[    0.594182] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS09._PLD] (Node ffff880455907fc8), AE_AML_NO_OPERAND (20150410/psparse-536)
[    0.594554] ACPI Error: Method parse/execution failed [\_SB_.PCI0.XHC_.RHUB.HS10._PLD] (Node ffff880455909028), AE_AML_NO_OPERAND (20150410/psparse-536)
[    0.661114] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.675521] ACPI Warning: SystemIO range 0x000000000000F000-0x000000000000F01F conflicts with OpRegion 0x000000000000F000-0x000000000000F00F (\_SB_.PCI0.SBUS.SMBI) (20150410/utaddress-254)
[    1.792974] kvm: disabled by bios
[    1.929955] asus_wmi: Disabling ACPI video driver
[    4.345621] <6>[fglrx] IRQ 135 Disabled
[    6.122257] <6>[fglrx] IRQ 136 Disabled

Weird, now I don't know why it says in has no history of the boots; had some - but there were no obvious problems

[root@PC fakemoth]# journalctl --list-boots
Failed to determine boots: No data available
[root@PC fakemoth]# journalctl -b -1
...skipping...
oct 01 16:43:00 PC systemd[1]: Stopping Load/Save Random Seed...
oct 01 16:43:00 PC systemd[1]: Stopped target Swap.
oct 01 16:43:00 PC systemd[1]: Stopped target Encrypted Volumes.
oct 01 16:43:00 PC systemd[1]: Stopped Setup Virtual Console.
oct 01 16:43:00 PC systemd[1]: Stopped Apply Kernel Variables.
oct 01 16:43:00 PC systemd[1]: Stopped Load Kernel Modules.
oct 01 16:43:00 PC systemd[1]: Stopping Update UTMP about System Boot/Shutdown...
oct 01 16:43:00 PC systemd[1]: Stopped target Paths.
oct 01 16:43:00 PC systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
oct 01 16:43:00 PC systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
oct 01 16:43:00 PC systemd[1]: Stopped Load/Save Random Seed.
oct 01 16:43:00 PC systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
oct 01 16:43:00 PC systemd[1]: Stopped Create Volatile Files and Directories.
oct 01 16:43:00 PC systemd[1]: Stopped target Local File Systems.
oct 01 16:43:00 PC systemd[1]: Unmounting Temporary Directory...
oct 01 16:43:00 PC systemd[1]: Unmounting /run/user/997...
oct 01 16:43:00 PC systemd[1]: Unmounting /home/fakemoth/Structure...
oct 01 16:43:00 PC systemd[1]: Unmounted Temporary Directory.
oct 01 16:43:00 PC systemd[1]: Unmounted /run/user/997.
oct 01 16:43:00 PC systemd[1]: Unmounted /home/fakemoth/Structure.
oct 01 16:43:00 PC systemd[1]: Reached target Unmount All Filesystems.
oct 01 16:43:00 PC systemd[1]: Stopped target Local File Systems (Pre).
oct 01 16:43:00 PC systemd[1]: Stopped Create Static Device Nodes in /dev.
oct 01 16:43:00 PC systemd[1]: Stopped Remount Root and Kernel File Systems.
oct 01 16:43:00 PC systemd[1]: Reached target Shutdown.
oct 01 16:43:00 PC systemd[1]: Reached target Final Step.
oct 01 16:43:00 PC systemd[1]: Starting Reboot...
oct 01 16:43:00 PC systemd[1]: Shutting down.
oct 01 16:43:00 PC systemd-shutdown[1]: Sending SIGTERM to remaining processes...
oct 01 16:43:00 PC systemd-journal[189]: Journal stopped

Issuing the following commands don't make any difference also:
sync && reboot -f
sync && poweroff -f

So how can I figure what is happening? Any ideeas?

BTW, my machine is a I7 Skylake 6700K; Asus Z170 Pro Gaming; Intel 730 SSD 480GB/s + a RAID 1 array 2x1,5TB ST; 2xSapphire R9 290 CSF, 16GB DDR4, 1000W power source. Quite new, but it doesn't do anything weird in openSUSE 13.1 with kernels 3.11 or 4.2, it shuts down as expected. I am also on the latest Asus BIOS 0802, and the latest firmware for the Intel SSD.

[fakemoth@PC ~]$ screenfetch
[[ ! ]] Qt: Session management error: networkIdsList argument is NULL
                   -`
                  .o+`                 fakemoth@PC
                 `ooo/                 OS: Arch Linux 
                `+oooo:                Kernel: x86_64 Linux 4.1.8-1-lts
               `+oooooo:               Uptime: 36m
               -+oooooo+:              Packages: 962
             `/:-:++oooo+:             Shell: bash 4.3.42
            `/++++/+++++++:            Resolution: 1920x1080
           `/++++++++++++++:           DE: KDE5
          `/+++ooooooooooooo/`         WM: KWin
         ./ooosssso++osssssso+`        GTK Theme: Orion [GTK2/3]
        .oossssso-````/ossssss+`       Icon Theme: breeze
       -osssssso.      :ssssssso.      Font: Oxygen-Sans Sans-Book
      :osssssss/        osssso+++.     CPU: Intel Core i7-6700K CPU @ 4.001GHz
     /ossssssss/        +ssssooo/-     GPU: AMD Radeon R9 200 Series
   `/ossssso+/:-        -:/+osssso+-   RAM: 2419MiB / 15981MiB
  `+sso+:-`                 `.-/+oso: 
 `++:.                           `-/+/
 .`                                 `/

THANKS!

Last edited by fakemoth (2015-11-15 15:13:43)


Don't take the name of root in vain.

Offline

#2 2015-10-04 05:15:46

fakemoth
Member
From: Transylvania
Registered: 2015-09-23
Posts: 23

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

So can anyone shed some light, what could be wrong? I take it that no one else has this problem, just me?


Don't take the name of root in vain.

Offline

#3 2015-10-04 08:56:21

berbae
Member
From: France
Registered: 2007-02-12
Posts: 1,301

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

Do you have something like that in systemd journal when not being able to poweroff:

sept. 21 23:13:13 arch64 systemd[1]: session-c1.scope: Unit entered failed state.

Better to post the entire journal of a not shutting down session.

As dmesg is included in the systemd journal (the kernel entries), it's useless to separate the two.

Offline

#4 2015-10-04 11:37:15

c3kay
Member
From: New Zealand
Registered: 2015-04-19
Posts: 61

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

yes, post full journals.

my fedora server used to do it all the time. could never figure it out because shutdowns were rare, but it's usually put down to something hanging on reboot. rtorrent on my arch server causes a significant delay in shutdown, so from my perspective it was probably that running as a service that caused the problems. when fedup borked it in the transition from 20 to 21 i just took the opportunity and switched to arch instead of restoring. so it's not an arch issue from my perspective because none of my arch machines (x3) fail to shut down. it's a systemd issue and it'll surface on any system from time to time.

if you google for "fedora not shutting down" you'll find the same kinds of problems.

Offline

#5 2015-10-04 14:02:00

ukhippo
Member
From: Non-paged pool
Registered: 2014-02-21
Posts: 366

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

See also https://bbs.archlinux.org/viewtopic.php?id=203112
Maybe the kernel command line/systemd hook solution will work for you too.

Offline

#6 2015-10-05 09:50:56

fakemoth
Member
From: Transylvania
Registered: 2015-09-23
Posts: 23

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

Oh my thanks for answering! I didn't get the notifications, better check the SPAM folders. For me it happened from the start, always, without any exception - it is never shutting down. I even left it like half a day to see if it is a hanging service. But I don't think it is, see below:

[root@PC fakemoth]# systemctl --failed
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

@berbae: I don't see anything like this in the logs... Here is a full one http://pastebin.com/EUhs4ATq as it is my understanding we shouldn't post long code here.

@c3kay: do you see anything weird in the logs? I am also suspecting systemd, but why is it happening only to me sad and why not to Lennart Poettering lol ? At least he could figure something like this smile . Some more info http://pastebin.com/j8H1TrJe

@ukhippo: reading right now

Last edited by fakemoth (2015-10-05 09:54:06)


Don't take the name of root in vain.

Offline

#7 2015-10-05 16:11:25

frank604
Member
From: BC, Canada
Registered: 2011-04-20
Posts: 1,211

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

I do notice an important error message "the x11 connection broke did the x11 server die".  Never had this one but I'd look into it.  To isolate the issue, can you disable sddm and boot into console without starting X server and try a regular 'systemctl shutdown -h now' ?

My interpretation of this error and it's relationship to your issue may be off the mark but a quick test could be of benefit.

Offline

#8 2015-10-06 02:03:24

c3kay
Member
From: New Zealand
Registered: 2015-04-19
Posts: 61

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

^ sddm is crashing. nothing else in the logs isn't stopping when it said it should. i was expecting to see something not unmounting, or a custom service but sddm could be the problem.

i did some quick reading around the fedora problems and the dm, and it appears that for some people gdm was causing the problem and replacing it with lightdm solved their shutdown issue.

Offline

#9 2015-10-06 07:18:31

fakemoth
Member
From: Transylvania
Registered: 2015-09-23
Posts: 23

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

Frank604 & c3kay : Thanks for the ideeas, seen that but I dismissed it for some reason a while ago.

'systemctl shutdown -h now' doesn't work, the new systemd command I guess is 'systemctl poweroff now'. So I disabled sddm, rebooted and ran all the commands I could think of, as root,  to shutdown the machine - no difference, the computer doesn't shut down even in terminal. Reboot works fine as always. So I don't think it's sddm. And enabled it back now.

I did saw something else, probably obfuscated by the GUI till now? But somewhere here it says that it's just some notice, and someone in the kernel (or systemd?) developers team decided to put it there for whatever reason. It is a cgroup error, "mismatching" something, something, something too fast to see. Curious it's not in the logs?

Later Edit:
Found it https://bbs.archlinux.org/viewtopic.php … 1#p1567921 ! It seems other people have the same problem, doesn't seem like a confirmed bug, yet.

Last edited by fakemoth (2015-10-06 07:26:20)


Don't take the name of root in vain.

Offline

#10 2015-10-06 07:20:33

c3kay
Member
From: New Zealand
Registered: 2015-04-19
Posts: 61

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

Can you post the journal from the boot where sddm was disabled?

Offline

#11 2015-10-06 07:31:43

fakemoth
Member
From: Transylvania
Registered: 2015-09-23
Posts: 23

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

Here it is http://pastebin.com/69hbwdYC Only 3 red lines, some harmless mdadm, and 2 regarding login (systemd and pam). Don't know about these two... Anything else of interest there?


Don't take the name of root in vain.

Offline

#12 2015-10-06 07:57:41

c3kay
Member
From: New Zealand
Registered: 2015-04-19
Posts: 61

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

just a feeling. dhcpcd and network manager might be conflicting with each other. i see a few lines in both journals that indicate it could be having trouble shutting down the dchpcd service.

https://lists.archlinux.org/pipermail/a … 35827.html

disable dhcpcd.service and force the nm's internal dhcp client in network manager as per:

https://wiki.archlinux.org/index.php/Ne … HCP_client

this might be the case, because the feeling is some process related to a service is not shutting down properly and continues to run after the journal closes. and it'll do no harm disabling dhcpcd because network manager apparently has issues with it and can use dhclient.

Offline

#13 2015-10-06 09:00:11

fakemoth
Member
From: Transylvania
Registered: 2015-09-23
Posts: 23

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

Tried that right now, no luck: disabled dhcpcd, modified the NetworkManager conf file, restarted NetworkManager.service, tried twice to shut it down... It's the same, no power off for me yet.

Later Edit:
Booted some other drives, still no problems in openSUSE, it's just Arch.

Last edited by fakemoth (2015-10-06 09:11:15)


Don't take the name of root in vain.

Offline

#14 2015-10-06 09:10:30

c3kay
Member
From: New Zealand
Registered: 2015-04-19
Posts: 61

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

Post journal again? smile

Offline

#15 2015-10-06 09:13:38

fakemoth
Member
From: Transylvania
Registered: 2015-09-23
Posts: 23

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

Forgot about it, sry >>> http://pastebin.com/K4jv354s


Don't take the name of root in vain.

Offline

#16 2015-10-06 09:16:47

c3kay
Member
From: New Zealand
Registered: 2015-04-19
Posts: 61

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

dhcpcd is still running.

Offline

#17 2015-10-06 09:41:00

fakemoth
Member
From: Transylvania
Registered: 2015-09-23
Posts: 23

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

But... says it's not:

[root@PC fakemoth]# systemctl status dhcpcd.service
● dhcpcd.service - dhcpcd on all interfaces
   Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; disabled; vendor preset: disabled)
   Active: inactive (dead)

And the latest log http://pastebin.com/H1Cn8ten

I don't know what it keeps telling stuff about it... Is there any other way i can stop it, or... is something else starting it?


Don't take the name of root in vain.

Offline

#18 2015-10-06 10:12:26

c3kay
Member
From: New Zealand
Registered: 2015-04-19
Posts: 61

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

sorry, that was a little cryptic and unfair for me to take you down this road and then just say that. and i might have confused you by telling you to use the internal and then mentioning dhclient.

if you ps aux | grep dhcpcd you'll see it running.

nm is probably starting it. when you changed the dhcp= setting in nm did you change it to dhcp=dhclient or dhcp=internal? i might be wrong but i think if you set dhcp=dhclient and it can't be started then nm will use dhcpcd.

dhclient needs a unit file to be written for systemd because the package doesn't come with one.

Offline

#19 2015-10-06 10:20:09

fakemoth
Member
From: Transylvania
Registered: 2015-09-23
Posts: 23

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

No problem, you were trying to help, and I am more than grateful. Yes the thingy is running, but in the NM conf it's internal:

[main]
plugins=keyfile
dhcp=internal
dns=default

## Set static hostname
#[keyfile]
#hostname=foobar

## HTTP-based connectivity check
#[connectivity]
#uri=http://nmcheck.gnome.org/check_network_status.txt
#interval=100

Last edited by fakemoth (2015-10-06 10:21:12)


Don't take the name of root in vain.

Offline

#20 2015-10-06 12:33:00

c3kay
Member
From: New Zealand
Registered: 2015-04-19
Posts: 61

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

sorry, i was going to reply an hour ago but coincidentally dhcp on my router failed.

you could either:

1. disable it using:

systemctl stop dhcpcd
systemctl disable dhcpcd
systemctl mask dhcpcd

check the status with systemctl is-enabled dhcpcd. if something's wrong with the internal dhcp then you might break networking. but it's easy to change that with unmask, enable and start.

2. OR remove dhcpcd altogether. that'll stop it from starting and force nm to use the internal dhcp. of course, it might break your network so remember you have the package locally to reinstall from. you don't technically need dhcpcd installed unless you use ipv6, because currently nm's internal dhcp doesn't support that. but using dhcpcd with nm is currently not recommended anyway.

3. OR install dhclient, which is the recommended nm dhcp daemon. dhclient will need a systemd unit file written for it (lots of guides in places). then use dhcp=dhclient in the nm conf. you can safely remove dhcpcd (disable it to test before you do) because dhclient provides ipv6. then systemctl reload NetworkManager.

this is assuming that dhcpcd is causing the shutdown issues. big_smile

Offline

#21 2015-10-06 13:37:10

fakemoth
Member
From: Transylvania
Registered: 2015-09-23
Posts: 23

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

Of course, I stopped the service; you can see it in the status output above. That's why I was saying that I don't know what's with the lines in the log. For the reference:

[fakemoth@PC ~]$ systemctl is-enabled dhcpcd
disabled

Overall sorry to say but no. 2. I am sure it will break more things that will resolve, as there is no evidence that dhcpcd is related to my problem. Tested by killing the processes and stopping all the services related to NM and dhcpcd and issuing a 'systemctl poweroff' command. As you might guess, no joy.


Don't take the name of root in vain.

Offline

#22 2015-10-07 19:54:08

DarkCerberus
Banned
From: Holsworthy, Devon
Registered: 2011-12-31
Posts: 252

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

Sorry if I'm incorrect but this message is to the Moderator's - doesn't this fall in the line of the System Administration section instead of kernel and Hardware as per https://bbs.archlinux.org/viewtopic.php?id=163496 - it seems to me as a challenging topic and might be properly looked at in that area of the forum...

@ Fakemoth have you checked the bugs.archlinux.org for any clues about this issue and have you tried other display managers?

Last edited by DarkCerberus (2015-10-07 19:55:43)


Our enemies are your enemies, Nick. Disorder, war. It's just a matter of time before a dirty bomb goes off in Moscow, or an EMP fries Chicago.  ---  Alexander Pierce, Captain America: Winter Soldier
Access Denied! De-cryption failed, override denied all files sealed! --- Triskelion, Shield OS
-----
How to ask questions the smart way

Offline

#23 2015-10-07 20:07:00

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 17,929

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

Perhaps.   It might not be a kernel problem.  I'll leave it to fakemoth to make a move request.    BTW, it is better to make such a request using the 'Report' function of the thread.  Moderators will see it much faster, and it does not clutter the discussion.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#24 2015-10-08 07:36:47

fakemoth
Member
From: Transylvania
Registered: 2015-09-23
Posts: 23

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

Well it might be the case, but in my defense I didn't know about the current direction at that time, of course initially was thinking that it's the kernel. Now after all this and a few more kernel updates, and very few topics similar to this, I really don't. But it still seems to me that is hardware related, systemd not coping with my way too new motherboard or something.

@DarkCerberus I already tried even without any display manager, it's not that.
@ewaller I will report myself smile !

Later info:
I requested the admins via the report function the relocation to another (more appropriate) section of the forum.

Last edited by fakemoth (2015-10-08 07:44:26)


Don't take the name of root in vain.

Offline

#25 2015-10-08 10:55:14

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 25,738
Website

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

Moved to Sys Admin issues per OP request.

I agree it is not clear exactly where this would fit best - but it's possible the move will get a new set of eyes on it.  However I'm not too sure about that: I suspect many forum users do not selectively read within subforums much, but it couldn't hurt.


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

Board footer

Powered by FluxBB