lscpu crashed with SIGFPE in read_topology()

Bug #1053539 reported by asiweb on 2012-09-20
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Fix Released
util-linux (Ubuntu)

Bug Description

when I run in the terminal lscpu gives me an error "floating point exception (`core 'generated)"

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: util-linux 2.20.1-5.1ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Thu Sep 20 19:44:38 2012
ExecutablePath: /usr/bin/lscpu
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120917)
ProcCmdline: lscpu
 PATH=(custom, no user)
Signal: 8
SourcePackage: util-linux
 ?? ()
 __libc_start_main () from /lib/x86_64-linux-gnu/
 ?? ()
 ?? ()
 ?? ()
Title: lscpu crashed with SIGFPE in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

asiweb (asiweb) wrote :

 read_topology (num=0, desc=0x7fff697ba460) at lscpu.c:658
 main (argc=<optimized out>, argv=<optimized out>) at lscpu.c:1146

Changed in util-linux (Ubuntu):
importance: Undecided → Medium
summary: - lscpu crashed with SIGFPE in __libc_start_main()
+ lscpu crashed with SIGFPE in read_topology()
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in util-linux (Ubuntu):
status: New → Confirmed
tags: added: raring
Dave Gilbert (ubuntu-treblig) wrote :

For anyone who can trigger this (doesn't happen for me); I'd be interested in the output of:

cat /proc/cpuinfo
lshw -c cpu
find /sys/devices/system/cpu
ulimit -a


Dave Gilbert (ubuntu-treblig) wrote :

Looking at the backtrace I can see:
 nnodes = 0, nodemaps = 0x0, nbooks = 0, bookmaps = 0x0, nsockets = 0, socketmaps = 0x0, ncores = 0, coremaps = 0x0, nthreads = 2, ncaches = 0, caches = 0x0

Why it thinks that ncores = 0 I can't tell however!

I can see however that current util-linux git has:

commit d4bfa64d44e0515c59e5274d2384dedd9f9d4cc8
Author: Karel Zak <email address hidden>
Date: Tue Nov 13 10:36:25 2012 +0100

    lscpu: make read_topology() more robust to avoid SIGFPE

which basically guards everything to make sure it's at least 1.

So I think we should just update our util-linux

information type: Private → Public
Changed in util-linux (Ubuntu):
status: Confirmed → Triaged
Changed in util-linux-ng:
importance: Unknown → Undecided
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.