Description of problem: Trying to start atop on old atom 270n netbook: sudo atop Version-Release number of selected component: atop-2.0.2-2.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: atop crash_function: __divdi3 executable: /usr/bin/atop kernel: 3.17.2-200.fc20.i686 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (3 frames) #0 __divdi3 #1 acctprocnt at acctproc.c:566 #2 engine at atop.c:837
Created attachment 959167 [details] File: backtrace
Created attachment 959168 [details] File: cgroup
Created attachment 959169 [details] File: core_backtrace
Created attachment 959170 [details] File: dso_list
Created attachment 959171 [details] File: environ
Created attachment 959172 [details] File: limits
Created attachment 959173 [details] File: maps
Created attachment 959174 [details] File: open_fds
Created attachment 959175 [details] File: proc_pid_status
Created attachment 959176 [details] File: var_log_messages
This is the same bug as in Fedora 21 and Rawhide and is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1147145 I have the same error on atop-2.0.2-4.fc21.x86_64 I suspect that the acctvers function is not working somehow. The read fails maybe? acctrecsz is not being set and is 0 causing a divide by 0 error.
The RPM on the maintainer's site: http://www.atoptool.nl/downloadatop.php works for me (it does mention fixes fo segfaults and floating point excepts). How can I help to get the updates into Fedora repos?
I do not really know hot to start a fedora update procedure, but I must say that I also did get and install the current atop from the developer's side and it has never ever failed me since... neither on old atom 32bit netbook nor on my other phenom-I (!) 64bit backup nas machine... So PLEASE just update in the package repos and all will be well!!
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.