netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: <raghunathan.venkatesan@wipro.com>
Cc: <davem@davemloft.net>, <linux-net@vger.kernel.org>,
	<netdev@oss.sgi.com>, <linux@der-keiler.de>
Subject: Re: Unable to handle kernel paging request at virtual address 04000460
Date: Thu, 2 Jun 2005 10:44:23 -0700	[thread overview]
Message-ID: <20050602104423.2c3825e5@dxpl.pdx.osdl.net> (raw)
In-Reply-To: <438662DA48DCAA41B1DF648BD4BD76C0E461B8@CHN-SNR-MBX01.wipro.com>

On Thu, 2 Jun 2005 09:20:21 +0530
<raghunathan.venkatesan@wipro.com> wrote:

> Hi David,
> I understand that the linux community may not be able to debug it for
> me. All I require is if people have seen similar problems (the problems
> we face are w.r.t to kfree_skb and skb_drop_fraglist crashing due to
> some reason, which could be a Memory Management issue or some thing we
> are not aware of), then let us know the patches, so that we can try them
> out here.

Turn on Debug memory allocations, spinlock debugging, sleep-inside-spinlock
checking, and preempt, it will help your debugging.  If you are not building
your own kernel from source learn how.

You are probably freeing memory twice, or not doing ref counting properly
or other locking issues.  Since it is your code, good luck debugging it,
if you want the community help it needs to be open source code that
is available for download or be in the kernel.org kernel.

  reply	other threads:[~2005-06-02 17:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-02  3:50 Unable to handle kernel paging request at virtual address 04000460 raghunathan.venkatesan
2005-06-02 17:44 ` Stephen Hemminger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-03  2:58 raghunathan.venkatesan
2005-06-01 11:31 raghunathan.venkatesan
2005-06-01 18:54 ` David S. Miller

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=20050602104423.2c3825e5@dxpl.pdx.osdl.net \
    --to=shemminger@osdl.org \
    --cc=davem@davemloft.net \
    --cc=linux-net@vger.kernel.org \
    --cc=linux@der-keiler.de \
    --cc=netdev@oss.sgi.com \
    --cc=raghunathan.venkatesan@wipro.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).