Package: itop
Version: 0.1-4
Followup-For: Bug #443798

Dear Maintainer,

Just confirming that itop is still broken for amd64 with multiple
cores. For example, on an Intel i5 processor with four cores, I get
output that looks like this:

INT                NAME          RATE             MAX
 19 [   0          0   ]     6 Ints/s     (max:     6)
 40 [   0          0  H]   514 Ints/s     (max:   514)
 46 [   0          0   ]   210 Ints/s     (max:   211)

When it should look more like:

INT                NAME          RATE             MAX
 19 [ IO-APIC-fasteoi  ]     6 Ints/s     (max:     6)
 40 [ HPET_MSI-edge    ]   514 Ints/s     (max:   514)
 46 [ PCI_MSI-edge     ]   210 Ints/s     (max:   211)


This bug seems to be because there are optional additional columns for
each CPU in /proc/interrupts. For example:

           CPU0       CPU1       CPU2       CPU3       
  0:         42          0          0          0   IO-APIC-edge      timer
  1:          0          0          0          2   IO-APIC-edge      i8042
....


Unfortunately, itop parses the file using fixed column numbers. Since
tracking down unusually high interrupts usually does not require
knowing which CPU is being interrupted, one reasonable solution for
this bug would be to sum each interrupt count across all CPUs.

---Ben


-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages itop depends on:
ii  libc6  2.19-7

itop recommends no packages.

itop suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to