Arch Linux

M4RC0Sx

Member

Registered: 2020-06-29

Posts: 13

Error on startup

Hi, I installed Arch and it all works good except that I have to wait for a timeout on startup.
That´s what I find in the journal:

-- Logs begin at Wed 2020-06-10 22:59:26 CEST, end at Mon 2020-06-29 11:58:14 CEST. --
Jun 29 11:56:44 masarch kernel: platform MSFT0101:00: failed to claim resource 1: [mem 0xfed40000-0xfed40fff]
Jun 29 11:56:44 masarch kernel: acpi MSFT0101:00: platform device creation failed: -16
Jun 29 11:58:14 masarch systemd[1]: Timed out waiting for device /sys/subsystem/net/devices/service.
-- Subject: A start job for unit sys-subsystem-net-devices-service.device has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l … temd-devel
--
-- A start job for unit sys-subsystem-net-devices-service.device has finished with a failure.
--
-- The job identifier is 91 and the job result is timeout.

I don´t know what to do and how could a find more details about the problem. But I have to wait like 90 seconds until timeout and I can log in into my system.

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 29,520

Website

Re: Error on startup

Please post a link to the complete journal.

There have been many cases of failing network connections blocking boot for 90 seconds.  Given the net device unit failing, I highly suspect that is what may be happening for you - but I'm not specifically familiar with the sys-subsystem-net-devices-service.device unit: I'm speculating that it may depend on a network service that failed.

What networking services do you have enabled?

---

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

M4RC0Sx

Member

Registered: 2020-06-29

Posts: 13

Re: Error on startup

I have NetworkManager and wpa_supplicant enabled. I tried disabling them and nithing changed.

seth

Member

Registered: 2012-09-03

Posts: 50,957

Re: Error on startup

I tried disabling them

Let's see…

find /etc/systemd -type l -exec test -f {} \; -print

Also please post the complete output of "sudo journalctl -b"

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

M4RC0Sx

Member

Registered: 2020-06-29

Posts: 13

Re: Error on startup

Output of the find command:

/etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service
/etc/systemd/system/getty.target.wants/getty@tty1.service
/etc/systemd/system/dbus-fi.w1.wpa_supplicant1.service
/etc/systemd/system/multi-user.target.wants/wpa_supplicant.service
/etc/systemd/system/multi-user.target.wants/NetworkManager.service
/etc/systemd/system/multi-user.target.wants/remote-fs.target
/etc/systemd/system/multi-user.target.wants/dhcpcd@service.service
/etc/systemd/system/multi-user.target.wants/cronie.service
/etc/systemd/system/multi-user.target.wants/ntpd.service
/etc/systemd/system/network-online.target.wants/NetworkManager-wait-online.service
/etc/systemd/user/sockets.target.wants/p11-kit-server.socket
/etc/systemd/user/sockets.target.wants/gpg-agent.socket
/etc/systemd/user/sockets.target.wants/dirmngr.socket
/etc/systemd/user/sockets.target.wants/gpg-agent-extra.socket
/etc/systemd/user/sockets.target.wants/gpg-agent-ssh.socket
/etc/systemd/user/sockets.target.wants/pulseaudio.socket
/etc/systemd/user/sockets.target.wants/gpg-agent-browser.socket

Full journal:

Jun 30 09:45:42 masarch kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/ … n/mds.html for more details.
Jun 30 09:45:42 masarch kernel:  #3
Jun 30 09:45:42 masarch kernel: pmd_set_huge: Cannot satisfy [mem 0xe0000000-0xe0200000] with a huge-page mapping due to MTRR override.
Jun 30 09:45:42 masarch kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jun 30 09:45:42 masarch kernel: platform MSFT0101:00: failed to claim resource 1: [mem 0xfed40000-0xfed40fff]
Jun 30 09:45:42 masarch kernel: acpi MSFT0101:00: platform device creation failed: -16
Jun 30 09:45:42 masarch kernel: ata1.00: supports DRM functions and may not be fully accessible
Jun 30 09:45:42 masarch kernel: ata1.00: supports DRM functions and may not be fully accessible
Jun 30 09:45:42 masarch kernel: usb: port power management may be unreliable
Jun 30 09:45:42 masarch systemd-journald[215]: Journal started
Jun 30 09:45:42 masarch systemd-journald[215]: Runtime Journal (/run/log/journal/32064d8bb17746ea9937e212bcde8e34) is 6.2M, max 50.0M, 43.7M free.
Jun 30 09:45:42 masarch systemd-journald[215]: Time spent on flushing to /var/log/journal/32064d8bb17746ea9937e212bcde8e34 is 898us for 11 entries.
Jun 30 09:45:42 masarch systemd-journald[215]: System Journal (/var/log/journal/32064d8bb17746ea9937e212bcde8e34) is 50.0M, max 50.0M, 0B free.
Jun 30 09:45:42 masarch kernel: wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
Jun 30 09:45:42 masarch kernel: wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
Jun 30 09:45:42 masarch kernel: wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
Jun 30 09:45:42 masarch kernel: wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
Jun 30 09:45:42 masarch kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:02)
Jun 30 09:45:42 masarch kernel: tpm_crb MSFT0101:00: [Firmware Bug]: Bad ACPI memory layout
Jun 30 09:45:42 masarch kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Jun 30 09:45:42 masarch kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwl-debug-yoyo.bin failed with error -2
Jun 30 09:45:42 masarch kernel: uvcvideo 1-5:1.0: Entity type for entity Extension 4 was not initialized!
Jun 30 09:45:42 masarch kernel: uvcvideo 1-5:1.0: Entity type for entity Extension 3 was not initialized!
Jun 30 09:45:42 masarch kernel: uvcvideo 1-5:1.0: Entity type for entity Processing 2 was not initialized!
Jun 30 09:45:42 masarch kernel: uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not initialized!
Jun 30 09:45:43 masarch kernel: thermal thermal_zone2: failed to read out thermal zone (-61)
Jun 30 09:45:43 masarch kernel: iwlwifi 0000:02:00.0: FW already configured (0) - re-configuring
Jun 30 09:45:44 masarch kernel: iwlwifi 0000:02:00.0: FW already configured (0) - re-configuring
Jun 30 09:45:44 masarch NetworkManager[321]: <warn>  [1593503144.1716] sup-iface[00d2dabdff189380,0,wlp2s0]: call-p2p-cancel: failed with P2P cancel failed
Jun 30 09:45:44 masarch kernel: [Firmware Bug]: ACPI(PXSX) defines _DOD but not _DOS
Jun 30 09:45:44 masarch systemd-udevd[230]: controlC0: Process '/usr/bin/alsactl restore 0' failed with exit code 99.
Jun 30 09:45:48 masarch kernel: kauditd_printk_skb: 15 callbacks suppressed
Jun 30 09:47:11 masarch systemd[1]: sys-subsystem-net-devices-service.device: Job sys-subsystem-net-devices-service.device/start timed out.
Jun 30 09:47:11 masarch systemd[1]: Timed out waiting for device /sys/subsystem/net/devices/service.
Jun 30 09:47:11 masarch systemd[1]: Dependency failed for dhcpcd on service.
Jun 30 09:48:58 masarch gnome-keyring-daemon[1709]: asked to register item /org/freedesktop/secrets/collection/Default_5fkeyring/5, but it's already registered
Jun 30 09:48:58 masarch gnome-keyring-d[1709]: asked to register item /org/freedesktop/secrets/collection/Default_5fkeyring/5, but it's already registered
Jun 30 09:48:58 masarch gnome-keyring-daemon[1709]: asked to register item /org/freedesktop/secrets/collection/Default_5fkeyring/5, but it's already registered
Jun 30 09:48:58 masarch gnome-keyring-d[1709]: asked to register item /org/freedesktop/secrets/collection/Default_5fkeyring/5, but it's already registered
Jun 30 09:50:01 masarch kernel: kauditd_printk_skb: 12 callbacks suppressed

seth

Member

Registered: 2012-09-03

Posts: 50,957

Re: Error on startup

That's not the full journal by any stretch and please use code tags.

Anyway, you've networkmanager, wpa_supplicant and dhcpcd (a whopping 3 different services) enabled.
Try harder, pick one and disable the other two.

The timeout is (likely, from what one can guess from the fraction of the journal)  because dhcpcd requires it while NM is already messing around w/ the device.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc