From: Andi Kleen <andi@firstfloor.org>
To: Greg Huber <ghuber@vanteon.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Assistance debugging a Micrel network driver
Date: 29 Jun 2007 19:20:09 +0200 [thread overview]
Message-ID: <p73ejju4r06.fsf@bingen.suse.de> (raw)
In-Reply-To: <468527A2.40909@vanteon.com>
Greg Huber <ghuber@vanteon.com> writes:
>
> The upper layers obviously work so I'm sure it's something in my driver.
netstat -s output might give some clue. Most packet drop
points have a counter.
>
> I have turned on as much debugging in the kernel as I could find, but
> I get no messages. Could someone please let me know if
> there is additional debugging I should consider or if there is a
> dynamic way to turn on debugging in L2 and/or L3.
The usual is to just add printks to the kernel source code until you
find where the packet is dropped.
Or perhaps check in __kfree_skb if the skb is coming from your
driver and force a backtrace with show_stack().
-Andi
prev parent reply other threads:[~2007-06-29 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 15:39 Assistance debugging a Micrel network driver Greg Huber
2007-06-29 16:02 ` Jesper Juhl
2007-06-29 17:20 ` Andi Kleen [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=p73ejju4r06.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=ghuber@vanteon.com \
--cc=linux-kernel@vger.kernel.org \
/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