netdev
[Top] [All Lists]

RE: Unable to handle kernel paging request at virtual address 04000460

To: <shemminger@xxxxxxxx>
Subject: RE: Unable to handle kernel paging request at virtual address 04000460
From: <raghunathan.venkatesan@xxxxxxxxx>
Date: Fri, 3 Jun 2005 08:28:34 +0530
Cc: <davem@xxxxxxxxxxxxx>, <linux-net@xxxxxxxxxxxxxxx>, <netdev@xxxxxxxxxxx>, <linux@xxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
Thread-index: AcVnmr7o+HCu/Cf9S06Mjf+yNyDZmwATUH0g
Thread-topic: Unable to handle kernel paging request at virtual address 04000460
Hi Stephen,
I appreciate you response. 
We'll get deeper into the problem after turning on these debugs.

Thanks,
Raghu


-----Original Message-----
From: Stephen Hemminger [mailto:shemminger@xxxxxxxx] 
Sent: Thursday, June 02, 2005 11:14 PM
To: Raghunathan Venkatesan (WT01 - EMBEDDED & PRODUCT ENGINEERING
SOLUTIONS)
Cc: davem@xxxxxxxxxxxxx; linux-net@xxxxxxxxxxxxxxx; netdev@xxxxxxxxxxx;
linux@xxxxxxxxxxxxx
Subject: Re: Unable to handle kernel paging request at virtual address
04000460

On Thu, 2 Jun 2005 09:20:21 +0530
<raghunathan.venkatesan@xxxxxxxxx> 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.


<Prev in Thread] Current Thread [Next in Thread>