irqbalance crashed with SIGSEGV in __libc_start_main()

Bug #1303067 reported by majo dom
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
irqbalance (Ubuntu)
New
Undecided
Unassigned

Bug Description

On Ubuntu Gnome 14.04 while using Darktable, this error showed while I was exporting a RAW file to JPG file on disk.
uname -a
Linux ubuntu 3.13.0-22-generic #44-Ubuntu SMP Wed Apr 2 20:05:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: irqbalance 1.0.6-2
ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
Uname: Linux 3.13.0-22-generic x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
Date: Sat Apr 5 16:58:51 2014
ExecutablePath: /usr/sbin/irqbalance
InstallationDate: Installed on 2014-04-05 (0 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404)
ProcCmdline: /usr/sbin/irqbalance
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x405db6: cmpl $0xffffffff,0x14(%rsi)
 PC (0x00405db6) ok
 source "$0xffffffff" ok
 destination "0x14(%rsi)" (0x2030203020302044) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: irqbalance
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main (main=0x401a20, argc=1, argv=0x7fff6ab71348, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff6ab71338) at libc-start.c:287
Title: irqbalance crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
majo dom (majo-dom) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1183374, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
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.