connmand crashed with SIGSEGV in g_timeout_dispatch()

Bug #672742 reported by Kalle Valo
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Connection Manager
Triaged
Medium
Unassigned

Bug Description

I was using 'cmcc offlinemode' command because ath9k was giving me troubles again and I had to put wlan0 down somehow.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: connman 0.62-0ubuntu1~ind3+r2799+201011041546
Uname: Linux 2.6.36-wl+ x86_64
Architecture: amd64
CrashCounter: 1
CrashDB: connman
Date: Mon Nov 8 16:21:05 2010
ExecutablePath: /usr/sbin/connmand
IpRoute:
 192.168.1.1 dev wlan0 scope link
 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.224
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
 default via 192.168.1.1 dev wlan0
MachineType: SAMSUNG ELECTRONICS CO., LTD. X120/X170
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.36-wl+ root=UUID=b345284f-a700-4b71-a796-254f8e2835e8 ro quiet splash security=
ProcCmdline: connmand -c -d -I wlan1 -P wifi_legacy
ProcEnviron: PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7fe261aa736a: mov 0x10(%rax),%rbx
 PC (0x7fe261aa736a) ok
 source "0x10(%rax)" (0x000000a0) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: connman
StacktraceTop:
 ?? ()
 g_timeout_dispatch (source=0x7fe2636bf870, callback=0, user_data=0x4) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:3585
 g_main_dispatch (context=0x7fe2636650e0) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2149
 g_main_context_dispatch (context=0x7fe2636650e0) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2702
 g_main_context_iterate (context=0x7fe2636650e0, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2780
ThirdParty: True
Title: connmand crashed with SIGSEGV in g_timeout_dispatch()
UserGroups:

dmi.bios.date: 10/13/2009
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 04CX.M005.20091013.KSY
dmi.board.name: X120/X170
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04CX.M005.20091013.KSY:bd10/13/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnX120/X170:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnX120/X170:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: X120/X170
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Kalle Valo (kvalo) wrote :
Revision history for this message
Kalle Valo (kvalo) wrote :

Most probably this is due to 04-wifi-add-a-disconnected-timer.patch to the new wifi plugin.

Changed in connman:
importance: Undecided → Medium
status: New → Triaged
visibility: private → public
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.