cpufreq-set crashed with SIGSEGV in __libc_start_main()

Bug #1202844 reported by george2706
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cpufrequtils (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

cpufreq-set -c non existent cpu crash instead error

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: cpufrequtils 008-1
Uname: Linux 3.11.0-rc1 x86_64
NonfreeKernelModules: parport_pc ppdev uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev joydev snd_seq_midi snd_seq_midi_event snd_rawmidi mei_me mei lpc_ich lp parport
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Fri Jul 19 00:03:36 2013
ExecutablePath: /usr/bin/cpufreq-set
InstallationDate: Installed on 2013-07-05 (13 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130626)
MarkForUpload: True
ProcCmdline: cpufreq-set -c 4 -r -u 1G
SegvAnalysis:
 Segfault happened at: 0x400e8b: mov (%rbx),%r12d
 PC (0x00400e8b) ok
 source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%r12d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cpufrequtils
StacktraceTop:
 ?? ()
 __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 ?? ()
 ?? ()
Title: cpufreq-set crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
george2706 (george-bungarzescu) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 __libc_start_main (main=0x400cd0, argc=6, ubp_av=0x7ffff578c9d8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffff578c9c8) at libc-start.c:260
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Connor Imes (ckimes)
information type: Private → Public
Changed in cpufrequtils (Ubuntu):
importance: Undecided → Low
status: New → Confirmed
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.