MASTER NetworkManager crashes during intrepid->jaunty upgrade

Bug #349060 reported by Scott Kitterman
58
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

Crashed during (at the end, just before reboot) of an Kubuntu 8.10 to Jaunty upgrade.

ProblemType: Crash
Architecture: i386
Disassembly: 0xb7ee8298:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
Package: network-manager 0.7.1~rc3.1.git4cf2da146-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/NetworkManager
ProcEnviron: PATH=(custom, no user)
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
ThreadStacktrace:

Title: NetworkManager crashed with SIGSEGV
Uname: Linux 2.6.27-11-generic i686
UserGroups:

Revision history for this message
Scott Kitterman (kitterman) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
get_active_ap (self=0x91faea8, ignore_ap=0x8066d19,
cleanup_association_attempt (self=0xb7f16ff4,
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Alexander Sack (asac) wrote :

do you have any upgrade logs that could show what happened at the time you got the crash?

summary: - NetworkManager crashed with SIGSEGV
+ MASTER NetworkManager crashes during intrepid->jaunty upgrade
visibility: private → public
Revision history for this message
Scott Kitterman (kitterman) wrote : Re: [Bug 349060] Re: MASTER NetworkManager crashes during intrepid->jaunty upgrade

The upgrade logs don't show any errors. I'm pretty sure apport collected
everything useful.

tags: added: iso-testing
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

What seems to me is like this crash was caused by HAL being successively restarted, and NM's signals firing too slowly for the HAL state (with probably missing sanity checks along the way).

Mar 26 11:58:28 scott-laptop NetworkManager: <info> HAL disappeared
Mar 26 11:58:30 scott-laptop NetworkManager: <info> HAL re-appeared
Mar 26 11:58:30 scott-laptop NetworkManager: <info> (eth0): now unmanaged
Mar 26 11:58:30 scott-laptop NetworkManager: <info> (eth0): device state change: 2 -> 1
Mar 26 11:58:30 scott-laptop NetworkManager: <info> (eth0): cleaning up...
Mar 26 11:58:30 scott-laptop NetworkManager: <info> (eth0): taking down device.
Mar 26 11:58:30 scott-laptop NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Mar 26 12:02:19 scott-laptop NetworkManager: <info> HAL disappeared
Mar 26 12:02:21 scott-laptop NetworkManager: <info> HAL re-appeared
Mar 26 12:02:21 scott-laptop NetworkManager: nm_device_get_managed: assertion `NM_IS_DEVICE (device)' failed
Mar 26 12:02:24 scott-laptop NetworkManager: <info> HAL disappeared

Fixing this however is going to be impractical since there is no longer archive packages for these releases -- closing as Won't Fix for lack of a better idea.

Changed in network-manager (Ubuntu):
status: New → Won't Fix
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.