Timed out waiting for device sys-subsystem-net ...

jorge_ · 2016-06-04 14:08:50

Hello all,

since the last pacman -Syu I am encountering some issues at boot. A startup job timeouts for me, which basically means I have to wait 90 secs at every boot. I am using Arch approx. 2 months and did not change any configuration after system installation.

During boot I see the following startup progress notification

A start job is running for sys-subsystem-net-devices-::1.device

which timeouts after 90 secs and more failure messages appear

[TIME] Timed out waiting for sys-subsystem-net-devices-::1.device
[DEPEND] Dependency failed for dhcpcd on ::1

I have tried to look at systemctl for anything related to ::1 without success.
Would anyone point me in the right direction? Given my (small) knowledge of arch, I am at the end of my wits.

Last edited by jorge_ (2016-06-06 15:48:22)

Slithery · 2016-06-04 14:27:42

::1 is the IPv6 equivalent of IPv4's 127.0.0.1, ie localhost.

Have you gone through the steps in https://wiki.archlinux.org/index.php/sy … leshooting

jorge_ · 2016-06-04 15:05:34

Systemctl does not list any failed services. However, it does list dhcpcd as inactive (dead). In that case the weird thing is my connection still works ...

[jirka@portege ~]$ 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'.
[jirka@portege ~]$ systemctl status dhcpcd
● dhcpcd.service - dhcpcd on all interfaces
   Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; disabled; vendor preset: disabled)
   Active: inactive (dead)

dhcpcd does not seem to have any problem when started manually ...

[jirka@portege ~]$ systemctl stop dhcpcd
[jirka@portege ~]$ sudo SYSTEMD_LOG_LEVEL=debug /usr/bin/dhcpcd 
[sudo] heslo pro jirka: 
dev: loaded udev
DUID 00:01:00:01:1e:6d:e9:b0:34:e6:ad:0b:44:b0
wlan0: IAID ad:0b:44:b0
eth0: waiting for carrier
wlan0: rebinding lease of 192.168.1.161
wlan0: probing address 192.168.1.161/24
wlan0: soliciting an IPv6 router
wlan0: leased 192.168.1.161 for 43200 seconds
wlan0: adding route to 192.168.1.0/24
wlan0: adding default route via 192.168.1.1
forked to background, child pid 1725

By the way, localhost seems to work fine (apart from the boot delay), tried using Ruby on Rails server ...

Last edited by jorge_ (2016-06-04 15:15:03)

jorge_ · 2016-06-04 15:32:39

Solved for now after some googleing by downgrading to systemd v229 ...

xithix · 2016-06-05 14:32:38

I'm having the same issue with systemd v230, and had to downgrade to v229 to resolve as well.

I have a USB wifi card I swapped out months ago with device id wlp0s29u1u2, but systemd v230 is getting stuck trying to load it at startup in the newest version.

Similarly, the device does not appear as a failed service.

[user@xithix netctl]$ systemctl --failed
  UNIT                         LOAD   ACTIVE SUB    DESCRIPTION
● systemd-backlight@backlight:acpi_video0.service loaded failed failed Load/Save

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

netctl -disable says the profile does not exist, and grepping for the interface returns nothing.

[user@xithix netctl]$ grep -ir wlp0s29u1u2 /etc/systemd/*
[user@xithix netctl]$

I really have no idea where to go next with this.

josealb77 · 2016-06-05 15:59:53

Downgrade to the previous package version IS NOT a reason to mark the thread as SOLVED even not "somewhat". It is a problem more people is having. In someway we are duplicating threads. Here is my message in other newbie corner thread: https://bbs.archlinux.org/viewtopic.php … 3#p1632133

josealb77 · 2016-06-06 07:11:41

This solved the problem for me: https://bbs.archlinux.org/viewtopic.php … 5#p1632295

xithix · 2016-06-07 22:56:12

josealb77 wrote:

This solved the problem for me: https://bbs.archlinux.org/viewtopic.php … 5#p1632295

Whoo! Thanks. This resolved the issue for me as well.

Ron74 · 2016-06-13 03:16:30

josealb77 wrote:

This solved the problem for me: https://bbs.archlinux.org/viewtopic.php … 5#p1632295

The same problem solved for me also. many thanks.

jasonwryan · 2016-06-13 03:17:36

No need to power post: https://wiki.archlinux.org/index.php/Co … mpty_posts

Closing.

Arch Linux

#1 2016-06-04 14:08:50

Timed out waiting for device sys-subsystem-net ...

#2 2016-06-04 14:27:42

Re: Timed out waiting for device sys-subsystem-net ...

#3 2016-06-04 15:05:34

Re: Timed out waiting for device sys-subsystem-net ...

#4 2016-06-04 15:32:39

Re: Timed out waiting for device sys-subsystem-net ...

#5 2016-06-05 14:32:38

Re: Timed out waiting for device sys-subsystem-net ...

#6 2016-06-05 15:59:53

Re: Timed out waiting for device sys-subsystem-net ...

#7 2016-06-06 07:11:41

Re: Timed out waiting for device sys-subsystem-net ...

#8 2016-06-07 22:56:12

Re: Timed out waiting for device sys-subsystem-net ...

#9 2016-06-13 03:16:30

Re: Timed out waiting for device sys-subsystem-net ...

#10 2016-06-13 03:17:36

Re: Timed out waiting for device sys-subsystem-net ...

Board footer