Hello

This is my first question to forum!!

we have encountered a problem with top command running on Linux.

please find the below output :

top - 04:37:54 up 10 days, 12:49, 1 user, load average: 0.20, 0.17, 0.10
Tasks: 690 total, 1 running, 689 sleeping, 0 stopped, 0 zombie
Cpu0 :-361980760699577565184.0%us,-361980760699577565184.0%sy,-1956022565642342
Cpu1 :-129.5%us,-67.6%sy,-67.6%ni, 0.0%id,-69.9%wa,-40.5%hi,-40.5%si,-59.8%st
Cpu2 :-448171072580659183616.0%us,-397927367025342021632.0%sy,-2598415664646748
Cpu3 :-40.1%us,-40.1%sy,-25.6%ni, 0.0%id,-80.1%wa,-40.1%hi,-40.1%si,-42.5%st
Cpu4 :-37.6%us,-78.7%sy,-37.9%ni, 0.0%id,-91.7%wa,-37.6%hi,-128.1%si,-88.3%st

Can someone tell me under which condition the top command would return negative values ?
Is there a known bug w.r.t top command ? if yes do we have patches ?

thanks.

Which distro are you using?
top should show positive values.

Looks possibly like a sign extend or variable size problem. Such as 64-bit program run on a 32-bit machine.

What distribution and what version of it are you using?

What are your machine specs?

What is the version of top?

You appear to have a 5-CPU machine.

procps version 3.2.7

any known bug is their top utility ?

Not really full answers here. The distribution and machine specs might have been helpful. Machine specs especially given my concerns about 64-bit and 32-bit discrepancies as well as JeremyBoden's observation:So,

2.6.32 kernel dates back to 2009, however that is the correct procps version to go with that kernel. And that version went EOL last year https://lkml.org/lkml/2016/3/12/78.

Either case, I believe 2.6 kernels came in two release forms, 64-bit or 32-bit. 64-bit on a 32-bit machine may be fine. And I'm thinking that 32-bit on a 64-bit machine may be fine, but there may be oddities which you're seeing here.

I do not see any top() bugs cited.

Once again, machine specs may help here. To really debug this better, someone would likely have to take the time to compile procps 3.2.7 from source, with the debug flag, and debug top() when you run it.