> it is very hard to imagine the scenario which can lead to this...
> I will try your suggestion..
Perhaps a problem with the csum assembler implementations? Which cpu
type do you optimize for, and which cpu is installed?
Btw, are you overclocking anything?
--
Manfred
-
To unsubscribe
> What you can try is to turn on slab debugging. Set the FORCED_DEBUG
> define in mm/slab.c to one and recompile. Does it change any pattern
> when you dump the data in the skbs or pings?
> If yes someone is playing with already freed packets.
I think the dump that i got suggests something
On Wed, Apr 11, 2001 at 08:15:49PM +0300, [EMAIL PROTECTED] wrote:
> And as a I said earlier, only ping packets with size within certain range
> create this problem..Something is terribly wrong here!! But as I am not
> a Linux mm guru, i can't tell what is wrong here!
What you can try is to
On Wed, Apr 11, 2001 at 01:47:18PM -0400, Bart Trojanowski wrote:
>
> Coudl the problem be in the NIC driver not in the alloc_skb? I have used
> both 2.4.{1,3} for some time and never seen this corruption. I use ping
> -f with various packet sizes for stress testing my IPSec boxes... these do
> Coudl the problem be in the NIC driver not in the alloc_skb?
No, i don't think so...i got the dump of the packet at the local_out and
post routing hooks& found it in bad shape there. Here it is what it
looks like:
45 0 0 80 0 0 40 0 ff 1 2d f8 c0 a8 66 16 c0 a8 66 1d 0 0 e4 48 11 d 0 0
Coudl the problem be in the NIC driver not in the alloc_skb? I have used
both 2.4.{1,3} for some time and never seen this corruption. I use ping
-f with various packet sizes for stress testing my IPSec boxes... these do
quite a bit of extra skb creation as an IPSec header sometimes does not
> -Original Message-
> From: ext Dave Airlie [mailto:[EMAIL PROTECTED]]
> Sent: 11. April 2001 20:20
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: RE: skb allocation problems (More Brain dam
What compiler are you using to compile the kernel?
Dave.
On Wed, 11 Apr 2001 [EMAIL PROTECTED] wrote:
> > Well, I don't know then. You have to debug it. It's probably
> > something stupid
> > (if fundamental services like alloc_skb/kfree_skb were
> > completely buggy
> > someone surely would
> Well, I don't know then. You have to debug it. It's probably
> something stupid
> (if fundamental services like alloc_skb/kfree_skb were
> completely buggy
> someone surely would have noticed earlier)
yep, at first i thought it was because of sume stupidity in my module...but
now it seems
What compiler are you using to compile the kernel?
Dave.
On Wed, 11 Apr 2001 [EMAIL PROTECTED] wrote:
Well, I don't know then. You have to debug it. It's probably
something stupid
(if fundamental services like alloc_skb/kfree_skb were
completely buggy
someone surely would have
-Original Message-
From: ext Dave Airlie [mailto:[EMAIL PROTECTED]]
Sent: 11. April 2001 20:20
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: RE: skb allocation problems (More Brain damage!)
What compiler
Coudl the problem be in the NIC driver not in the alloc_skb? I have used
both 2.4.{1,3} for some time and never seen this corruption. I use ping
-f with various packet sizes for stress testing my IPSec boxes... these do
quite a bit of extra skb creation as an IPSec header sometimes does not
Coudl the problem be in the NIC driver not in the alloc_skb?
No, i don't think so...i got the dump of the packet at the local_out and
post routing hooks found it in bad shape there. Here it is what it
looks like:
45 0 0 80 0 0 40 0 ff 1 2d f8 c0 a8 66 16 c0 a8 66 1d 0 0 e4 48 11 d 0 0 14
On Wed, Apr 11, 2001 at 01:47:18PM -0400, Bart Trojanowski wrote:
Coudl the problem be in the NIC driver not in the alloc_skb? I have used
both 2.4.{1,3} for some time and never seen this corruption. I use ping
-f with various packet sizes for stress testing my IPSec boxes... these do
On Wed, Apr 11, 2001 at 08:15:49PM +0300, [EMAIL PROTECTED] wrote:
And as a I said earlier, only ping packets with size within certain range
create this problem..Something is terribly wrong here!! But as I am not
a Linux mm guru, i can't tell what is wrong here!
What you can try is to
it is very hard to imagine the scenario which can lead to this...
I will try your suggestion..
Perhaps a problem with the csum assembler implementations? Which cpu
type do you optimize for, and which cpu is installed?
Btw, are you overclocking anything?
--
Manfred
-
To unsubscribe
16 matches
Mail list logo
