NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates()

Bug #1622571 reported by twicejr
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

it appeared right after boot, but I do use a 4.8 kernel..
Linux jaypc 4.8.0-040800rc1-generic #201608072231 SMP Mon Aug 8 02:33:57 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: network-manager 1.2.2-0ubuntu8
Uname: Linux 4.6.0-040600-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Thu Sep 8 09:01:03 2016
ExecutablePath: /usr/sbin/NetworkManager
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-04-04 (160 days ago)
InstallationMedia: It
IpRoute:
 default via 192.168.11.1 dev enp3s0 proto static metric 100
 169.254.0.0/16 dev enp3s0 scope link metric 1000
 192.168.11.0/24 dev enp3s0 proto kernel scope link src 192.168.11.20 metric 100
IwConfig:
 lo no wireless extensions.

 enp3s0 no wireless extensions.
NetworkManager.conf:
 [main]
 plugins=ifupdown,keyfile,ofono

 [ifupdown]
 managed=false
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcCmdline: /usr/sbin/NetworkManager --no-daemon
ProcEnviron:
 LANG=nl_NL.UTF-8
 PATH=(custom, no user)
RfKill: Can't open RFKILL control device: No such file or directory
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 nm_dns_manager_end_updates ()
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic_va () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates()
UpgradeStatus: Upgraded to yakkety on 2016-05-20 (115 days ago)
UserGroups:

nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH
 Wired connection 1 83b55d9f-56b0-3de7-8781-b60ac02d32da 802-3-ethernet 1473679209 ma 12 sep 2016 13:20:09 CEST yes 4294966297 no /org/freedesktop/NetworkManager/Settings/1 yes enp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0
 NETGEAR74 2508a31f-ca9b-47cc-a9e3-8f5be4686282 802-11-wireless 1463994465 ma 23 mei 2016 11:07:45 CEST yes 0 no /org/freedesktop/NetworkManager/Settings/0 no -- -- --
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 enp3s0 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 83b55d9f-56b0-3de7-8781-b60ac02d32da /org/freedesktop/NetworkManager/ActiveConnection/0
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- --
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.2.2 connected started full enabled enabled enabled enabled enabled

Revision history for this message
twicejr (twicejr) wrote :
information type: Private → Public
Revision history for this message
twicejr (twicejr) wrote :

I use NO wifi, by the way.

Revision history for this message
twicejr (twicejr) wrote :

Not even an adapter present in this pc.

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 nm_dns_manager_end_updates (self=0x55b4969d70a0, func=0x55b4953465e0 <__func__.34005> "device_ip4_config_changed") at dns-manager/nm-dns-manager.c:1364
 ffi_call_unix64 () from /tmp/apport_sandbox_8HAtJC/usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /tmp/apport_sandbox_8HAtJC/usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic_va () from /tmp/apport_sandbox_8HAtJC/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 _g_closure_invoke_va () from /tmp/apport_sandbox_8HAtJC/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in network-manager (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Travis Downs (travis-downs) wrote :

I believe I'm also having this problem. I've uploaded the whoopsie dump with apport but I can't see where it is being tracked (see http://askubuntu.com/questions/900191/where-do-i-look-to-see-if-my-whoopsie-is-being-tracked).

The stack looks the same:

SegvAnalysis:
 Segfault happened at: 0x7fc79f90e830 <__libc_start_main+240>: mov %eax,%edi
 PC (0x7fc79f90e830) ok
 source "%eax" ok
 destination "%edi" ok
 SP (0x7ffc12fba2c0) ok
 Reason could not be automatically determined.
SourcePackage: network-manager
Stacktrace:
 #0 0x000000000048cc66 in nm_dns_manager_end_updates ()
 #1 0x00007fc79d566e40 in ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 #2 0x00007fc79d5668ab in ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 #3 0x00007fc7a01f5cf5 in g_cclosure_marshal_generic_va () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 #4 0x00007fc7a01f51d4 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 #5 0x00007fc7a020f9a6 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 #6 0x00007fc7a021008f in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0

This started happening when I commented out the dns=dnsmasq line in my NetworkManager.conf and indeed the crash happens in DNS related code.

The often occurs after resuming from suspend, but not always - it may also just occur while using the host.

Here's a link to the whoopise upload - I don't have perms to see it, but perhaps someone who does can associate it with this bug?

https://errors.ubuntu.com/oops/f3ce1fb0-1957-11e7-968c-fa163e8d4bab

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.