Your message dated Sun, 22 Jan 2023 07:40:49 +0200 with message-id <capzxpqcciezhgmlujeg5ipw4sushbfv2jhbzkow40tpvo5m...@mail.gmail.com> and subject line Re: Bug#1029176: please check dhcpcd 9.4.1-14 in unstable has caused the Debian Bug report #1029174, regarding dhcpcd-base: Brakes networking completely to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1029174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029174 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: dhcpcd-base Version: 9.4.1-13 Severity: grave Justification: renders package unusable When this version is installed, all networking is broken, e.g. root@twentytwo:~# LC_ALL=C ping lwn.net ping: lwn.net: Temporary failure in name resolution I cannot access *any* outside resource. No IP, no ssh, no ping, .. Additionally, comands involving network state take several minutes, i.e. running into timeouts. E.g. systemctl restart networking Or shutdown takes several minutes (for each interface) before completion. If I strace such a command, I see: access("/run/network/ifstate.enp3s0", R_OK) = 0 openat(AT_FDCWD, "/run/network/ifstate.enp3s0", O_RDWR|O_CREAT|O_APPEND|O_CLOEXEC, 0666) = 3 fcntl(3, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = -1 EAGAIN (Die Ressource ist zur Zeit nicht verfügbar) write(2, "ifdown: ", 8ifdown: ) = 8 write(2, "waiting for lock on /run/network"..., 47waiting for lock on /run/network/ifstate.enp3s0) = 47 write(2, "\n", 1 ) = 1 fcntl(3, F_SETLKW, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0} And there it hangs. (I did not search if this is the only place for hangs, but it was the first). Downgrading to 9.4.1-11 fixes the problem, i.e. the machine behaves normally after reboot. This is reproducible, i.e. upgrading to -13 and rebooting and the broken network is back; downgrading and rebooting and the network is fine again. Please tell me which data you need to further boil this down and I can provide it. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages dhcpcd-base depends on: ii adduser 3.130 ii libc6 2.36-8 ii libudev1 252.4-1 dhcpcd-base recommends no packages. dhcpcd-base suggests no packages. -- no debconf information -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---On Fri, Jan 20, 2023 at 5:11 PM Martin-Éric Racine <martin-eric.rac...@iki.fi> wrote: > > On Thu, Jan 19, 2023 at 10:25 PM Beat Bolli <i...@drbeat.li> wrote: > > On 19.01.23 16:35, Martin-Éric Racine wrote: > > > We've just pushed dhcpcd 9.4.1-14 into unstable. Can you please check > > > whether that fixes it? > > > > Indeed, this new version works. > > Marking FIXED as of 9.4.1-14 . I'll wait until it has trickled down to > Testing before closing. Closing. Martin-Éric
--- End Message ---
