Devuan bug report logs - #521
boot hangs on 'ifup: waiting for lock'

Package: devuan-desktop; Maintainer for devuan-desktop is Devuan Developers <devuan-dev@lists.dyne.org>;

Reported by: leirbag <leirbag@sdfeu.org>

Date: Wed, 11 Nov 2020 07:48:02 UTC

Severity: normal

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to devuan-bugs@lists.dyne.org, Devuan Developers <devuan-dev@lists.dyne.org>:
bug#521; Package devuan-desktop. (Wed, 11 Nov 2020 07:48:02 GMT) (full text, mbox, link).


Acknowledgement sent to leirbag <leirbag@sdfeu.org>:
New bug report received and forwarded. Copy sent to Devuan Developers <devuan-dev@lists.dyne.org>. (Wed, 11 Nov 2020 07:48:04 GMT) (full text, mbox, link).


Message #5 received at submit@bugs.devuan.org (full text, mbox, reply):

From: leirbag <leirbag@sdfeu.org>
To: submit@bugs.devuan.org
Subject: boot hangs on 'ifup: waiting for lock'
Date: Wed, 11 Nov 2020 08:31:50 +0100
Package: devuan-desktop
Severity: normal

Dear Maintainer,

Booting process hangs on what seems to be the initialisation of network:
it remains on

Configuring network interfaces...ifup: waiting for lock on 
/run/network/ifstate.eth0

for a long time (I hence usually skip this phase with C-c). When logging
into the desktop, internet is available (through eth0).

The setup is very close to the default one (wicd is used).

-- System Information:
Distributor ID: Debian
Description:    Devuan GNU/Linux 3 (beowulf)
Release:        3
Codename:       beowulf
Architecture: x86_64

Kernel: Linux 4.19.0-12-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Information forwarded to devuan-bugs@lists.dyne.org, Devuan Developers <devuan-dev@lists.dyne.org>:
bug#521; Package devuan-desktop. (Wed, 11 Nov 2020 08:33:01 GMT) (full text, mbox, link).


Acknowledgement sent to leirbag <leirbag@sdfeu.org>:
Extra info received and forwarded to list. Copy sent to Devuan Developers <devuan-dev@lists.dyne.org>. (Wed, 11 Nov 2020 08:33:03 GMT) (full text, mbox, link).


Message #10 received at 521@bugs.devuan.org (full text, mbox, reply):

From: leirbag <leirbag@sdfeu.org>
To: 521@bugs.devuan.org
Subject: Possible cause of problem
Date: Wed, 11 Nov 2020 09:19:20 +0100
Hi,

Section 5.2.1 of Debian Handbook suggests that wicd might conflict with 
ifup, and hence advise to keep the file /etc/network/interfaces as 
simple as possible, such as

auto lo
iface lo inet loopback

or disable wicd and let ifup do the work. Perhaps the default 
/etc/network/interfaces should be changed?

-- My /etc/network/interfaces:
source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet dhcp
iface eth0 inet6 auto

Information forwarded to devuan-bugs@lists.dyne.org, Devuan Developers <devuan-dev@lists.dyne.org>:
bug#521; Package devuan-desktop. (Wed, 11 Nov 2020 14:03:01 GMT) (full text, mbox, link).


Acknowledgement sent to tito <farmatito@tiscali.it>:
Extra info received and forwarded to list. Copy sent to Devuan Developers <devuan-dev@lists.dyne.org>. (Wed, 11 Nov 2020 14:03:04 GMT) (full text, mbox, link).


Message #15 received at 521@bugs.devuan.org (full text, mbox, reply):

From: tito <farmatito@tiscali.it>
To: devuan-dev@lists.dyne.org, leirbag <leirbag@sdfeu.org>, 521@bugs.devuan.org
Subject: Re: [devuan-dev] bug#521: boot hangs on 'ifup: waiting for lock'
Date: Wed, 11 Nov 2020 14:43:46 +0100
On Wed, 11 Nov 2020 08:31:50 +0100
leirbag <leirbag@sdfeu.org> wrote:

> Package: devuan-desktop
> Severity: normal
> 
> Dear Maintainer,
> 
> Booting process hangs on what seems to be the initialisation of
> network: it remains on
> 
> Configuring network interfaces...ifup: waiting for lock on 
> /run/network/ifstate.eth0
> 
> for a long time (I hence usually skip this phase with C-c). When
> logging into the desktop, internet is available (through eth0).
> 
> The setup is very close to the default one (wicd is used).
> 
> -- System Information:
> Distributor ID: Debian
> Description:    Devuan GNU/Linux 3 (beowulf)
> Release:        3
> Codename:       beowulf
> Architecture: x86_64
> 
> Kernel: Linux 4.19.0-12-amd64 (SMP w/4 CPU cores)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
> TAINT_UNSIGNED_MODULE
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_GB:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
> LSM: AppArmor: enabled

Hi,
I worked around this by changing /etc/network/interfaces to:

______________________________________________________________
iface eth0 inet manual
        pre-up /sbin/ip link set eth0 up
        up /sbin/dhclient -nw -4 -v -i -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases -I -df /var/lib/dhclient6.eth0.leases eth0
        pre-down /sbin/dhclient -r -4 -v -i -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases -I -df /var/lib/dhclient6.eth0.leases eth0
        down /sbin/ip link set eth0 down
______________________________________________________________

and installing ifplugd and setting /etc/default/ifplugd to:

______________________________________________________________
INTERFACES="eth0"
HOTPLUG_INTERFACES=""
ARGS="-q -f -u0 -d10 -w -I"
SUSPEND_ACTION="stop"
______________________________________________________________

This way boot is fast and the network is setup in the background 
as soon as ifplugd detects the link beat.
Don't know how this will interact with wicd.

Ciao,
Tito

 

Send a report that this bug log contains spam.


Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.

Devuan Bugs Owner <owner@bugs.devuan.org>.
Last modified: Sat Aug 13 00:38:48 2022;