From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Jack Smith <smith.jack.sidman@googlemail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: wpa_supplicant and system tap
Date: Thu, 17 Feb 2011 16:25:21 +0100 [thread overview]
Message-ID: <20110217152520.GA2287@redhat.com> (raw)
In-Reply-To: <1297949294.3082.4.camel@DottleKnocker>
On Thu, Feb 17, 2011 at 02:28:13PM +0100, Jack Smith wrote:
> I am trying to understand why my Wireless network connection is so
> unstable.
>
> I was wondering if it would be worthwhile to explore what ipw2200 is
> doing by way of system tap.
I never find system-tap useful for debugging modules, adding printk
in the code, recompiling and reloading module is much faster/better
method for me instead of writing stap scripts.
> Is this a sensible approach ?
>
> If not, can you suggest a better one.
Many modules, including ipw2200, have "debug" option, using it is a good
idea when starting debugging. At some point, when more or less problem
is localized, adding custom printk's for getting more detailed
information is usually needed as well.
Stanislaw
prev parent reply other threads:[~2011-02-17 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 13:28 wpa_supplicant and system tap Jack Smith
2011-02-17 15:25 ` Stanislaw Gruszka [this message]
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=20110217152520.GA2287@redhat.com \
--to=sgruszka@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=smith.jack.sidman@googlemail.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).