Hi Ivo,
* Ivo De Decker schrieb:
> As documented in /usr/share/doc/latencytop/README.Debian, latencytop needs a
> kernel with the CONFIG_LATENCYTOP option to run. Enabling this option on
> all (non-debug) kernels is not a good idea:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600935
Oh. Seems like I was mislead by the somewhat ambigously named kernel build
options (CONFIG_HAVE_LATENCYTOP_SUPPORT is set, while CONFIG_LATENCYTOP is
not):
# uname -r
3.2.0-4-amd64
# grep LATENCYTOP /boot/config-3.2.0-4-amd64
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
# CONFIG_LATENCYTOP is not set
> I'm lowering the severity of this bug, but I'm not closing it yet. Maybe the
> fact that Debian doesn't ship kernel with CONFIG_LATENCYTOP should be
> documented explicitly in README.Debian.
Alright :-) However, I suggest that latencytop should detect missing kernel
support and display a useful error message indicating that situation.
And that error message is already in latencytop.c:
»·file = fopen("/proc/latency_stats","r+");
»·if (!file) {
»·»·fprintf(stderr, "Please enable the CONFIG_LATENCYTOP configuration in
your kernel.\n");
»·»·fprintf(stderr, "Exiting...\n");
»·»·exit(EXIT_FAILURE);
»·}
So the real bug seems to be that that error message isn't really displayed. Or
it might be, as the terminal flashes for a split second, but I can't make out
if there's a message. (On an Ubuntu "Terminal", but I think this was the case
using a PuTTY on Windows 7, too, first time I tried to use latencytop on the
same wheezy VM. Logged in via SSH.)
# echo $TERM
xterm
Thanks,
Mike
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
