[Pkg-utopia-maintainers] Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity
On Tue, 05 Mar 2019 09:03:53 +0100 Dominique Dumont wrote: > They probably patched curl with [1] following the resolution if this curl bug > [2]. I don't know > archlinux enough to track down the patch applied to curl version 7.64.0-9 Never mind. Archlinux 's web site is easy to use. Here's the patch they applied to curl package [1]. They indeed used the commit that resolved the curl bug upstream . ghedo, can you take over this bug for curl package and release a fix ? All the best [1] https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/curl=4ea6d939508dd6140d3bba0b784f081e4e75ec0f ___ Pkg-utopia-maintainers mailing list Pkg-utopia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
[Pkg-utopia-maintainers] Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity
On Sun, 03 Mar 2019 14:23:40 +0100 gpe wrote: > it seems that the issue is resolved with their last curl version 7.64.0-9, no? Looks like it. They probably patched curl with [1] following the resolution if this curl bug [2]. I don't know archlinux enough to track down the patch applied to curl version 7.64.0-9 Note: I've linked this Debian bug to upstream network-manager bug [3] HTH [1] https://github.com/curl/curl/commit/b7753be57d7bdb6b909f1a0a4207950e18100d79 [2] https://github.com/curl/curl/issues/3585 [3] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/123 ___ Pkg-utopia-maintainers mailing list Pkg-utopia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
[Pkg-utopia-maintainers] Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity
On Sat, 02 Mar 2019 19:49:49 +0100 Dominique Dumont wrote: > On Mon, 18 Feb 2019 01:45:12 +0100 Jiri Palecek wrote: > > exe->curl_multi_socket_action(0x15c4900, 24, 2, 0xbfb0bd88) = 0 > > exe->curl_multi_info_read(0x15c4900, 0xbfb0bd80, 2, 0xbfb0bd88) = 0 > > Looks related to > https://bugs.archlinux.org/index.php?do=details=details.addvote_id=61688 > > where they suggest to downgrade curl (or libcurl in our case) > > HTH > > > > it seems that the issue is resolved with their last curl version 7.64.0-9, no? ___ Pkg-utopia-maintainers mailing list Pkg-utopia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
[Pkg-utopia-maintainers] Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity
On Mon, 18 Feb 2019 01:45:12 +0100 Jiri Palecek wrote: > exe->curl_multi_socket_action(0x15c4900, 24, 2, 0xbfb0bd88) > > = 0 > exe->curl_multi_info_read(0x15c4900, 0xbfb0bd80, 2, 0xbfb0bd88) > > = 0 Looks related to https://bugs.archlinux.org/index.php?do=details=details.addvote_id=61688 where they suggest to downgrade curl (or libcurl in our case) HTH ___ Pkg-utopia-maintainers mailing list Pkg-utopia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
[Pkg-utopia-maintainers] Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity
On Tue, 26 Feb 2019 19:26:30 +0100 Michael Biebl wrote: > Control: tags -1 + moreinfo > > Do you have network-manager-config-connectivity-debian installed or > connectivity checking enabled otherwise? Yes network-manager-config-connectivity-debian is installed > Is the server reachable for the connectivity check reachable? Not sure to understand the question but the connectivity is ok even if I kill NetworManager to avoid CPU consumption. BR ___ Pkg-utopia-maintainers mailing list Pkg-utopia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
[Pkg-utopia-maintainers] Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity
Control: tags -1 + moreinfo Do you have network-manager-config-connectivity-debian installed or connectivity checking enabled otherwise? Is the server reachable for the connectivity check reachable? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-utopia-maintainers mailing list Pkg-utopia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
[Pkg-utopia-maintainers] Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity
Package: network-manager Version: 1.14.4-4 Followup-For: Bug #922554 Dear Maintainer, I've exactly the same problem since few days. BR -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages network-manager depends on: ii adduser3.118 ii dbus 1.12.12-1 ii init-system-helpers1.56+nmu1 ii libaudit1 1:2.8.4-2 ii libbluetooth3 5.50-1 ii libc6 2.28-7 ii libcurl3-gnutls7.64.0-1 ii libglib2.0-0 2.58.3-1 ii libgnutls303.6.6-2 ii libjansson42.12-1 ii libmm-glib01.10.0-1 ii libndp01.6-1+b1 ii libnewt0.520.52.20-8 ii libnm0 1.14.4-4 ii libpam-systemd 240-5 ii libpolkit-agent-1-00.105-25 ii libpolkit-gobject-1-0 0.105-25 ii libpsl50.20.2-2 ii libreadline7 7.0-5 ii libselinux12.8-1+b1 ii libsystemd0240-5 ii libteamdctl0 1.28-1 ii libudev1 240-5 ii libuuid1 2.33.1-0.1 ii lsb-base 10.2018112800 ii policykit-10.105-25 ii udev 240-5 ii wpasupplicant 2:2.6-21 Versions of packages network-manager recommends: ii crda 3.18-1 ii dnsmasq-base [dnsmasq-base] 2.80-1 ii iptables 1.8.2-3 ii isc-dhcp-client 4.4.1-2 ii modemmanager 1.10.0-1 ii ppp 2.4.7-2+4 Versions of packages network-manager suggests: pn libteam-utils -- Configuration Files: /etc/NetworkManager/NetworkManager.conf changed: [main] plugins=ifupdown,keyfile [ifupdown] managed=true -- no debconf information ___ Pkg-utopia-maintainers mailing list Pkg-utopia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
[Pkg-utopia-maintainers] Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity
Package: network-manager
Version: 1.14.4-4
Severity: normal
Dear Maintainer,
I've noticed network manager is consuming most of the cpu time on my
system. It seems to be caused by the connectivity checking code. The
symptoms are:
1. ltrace shows this repeating on and on:
exe->epoll_wait(15, 0xbfb0bba0, 1, 0)
= 0
exe->clock_gettime(0, 0xbfb0bb54, 1, 15)
= 0
exe->clock_gettime(1, 0xbfb0bb54, 1, 15)
= 0
exe->clock_gettime(7, 0xbfb0bb54, 1, 15)
= 0
exe->g_object_ref(0x15c1b58, 0x15adf20, 0x15a84b0, 0xb7a5acc6)
= 0x15c1b58
exe->g_io_channel_unix_get_fd(0x1629fb0, 0x15adf20, 0x15a84b0, 0xb7a5acc6)
= 20
exe->curl_multi_socket_action(0x15c4900, 20, 2, 0xbfb0bd88)
= 0
exe->curl_multi_info_read(0x15c4900, 0xbfb0bd80, 2, 0xbfb0bd88)
= 0
exe->g_object_ref(0x15c1b58, 0x1612440, 0x1640dc0, 0xb7a5acc6)
= 0x15c1b58
exe->g_io_channel_unix_get_fd(0x15e32b0, 0x1612440, 0x1640dc0, 0xb7a5acc6)
= 22
exe->curl_multi_socket_action(0x15c4900, 22, 2, 0xbfb0bd88)
= 0
exe->curl_multi_info_read(0x15c4900, 0xbfb0bd80, 2, 0xbfb0bd88)
= 0
exe->g_object_ref(0x15c1b58, 0, 0x1654880, 0xb7a5acc6)
= 0x15c1b58
exe->g_io_channel_unix_get_fd(0x1627080, 0, 0x1654880, 0xb7a5acc6)
= 24
exe->curl_multi_socket_action(0x15c4900, 24, 2, 0xbfb0bd88)
= 0
exe->curl_multi_info_read(0x15c4900, 0xbfb0bd80, 2, 0xbfb0bd88)
= 0
2. strace only shows incrementing and decrementing an eventfd, no
network activity or something.
poll([{fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=8,
events=POLLIN|POLLPRI}, {fd=12, events=POLLIN}, {fd=13, events=POLLIN}, {fd=14,
events=POLLIN}, {fd=15, events=POLLIN}, {fd=16, events=POLLIN}, {fd=17,
events=POLLIN}, {fd=20, events=POLLOUT}, {fd=22, events=POLLOUT}, {fd=24,
events=POLLOUT}], 12, 0) = 4 ([{fd=3, revents=POLLIN}, {fd=20,
revents=POLLOUT}, {fd=22, revents=POLLOUT}, {fd=24, revents=POLLOUT}])
read(3, "\6\0\0\0\0\0\0\0", 16) = 8
epoll_wait(15, [], 1, 0)= 0
clock_gettime(CLOCK_BOOTTIME, {tv_sec=124345, tv_nsec=994550347}) = 0
write(3, "\1\0\0\0\0\0\0\0", 8) = 8
write(3, "\1\0\0\0\0\0\0\0", 8) = 8
write(3, "\1\0\0\0\0\0\0\0", 8) = 8
write(3, "\1\0\0\0\0\0\0\0", 8) = 8
write(3, "\1\0\0\0\0\0\0\0", 8) = 8
write(3, "\1\0\0\0\0\0\0\0", 8) = 8
Note: fd 22 is
NetworkMa 20906 root 20u IPv42035553 0t0 TCP
debian:45852->senfter.debian.org:http (ESTABLISHED)
However the event loop doesn't seem to touch the connection in any
way. fds 20 and 24 are similar connections.
Do you have any ideas about this? I'm not very knowledgeable about curl,
but surely it shouldn't hog the glib main loop like that?
Regards
Jiri Palecek
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 4.19.0-3-686-pae (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2), LANGUAGE=cs_CZ
(charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
