NetworkManager crashed with SIGSEGV in <unavailable> in ??()

Bug #1154083 reported by Steven Noonan on 2013-03-12
54
This bug affects 11 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Medium
Unassigned

Bug Description

I have a SIXXS IPv6 tunnel set up on my Linux router box, using radvd to announce the route to boxes on the LAN side. With the configuration for my wireless connection set to 'Automatic' for IPv6, network-manager will segfault, be restarted, try again, segfault, restart, try again, ad nauseum. By changing IPv6 to 'Ignore' I was able to get the connection to come up without network-manager segfaulting.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: network-manager 0.9.8.0-0ubuntu1
Uname: Linux 3.4.0-02535-ged4f6f6 armv7l
ApportVersion: 2.9.1-0ubuntu1
Architecture: armhf
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Tue Mar 12 06:22:08 2013
ExecutablePath: /usr/sbin/NetworkManager
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.106.1 dev mlan0 proto static
 169.254.0.0/16 dev mlan0 scope link metric 1000
 192.168.106.0/24 dev mlan0 proto kernel scope link src 192.168.106.42 metric 9
MarkForUpload: True
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
PciNetwork:

ProcCmdline: NetworkManager
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 nm_dhcp_dhclient_escape_duid ()
 ?? ()
 ?? ()
Title: NetworkManager crashed with SIGSEGV in nm_dhcp_dhclient_escape_duid()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
 Cactus Restaurant a1b5c702-2370-4f17-9d6e-278bab89141f 802-11-wireless 0 never yes no /org/freedesktop/NetworkManager/Settings/2
 I Like To Eat Waffles 5GHz 3f3dcf70-c86c-486e-b0d4-5ca7303be86c 802-11-wireless 1363094737 Tue 12 Mar 2013 06:25:37 PDT yes no /org/freedesktop/NetworkManager/Settings/1
 snoonan fe486a57-93ef-4e59-8983-aabf43321501 802-11-wireless 0 never yes no /org/freedesktop/NetworkManager/Settings/0
 Amazon a4aa96d3-4d2f-4c84-8057-6cc2fcd15ff2 802-11-wireless 1362705773 Thu 07 Mar 2013 17:22:53 PST yes no /org/freedesktop/NetworkManager/Settings/3
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 mlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.8.0 connected enabled enabled enabled enabled disabled

information type: Private → Public

Stacktrace:
 #0 <unavailable> in ?? ()
 PC not available
StacktraceSource: #0 <unavailable> in ?? ()
StacktraceTop: <unavailable> in ?? ()
ThreadStacktrace:
 PC not available
 warning: wrong size gregset struct in core file
 Quitting: PC register is not available

Changed in network-manager (Ubuntu):
importance: Undecided → Medium
summary: - NetworkManager crashed with SIGSEGV in nm_dhcp_dhclient_escape_duid()
+ NetworkManager crashed with SIGSEGV in <unavailable> in ??()
tags: removed: need-armhf-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in network-manager (Ubuntu):
status: New → Confirmed

Hi,

If you're still seeing this issue, could you please run NetworkManager in a debugger or using any such other trick to provide a stack trace for the crash? It seems like unfortunately the crash report system could not successfully get the crashes for your system; and as such I can't do much with this report due to insufficient information. Any other details you can add to this bug report would be much appreciated.

Thanks!

/ Matt

Changed in network-manager (Ubuntu):
status: Confirmed → Incomplete

I've stopped using IPv6 tunneling due to this kind of pain. Might as well wait for my ISP to get IPv6.

Launchpad Janitor (janitor) wrote :

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in network-manager (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers