NetworkManager crashed with SIGSEGV in nm_dhcp_client_start_ip6()

Bug #864795 reported by Caspar Adriani
80
This bug affects 10 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

My wireless connection keeps dropping. Normally it reconnects without a warning but hopefully this is related

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: network-manager 0.9.1.90-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Sun Oct 2 20:45:33 2011
ExecutablePath: /usr/sbin/NetworkManager
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
IpRoute:
 default via 192.168.1.1 dev wlan0 proto static
 169.254.0.0/16 dev wlan0 scope link metric 1000
 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.100 metric 2
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
 WimaxEnabled=true
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7f985f806996: movdqu (%rdi),%xmm1
 PC (0x7f985f806996) ok
 source "(%rdi)" (0x5800ec30) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 nm_dhcp_client_start_ip6 ()
 ?? ()
 nm_dhcp_manager_start_ip6 ()
Title: NetworkManager crashed with SIGSEGV in nm_dhcp_client_start_ip6()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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

StacktraceTop:
 __strcmp_sse42 () at ../sysdeps/x86_64/multiarch/strcmp.S:259
 dhclient_start (client=<optimized out>, mode_opt=0x4ad41a "-S", release=0) at nm-dhcp-dhclient.c:647
 nm_dhcp_client_start_ip6 (self=0x7f1480, s_ip6=0x823830, dhcp_anycast_addr=0x0, hostname=0x0, info_only=1) at nm-dhcp-client.c:493
 client_start (self=0x821de0, iface=<optimized out>, uuid=<optimized out>, ipv6=1, s_ip4=0x0, s_ip6=0x823830, timeout=0, dhcp_anycast_addr=0x0, hostname=0x0, info_only=1) at nm-dhcp-manager.c:446
 nm_dhcp_manager_start_ip6 (self=<optimized out>, iface=<optimized out>, uuid=<optimized out>, s_ip6=<optimized out>, timeout=<optimized out>, dhcp_anycast_addr=<optimized out>, info_only=1) at nm-dhcp-manager.c:519

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.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
Martin Pitt (pitti)
visibility: private → public
tags: added: precise
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.