From: Oliver Hartkopp <oliver@hartkopp.net>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: netdev@vger.kernel.org
Subject: Re: dropwatch for network drop monitor
Date: Fri, 17 Apr 2009 16:16:10 +0200 [thread overview]
Message-ID: <49E88F2A.4010301@hartkopp.net> (raw)
In-Reply-To: <20090417132848.GA2723@hmsreliant.think-freely.org>
Hi Neil,
>> Initalizing kallsyms db
>> dropwatch> start
>> Enabling monitoring...
>> Waiting for activation ack....
>> Waiting for activation ack....
>> Waiting for activation ack....
>> Waiting for activation ack....
>> Waiting for activation ack....
>> Waiting for activation ack....
>> Failed activation request, error: Operation now in progress
>> Shutting down ...
>> vwagwolkf320:/home/hartko/dropwatch/src#
Indeed i only get this the second time.
The first time i get
hartko@vwagwolkf320:~/dropwatch/src$ ./dropwatch
Initalizing kallsyms db
dropwatch> start
Enabling monitoring...
Kernel monitoring activated.
Issue Ctrl-C to stop monitoring
But Ctrl-C does not work. I only get 100% CPU load on the CPU executing dropwatch.
After killing the process, i get the above originally described behaviour.
>>
>> And in my kernel log i get at the same time:
>> [ 7070.568482] netlink: 60 bytes leftover after parsing attributes.
And this comes every time, i invoke dropwatch.
I'm running a debian system here on a Dell 830 Laptop with Core2Duo and the
latest linux-2.6 git
Regards,
Oliver
ps. Do i need to be root to run dropwatch?
next prev parent reply other threads:[~2009-04-17 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 12:57 dropwatch for network drop monitor Oliver Hartkopp
2009-04-17 13:28 ` Neil Horman
2009-04-17 14:16 ` Oliver Hartkopp [this message]
2009-04-17 14:30 ` Neil Horman
2009-04-17 17:22 ` Neil Horman
2009-04-17 18:13 ` Oliver Hartkopp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49E88F2A.4010301@hartkopp.net \
--to=oliver@hartkopp.net \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).