Arch Linux

zerophase

Member

Registered: 2015-09-03

Posts: 229

[SOLVED]Arch takes forever to shutdown or reboot.

Starting yesterday most of the time when I shutdown the computer sits at a red screen for at least five minutes.  Since then I've removed prelink, and steam package. That removed the red screen, but my system still takes forever to shutdown.  I started debugging the shutdown process, and have a huge text file I'm currently parsing.  So far

passed device to netlink monitor

is the only thing that keeps getting repeated 1 / 4 of the way through the file.  I'll add more once I get further in the file.

Have any suggestions for entries I should watch out for?

Last edited by zerophase (2015-09-11 14:32:39)

frank604

Member

From: BC, Canada

Registered: 2011-04-20

Posts: 1,212

Re: [SOLVED]Arch takes forever to shutdown or reboot.

You could probably post the complete dmesg log from last boot for us.

zerophase

Member

Registered: 2015-09-03

Posts: 229

Re: [SOLVED]Arch takes forever to shutdown or reboot.

Alright, here's the link to the file. https://drive.google.com/file/d/0B-Ei-Z … sp=sharing

The only things I have found in the shutdown log are:

NVRM: Your system is not currently configured to drive a VGA console
NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
NVRM: requires the use of a text-mode VGA console. Use of other console
NVRM: drivers including, but not limited to, vesafb, may result in
NVRM: corruption and stability problems, and is not supported.

Also in Journalctl smbd and nmbd won't start.  I do have dnsmasq running as well. My samba drives still mount though using automount in fstab.

Unit nmbd.service has begun starting up.
Sep 10 09:13:44 Odin nmbd[968]: [2015/09/10 09:13:44.099971,  0] ../lib/util/util.c:285(directory_create_or_exist_strict)
Sep 10 09:13:44 Odin nmbd[968]:   invalid permissions on directory '/var/cache/samba/msg': has 0700 should be 0755
Sep 10 09:13:44 Odin systemd[1]: nmbd.service: Control process exited, code=exited status=1
Sep 10 09:13:44 Odin systemd[1]: Failed to start Samba NetBIOS name server.
Subject: Unit nmbd.service has failed
Defined-By: systemd
Support: http://lists.freedesktop.org/mailman/li … temd-devel

Unit nmbd.service has failed.

The result is failed.

Sep 10 09:23:09 Odin sudo[1549]: pam_unix(sudo:session): session opened for user root by zerophase(uid=0)
Sep 10 09:23:09 Odin polkitd[543]: Registered Authentication Agent for unix-process:1551:58986 (system bus name :1.37 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/Authent
Sep 10 09:23:09 Odin systemd[1]: Starting Samba SMB/CIFS server...
Subject: Unit smbd.service has begun start-up
Defined-By: systemd
Support: http://lists.freedesktop.org/mailman/li … temd-devel

Unit smbd.service has begun starting up.
Sep 10 09:23:09 Odin systemd[1]: smbd.service: Control process exited, code=exited status=1
Sep 10 09:23:09 Odin systemd[1]: Failed to start Samba SMB/CIFS server.
Subject: Unit smbd.service has failed
Defined-By: systemd
Support: http://lists.freedesktop.org/mailman/li … temd-devel

Unit smbd.service has failed.

The result is failed.

According to this post I just need to add /etc/samba/samba.conf and change security to share. I changed the configuration file back to default and changed it to share with no luck.

In Journalctl I also have pcie errors listed. I don't know if those have any effect on the shutdown time

Sep 10 09:19:33 Odin kernel: pcieport 0000:00:03.0: AER: Corrected error received: id=0018
Sep 10 09:19:33 Odin kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0018(Transmitter ID)
Sep 10 09:19:33 Odin kernel: pcieport 0000:00:03.0:   device [8086:2f08] error status/mask=00001000/00002000
Sep 10 09:19:33 Odin kernel: pcieport 0000:00:03.0:    [12] Replay Timer Timeout 
Sep 10 09:19:33 Odin kernel: pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018
Sep 10 09:19:33 Odin kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0018(Receiver ID)
Sep 10 09:19:33 Odin kernel: pcieport 0000:00:03.0:   device [8086:2f08] error status/mask=00000040/00002000
Sep 10 09:19:33 Odin kernel: pcieport 0000:00:03.0:    [ 6] Bad TLP               
Sep 10 09:19:34 Odin kernel: pcieport 0000:00:03.0: AER: Corrected error received: id=0018
Sep 10 09:19:34 Odin kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0018(Receiver ID)
Sep 10 09:19:34 Odin kernel: pcieport 0000:00:03.0:   device [8086:2f08] error status/mask=00000040/00002000
Sep 10 09:19:34 Odin kernel: pcieport 0000:00:03.0:    [ 6] Bad TLP               
Sep 10 09:19:34 Odin kernel: pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018
Sep 10 09:19:34 Odin kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0018(Receiver ID)
Sep 10 09:19:34 Odin kernel: pcieport 0000:00:03.0:   device [8086:2f08] error status/mask=00000040/00002000
Sep 10 09:19:34 Odin kernel: pcieport 0000:00:03.0:    [ 6] Bad TLP               
Sep 10 09:19:34 Odin kernel: pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018
Sep 10 09:19:34 Odin kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0018(Receiver ID)
Sep 10 09:19:34 Odin kernel: pcieport 0000:00:03.0:   device [8086:2f08] error status/mask=00000040/00002000
Sep 10 09:19:34 Odin kernel: pcieport 0000:00:03.0:    [ 6] Bad TLP               
Sep 10 09:19:52 Odin kernel: [UFW BLOCK] IN=wlp6s0 OUT= MAC=40:e2:30:85:b9:fe:50:46:5d:d1:81:00:08:00 SRC=198.252.206.25 DST=192.168.1.25 LEN=110 TOS=0x00 PREC=0x00 TTL=51 ID=25198 DF PROTO=TCP SPT=443 DPT=53269 W

Last edited by zerophase (2015-09-10 14:39:27)

niceman

Member

Registered: 2015-08-31

Posts: 55

Re: [SOLVED]Arch takes forever to shutdown or reboot.

the first is just a warning that won't cause something like that(if you're interested I removed by appending video:vesa=off vga=normal to my kernel paramters).

Now I see PCIe error repeating So I doubt you have some hardware issue.

Do you have these problems with the same hardware but different OS ? also was it normal after installation and had this problem suddenly or you had the problem right after the installation ?

Edit : As a comment to this question http://askubuntu.com/questions/643952/p … -dmesg-log , those are just warnings, strange but in your file it seems to remount /dev/sda3 after unmounting it when it shouldn't do on shutdown(and after succeding in unmounting it too !).

Last edited by niceman (2015-09-10 16:57:15)

zerophase

Member

Registered: 2015-09-03

Posts: 229

Re: [SOLVED]Arch takes forever to shutdown or reboot.

This doesn't happen when I shutdown from Windows 10.  The shutdown was normal after installation, and it just started after I installed Steam, Prelink, and did a system update. Removed steam and prelink with no effect. I added this script:

mount -o remount,rw /
dmesg > /shutdown-log.txt
mount -o remount,ro /

to the save the output from each shutdown. I'm going to try disabling lightdm and see if that has any effect.

And the issue has seemed to go away, after I disabled lightdm and reenabled it on the next boot. Removed my debug script from remounting root, and changed some boot parameters and fstab parameters.

Added quiet to refind_linux.conf:

"Boot with standard options"        "ro root=UUID=ea0238be-78af-42b6-aff9-a5c82d5716c9 quiet ipv6.disable=1 initrd=intel-ucode.img initrd=initramfs-linux.img elevator=noop"
"Boot to single-user mode"          "ro root=UUID=ea0238be-78af-42b6-aff9-a5c82d5716c9   single"
"Boot with minimal options"         "ro root=UUID=ea0238be-78af-42b6-aff9-a5c82d5716c9"

changed fstab to include discard on swap:

#
# /etc/fstab: static file system information
#
# <file system>    <dir>    <type>    <options>    <dump>    <pass>
# /dev/sda3
UUID=ea0238be-78af-42b6-aff9-a5c82d5716c9    /             ext4          rw,noatime,data=ordered    0 1

# /dev/sda1
UUID=F0B2-9AD9          /boot         vfat          rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro    0 2

# /dev/sda4
UUID=2dc1667e-7e55-448f-b008-bb4fe8ba8126    /var          ext4          rw,noatime,data=ordered    0 2

# /dev/sda5
UUID=6f3de07b-0914-4554-abd4-b805376a9ba4    /home         ext4          rw,noatime,data=ordered    0 2

# /dev/sda2
UUID=bc6b2916-bf76-4932-a9e5-271dc7eef323    none          swap          defaults,discard      0 0

//192.168.1.1/SystemBackUp /mnt/SystemBackUp cifs credentials=/etc/credentials/sambacreds,x-systemd.automount, 0 0

I'm going to reboot and shutdown a few times to make sure the times stay the same. The odd thing is I had those slow shutdown times before I added that debug script.

**Update: Just rebooted and the issue came back. It appears to be intermittent with it happening on most shutdowns.

Last edited by zerophase (2015-09-10 18:22:45)

VCoolio

Member

From: Netherlands

Registered: 2010-01-05

Posts: 120

Re: [SOLVED]Arch takes forever to shutdown or reboot.

I think I had similar trouble (long shutdown) some time ago. Had to do with a network share unmount thing. Don't know what the problem was, maybe network already closed before it tried to unmount. Couldn't solve it (still struggling getting dirty with systemd), so I removed the automount part in fstab, made it noauto. May not at all be your problem, but it's easy to give it a shot in your SystemBackUp line.

zerophase

Member

Registered: 2015-09-03

Posts: 229

Re: [SOLVED]Arch takes forever to shutdown or reboot.

@VCoolio that seems to have worked. Now, I just need to figure out how to get systemd to dismount it correctly. (If I forget to unmount the drive during shutdown I run into a long wait time) I also have to remember what I configured for controlling samba shares in place of smbd and nmbd.

It looks, like systemd-networkd might be able to solve the issue.

**Update1: looks like some how my /var/cache/samba/msg had it's permission changed to 0700, instead of 0755.  Maybe that was causing the issue.

**Update2: Think I fixed the slow shut down, while still allowing for automount.  I just had to make sure smbd and nmbd were using different loop back ports from dnsmasq. That way all three could startup at boot, without getting in the way of each other and allow the drive to be be unmounted correctly during shutdown.

Last edited by zerophase (2015-09-11 06:42:28)