atop unusable in Quantal: trap divide error

Bug #1098011 reported by Adam Porter
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
atop (Debian)
Fix Released
Unknown
atop (Ubuntu)
Triaged
High
Unassigned

Bug Description

After upgrading from Precise to Quantal, atop is completely unusable.

$ atop
$ dmesg | tail -2
[ 1292.322680] Process accounting paused
[ 1292.346494] atop[24981] trap divide error ip:407173 sp:7fffc9efb120 error:0 in atop[400000+25000]
$ atop
$ dmesg | tail -4
[ 1292.322680] Process accounting paused
[ 1292.346494] atop[24981] trap divide error ip:407173 sp:7fffc9efb120 error:0 in atop[400000+25000]
[ 1301.829009] Process accounting paused
[ 1301.852339] atop[24988] trap divide error ip:407173 sp:7fff9e886e50 error:0 in atop[400000+25000]

This bug report <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686329> says this can happen if /var/run is nearly full, but it is not on my system:

$ df /var/run
Filesystem Size Used Avail Use% Mounted on
tmpfs 791M 768K 791M 1% /run

I tried purging and reinstalling atop, but it made no difference.

atop has always worked just fine until I upgraded to Quantal.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: atop 1.26-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
Uname: Linux 3.5.0-21-generic x86_64
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
Date: Wed Jan 9 20:10:40 2013
InstallationDate: Installed on 2010-05-20 (965 days ago)
InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
MarkForUpload: True
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: atop
UpgradeStatus: Upgraded to quantal on 2013-01-09 (0 days ago)

Revision history for this message
Adam Porter (alphapapa) wrote :
Revision history for this message
Adam Porter (alphapapa) wrote :

This bug no longer occurs in Raring.

Revision history for this message
sz gy (gyszabolcs) wrote :

The bug is present in wily 15.10...

kernel: [187758.771068] traps: atop[11199] trap divide error ip:4073e6 sp:7ffbffffac20 error:0 in atop[400000+26000]

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

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

Changed in atop (Ubuntu):
status: New → Confirmed
Revision history for this message
Ariel Faigon (ariel.faigon) wrote :

Started to occur for me after upgrading from 12.04 to 16.04

atop is mostly usable, but I see these (once per day, one sec after midnight) in kern.log:

May 19 00:00:01 hostname kernel: [746105.037456] traps: atop[1943] trap divide error ip:4073c2 sp:7fff3b17e200 error:0 in atop[400000+26000]

May 20 00:00:01 hostname kernel: [832515.341713] traps: atop[19356] trap divide error ip:4073c2 sp:7ffee489c910 error:0 in atop[400000+26000]

Revision history for this message
Stefano Barbato (r-stefano) wrote :

Same for me on ubuntu 16.04:

2016-06-22T00:00:01.323439+00:00 ip-10-13-62-24 CRON[28725]: (root) CMD (invoke-rc.d atop _cron)

2016-06-22T00:00:01.973658+00:00 ip-10-13-62-24 kernel: [1071894.917868] traps: atop[28805] trap divide error ip:4073c2 sp:7ffe18bef8d0 error:0 in atop[400000+26000]

Changed in atop (Debian):
status: Unknown → Fix Released
Revision history for this message
Leon Keijser (errtu) wrote :

Which version fixes this? I'm currently on 16.04 using atop 1.26-2build1 and the bug is still present.

Jun 29 00:00:01 myhost kernel: [826159.413832] traps: atop[1812] trap divide error ip:4073c2 sp:7ffe3cd33530 error:0 in atop[400000+26000]

Vinson Lee (vlee)
tags: added: xenial
Luke Faraone (lfaraone)
Changed in atop (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → High
Revision history for this message
Remy van Elst (raymii) wrote :

Installing the 2.x release from 16.10 or higher fixes it in 16.04 for me: https://raymii.org/s/articles/atop_is_broken_on_Ubuntu_16.04.html

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.