ovs-vswitchd crashed with SIGSEGV

Bug #1306457 reported by Dominique Jullier
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openvswitch (Ubuntu)
Expired
Low
Unassigned

Bug Description

At almost every start of the system, the Ubuntu bug reporting tool detects this crash. It seems, that although it crashes at the beginning, it gets started anyway and the openvswitch works without problems later on.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: openvswitch-switch 2.0.1+git20140120-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Apr 10 13:07:37 2014
ExecutablePath: /usr/sbin/ovs-vswitchd
InstallationDate: Installed on 2014-04-08 (2 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Daily amd64 (20140408)
ProcCmdline: ovs-vswitchd unix:/var/run/openvswitch/db.sock -vconsole:emer -vsyslog:err -vfile:info --mlockall --no-chdir --log-file=/var/log/openvswitch/ovs-vswitchd.log --pidfile=/var/run/openvswitch/ovs-vswitchd.pid --detach --monitor
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x457d10: mov 0x8(%rdi),%rax
 PC (0x00457d10) ok
 source "0x8(%rdi)" (0x00000179) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: openvswitch
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: ovs-vswitchd crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: libvirtd

Revision history for this message
Dominique Jullier (dominique-jullier) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 netdev_get_etheraddr (netdev=0x171, mac=0xbfdab6 "") at ../lib/netdev.c:627
 send_bpdu_cb (pkt=pkt@entry=0xbc1050, port_num=1, ofproto_=ofproto_@entry=0xba7eb0) at ../ofproto/ofproto-dpif.c:2021
 stp_send_bpdu (p=p@entry=0xbadb68, bpdu=0x7fff3e008000, bpdu_size=bpdu_size@entry=35) at ../lib/stp.c:1548
 stp_transmit_config (p=p@entry=0xbadb68) at ../lib/stp.c:1046
 stp_config_bpdu_generation (stp=stp@entry=0xbada80) at ../lib/stp.c:1106

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 openvswitch (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
James Page (james-page)
information type: Private → Public
Revision history for this message
James Page (james-page) wrote :

Hi Dominique

This bug has been around for a while; I've not seen or been able to reproduce this problem - do you still see this issue?

Marking 'Incomplete' - if you are still having this problem with the latest ovs packages for your installation, please set back to New with an appropriate comment.

Thanks

Changed in openvswitch (Ubuntu):
status: New → Incomplete
importance: Medium → Low
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in openvswitch (Ubuntu):
status: Incomplete → Expired
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.