pybootchartgui crashed with ZeroDivisionError in _parse_proc_disk_stat_log()

Bug #506910 reported by Oliver Grawert
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bootchart (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: pybootchartgui

on an armel imx51 system (licid alpha2) i'm greeted with an apport notification from pybootchartgui.

ProblemType: Crash
Architecture: armel
Date: Wed Jan 13 11:56:57 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/pybootchartgui
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha armel+imx51 (20100112.2)
InterpreterPath: /usr/bin/python2.6
Package: pybootchartgui 0+r139-2
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/bootchart --format=png --crop-after=gnome-panel --output=/var/log/bootchart /var/log/bootchart/hostname-lucid-20100113-4.tgz
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.31-602.4-imx51
PythonArgs: ['/usr/bin/bootchart', '--format=png', '--crop-after=gnome-panel', '--output=/var/log/bootchart', '/var/log/bootchart/hostname-lucid-20100113-4.tgz']
SourcePackage: pybootchartgui
Tags: lucid
Title: pybootchartgui crashed with ZeroDivisionError in _parse_proc_disk_stat_log()
Uname: Linux 2.6.31-602-imx51 armv7l
UserGroups:

Related branches

Revision history for this message
Oliver Grawert (ogra) wrote :
Changed in pybootchartgui (Ubuntu):
importance: Undecided → Medium
tags: removed: need-duplicate-check
tags: added: iso-testing
Revision history for this message
Paul Larson (pwlars) wrote :

Seems to be reading numCpu incorrectly and dividing by 0

visibility: private → public
Changed in pybootchartgui (Ubuntu):
status: New → Triaged
Revision history for this message
Anders Norgaard (anders-norgaard) wrote :

Hi,

Can you upload the

/var/log/bootchart/$hostname-lucid-$date.tgz

that causes the crash? Then I'll have a look.

Best
Anders

Revision history for this message
Paul Larson (pwlars) wrote :
Revision history for this message
Anders Norgaard (anders-norgaard) wrote :

Ah, yes. The cpu information seems to be missing. This is what the "header" file looks like in the .tgz

version = 0.90.2-5
title = Boot chart for b3 (Wed Jan 13 12:09:03 CST 2010)
system.uname = Linux 2.6.31-602-imx51 #4-Ubuntu Mon Jan 11 17:05:57 UTC 2010 armv7l
system.release = Ubuntu lucid (development branch)
system.cpu = (0)
system.kernel.options = root=UUID=d7b8167d-555b-45ba-88cc-94b8b187cda8 ro quiet splash

A quick workaround in pybootchartgui is to simply delete the " / numCpu" in

  File "/home/anders/devel/pybootchartgui/pybootchartgui/parsing.py", line 161, in _parse_proc_disk_stat_log
    util = float( sums[2] ) / 10 / interval / numCpu

(the cpu usage graph is relative anyway)

Best
Anders

Revision history for this message
Anders Norgaard (anders-norgaard) wrote :

When I look in the bootchart-gather.sh file in the bootchart package the line that outputs the "header" file is

echo "system.cpu = $(grep '^model name' /proc/cpuinfo)"\
         "($(grep -c '^model name' /proc/cpuinfo))"

How does that match the output on you arm machine? What does /proc/cpuinfo show?

Revision history for this message
Paul Larson (pwlars) wrote :

Attaching cpuinfo

Revision history for this message
Paul Larson (pwlars) wrote :

Tested on armel, it now gathers correct information for the number of processors.

affects: pybootchartgui (Ubuntu) → bootchart (Ubuntu)
Revision history for this message
Paul Larson (pwlars) wrote :

updated debdiff including Oliver's suggestion to cover arm* instead of just armv7

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bootchart - 0.90.2-6

---------------
bootchart (0.90.2-6) lucid; urgency=low

  * Get correct cpu count on armel (LP: #506910).
 -- Paul Larson <email address hidden> Thu, 04 Feb 2010 17:53:09 -0800

Changed in bootchart (Ubuntu):
status: Triaged → Fix Released
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.