Public bug reported:
1. start top in a session
2. press '1' to show the CPUs individually
3. in a separate (root) session, shut down a cpu like this:
# echo 0 > /sys/devices/system/cpu/cpu2/online
4. top will exit with a message like this:
top: failed /proc/stat read
Related: when reactivating a cpu, top will only continue to show the
first N-1 cpus in its display.
The workaround for people who want to keep an active system monitor up, can do:
$ while true; do top; done
cpus_refresh() assumes that Cpu_tot never changes; it reads that many
cpu* entries from /proc/stat, incorrectly interpreting the 'intr' line
as a failed cpu line read.
** Affects: procps (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1399861
Title:
top errors out when a cpu is taken offline
Status in procps package in Ubuntu:
New
Bug description:
1. start top in a session
2. press '1' to show the CPUs individually
3. in a separate (root) session, shut down a cpu like this:
# echo 0 > /sys/devices/system/cpu/cpu2/online
4. top will exit with a message like this:
top: failed /proc/stat read
Related: when reactivating a cpu, top will only continue to show the
first N-1 cpus in its display.
The workaround for people who want to keep an active system monitor up, can
do:
$ while true; do top; done
cpus_refresh() assumes that Cpu_tot never changes; it reads that many
cpu* entries from /proc/stat, incorrectly interpreting the 'intr' line
as a failed cpu line read.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1399861/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
