KERNEL: assertion (!sk->sk_forward_alloc) failed

KERNEL: assertion (!sk->sk_forward_alloc) failed

[Yoseph Basri]

Hello kernel maillist,

I'm new member maillist.

Currently, I receive the warning log from my kernel.

Since update to
Linux  2.6.14.3 #1 SMP Fri Nov 25 20:20:05 SGT 2005 i686 GNU/Linux from 2.4,

I am getting the warning log:

kernel: KERNEL: assertion (!sk->sk_forward_alloc) failed at
net/core/stream.c (279)
kernel: KERNEL: assertion (!sk->sk_forward_alloc) failed at
net/ipv4/af_inet.c (148)

Any information about this issue, and how to solve this problem ?

Another server that i rolled back from 2.6.14 to 2.4 kernel and has no
warning again. is this bug from 2.6 kernel?

Thanks for your info.

YB

Re: KERNEL: assertion (!sk->sk_forward_alloc) failed

[Boris B. Zhmurov]

Hello, Yoseph Basri.

On 07.02.2006 12:46 you said the following:

> I am getting the warning log:
> 
> kernel: KERNEL: assertion (!sk->sk_forward_alloc) failed at
> net/core/stream.c (279)
> kernel: KERNEL: assertion (!sk->sk_forward_alloc) failed at
> net/ipv4/af_inet.c (148)


Do you have Intel Pro 1000 network card? Same here...


-- 
Boris B. Zhmurov
mailto: bb@kernelpanic.ru
"wget http://kernelpanic.ru/bb_public_key.pgp -O - | gpg --import"

Re: KERNEL: assertion (!sk->sk_forward_alloc) failed

[Yoseph Basri]

Hi Boris,

I think so, here is from the dmeg info:

Intel(R) PRO/1000 Network Driver - version 6.0.60-k2
Copyright (c) 1999-2005 Intel Corporation.
ACPI: PCI Interrupt 0000:06:08.0[A] -> GSI 29 (level, low) -> IRQ 16
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
ACPI: PCI Interrupt 0000:06:08.1[B] -> GSI 30 (level, low) -> IRQ 17
e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
e100: Intel(R) PRO/100 Network Driver, 3.4.14-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation

any info regarding this warning?

YB

On 2/7/06, Boris B. Zhmurov <bb@kernelpanic.ru> wrote:
> Hello, Yoseph Basri.
>
> On 07.02.2006 12:46 you said the following:
>
> > I am getting the warning log:
> >
> > kernel: KERNEL: assertion (!sk->sk_forward_alloc) failed at
> > net/core/stream.c (279)
> > kernel: KERNEL: assertion (!sk->sk_forward_alloc) failed at
> > net/ipv4/af_inet.c (148)
>
>
> Do you have Intel Pro 1000 network card? Same here...
>
>
> --
> Boris B. Zhmurov
> mailto: bb@kernelpanic.ru
> "wget http://kernelpanic.ru/bb_public_key.pgp -O - | gpg --import"
>
>

Re: KERNEL: assertion (!sk->sk_forward_alloc) failed

[Jesse Brandeburg]

this should be on netdev (cc'd), i included some of the thread here.

On 2/7/06, Yoseph Basri <yoseph.basri@gmail.com> wrote:
> Hello kernel maillist,
>
> I'm new member maillist.
>
> Currently, I receive the warning log from my kernel.
>
> Since update to
> Linux  2.6.14.3 #1 SMP Fri Nov 25 20:20:05 SGT 2005 i686 GNU/Linux from 2.4,
>
> I am getting the warning log:
>
> kernel: KERNEL: assertion (!sk->sk_forward_alloc) failed at
> net/core/stream.c (279)
> kernel: KERNEL: assertion (!sk->sk_forward_alloc) failed at
> net/ipv4/af_inet.c (148)
>
> Any information about this issue, and how to solve this problem ?
>
> Another server that i rolled back from 2.6.14 to 2.4 kernel and has no
> warning again. is this bug from 2.6 kernel?
>
> Thanks for your info.

On 2/7/06, Yoseph Basri <yoseph.basri@gmail.com> wrote:
> Hi Boris,
>
> I think so, here is from the dmeg info:
>
> Intel(R) PRO/1000 Network Driver - version 6.0.60-k2
> Copyright (c) 1999-2005 Intel Corporation.
> ACPI: PCI Interrupt 0000:06:08.0[A] -> GSI 29 (level, low) -> IRQ 16
> e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
> ACPI: PCI Interrupt 0000:06:08.1[B] -> GSI 30 (level, low) -> IRQ 17
> e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
> e100: Intel(R) PRO/100 Network Driver, 3.4.14-k2-NAPI
> e100: Copyright(c) 1999-2005 Intel Corporation
>
> any info regarding this warning?
>
> YB
>
> On 2/7/06, Boris B. Zhmurov <bb@kernelpanic.ru> wrote:
> > Hello, Yoseph Basri.
> >
> > On 07.02.2006 12:46 you said the following:
> >
> > > I am getting the warning log:
> > >
> > > kernel: KERNEL: assertion (!sk->sk_forward_alloc) failed at
> > > net/core/stream.c (279)
> > > kernel: KERNEL: assertion (!sk->sk_forward_alloc) failed at
> > > net/ipv4/af_inet.c (148)
> >
> >
> > Do you have Intel Pro 1000 network card? Same here...

whats the relevance of e1000?

I though Herbert had fixed these, and it looks like half the patches
got into 2.6.14.3, but not the fix to the fix committed on 9-6 (not in
2.6.14.* at all)

Jesse

Re: KERNEL: assertion (!sk->sk_forward_alloc) failed

[David S. Miller]

From: Jesse Brandeburg <jesse.brandeburg@gmail.com>
Date: Wed, 8 Feb 2006 12:07:14 -0800

> this should be on netdev (cc'd), i included some of the thread here.
 ...
> I though Herbert had fixed these, and it looks like half the patches
> got into 2.6.14.3, but not the fix to the fix committed on 9-6 (not in
> 2.6.14.* at all)

What are the changeset IDs so I can fix this?

Thanks.

Re: KERNEL: assertion (!sk->sk_forward_alloc) failed

[Jesse Brandeburg]

On 2/8/06, David S. Miller <davem@davemloft.net> wrote:
> From: Jesse Brandeburg <jesse.brandeburg@gmail.com>
> Date: Wed, 8 Feb 2006 12:07:14 -0800
>
> > this should be on netdev (cc'd), i included some of the thread here.
>  ...
> > I though Herbert had fixed these, and it looks like half the patches
> > got into 2.6.14.3, but not the fix to the fix committed on 9-6 (not in
> > 2.6.14.* at all)
>
> What are the changeset IDs so I can fix this?

I think the commit id that is missing from 2.6.14.X is
fb5f5e6e0cebd574be737334671d1aa8f170d5f3

but here is the web link if i gave the wrong info
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=fb5f5e6e0cebd574be737334671d1aa8f170d5f3

Re: KERNEL: assertion (!sk->sk_forward_alloc) failed

[David S. Miller]

From: Jesse Brandeburg <jesse.brandeburg@gmail.com>
Date: Wed, 8 Feb 2006 18:10:21 -0800

> I think the commit id that is missing from 2.6.14.X is
> fb5f5e6e0cebd574be737334671d1aa8f170d5f3

It's in 2.6.14.x I just double checked.
 

Re: KERNEL: assertion (!sk->sk_forward_alloc) failed

[Boris B. Zhmurov]

Hello, Jesse Brandeburg.

On 08.02.2006 23:07 you said the following:

> whats the relevance of e1000?
> 
> I though Herbert had fixed these

Nope :( I had this messages on 2.6.14.2 and now I have it on 2.6.15.3.


-- 
Boris B. Zhmurov
mailto: bb@kernelpanic.ru
"wget http://kernelpanic.ru/bb_public_key.pgp -O - | gpg --import"

Re: KERNEL: assertion (!sk->sk_forward_alloc) failed

[Ian McDonald]

On 2/10/06, Boris B. Zhmurov <bb@kernelpanic.ru> wrote:
> Hello, Jesse Brandeburg.
>
> On 08.02.2006 23:07 you said the following:
>
> > whats the relevance of e1000?
> >
> > I though Herbert had fixed these
>
> Nope :( I had this messages on 2.6.14.2 and now I have it on 2.6.15.3.
>
For what it's worth I had these messages for a while and they got
fixed 2 or 3 weeks ago from memory in Dave's 2.6.16 net tree or net2.6
tree.

Is it possible for you to download 2.6.16-rc2 or similar and see if it
goes away?

Ian
--
Ian McDonald
http://wand.net.nz/~iam4
WAND Network Research Group
University of Waikato
New Zealand

Re: KERNEL: assertion (!sk->sk_forward_alloc) failed

[Boris B. Zhmurov]

Hello, Ian McDonald.

On 09.02.2006 22:25 you said the following:

> Is it possible for you to download 2.6.16-rc2 or similar and see if it
> goes away?

It'll be better, if I get only patch fixs that problem, not all 2.6.16-rc2.

-- 
Boris B. Zhmurov
mailto: bb@kernelpanic.ru
"wget http://kernelpanic.ru/bb_public_key.pgp -O - | gpg --import"

Re: KERNEL: assertion (!sk->sk_forward_alloc) failed

[Ian McDonald]

On 2/10/06, Boris B. Zhmurov <bb@kernelpanic.ru> wrote:
> Hello, Ian McDonald.
>
> On 09.02.2006 22:25 you said the following:
>
> > Is it possible for you to download 2.6.16-rc2 or similar and see if it
> > goes away?
>
> It'll be better, if I get only patch fixs that problem, not all 2.6.16-rc2.
>
Oops I didn't read Jesse's message earlier properly.

That patch which probably fixed it is (from his message):
I think the commit id that is missing from 2.6.14.X is
fb5f5e6e0cebd574be737334671d1aa8f170d5f3

but here is the web link if i gave the wrong info
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=fb5f5e6e0cebd574be737334671d1aa8f170d5f3
--
Ian McDonald
http://wand.net.nz/~iam4
WAND Network Research Group
University of Waikato
New Zealand

Re: KERNEL: assertion (!sk->sk_forward_alloc) failed

[David S. Miller]

From: Ian McDonald <imcdnzl@gmail.com>
Date: Fri, 10 Feb 2006 08:37:48 +1300

> On 2/10/06, Boris B. Zhmurov <bb@kernelpanic.ru> wrote:
> > Hello, Ian McDonald.
> >
> > On 09.02.2006 22:25 you said the following:
> >
> > > Is it possible for you to download 2.6.16-rc2 or similar and see if it
> > > goes away?
> >
> > It'll be better, if I get only patch fixs that problem, not all 2.6.16-rc2.
>
> Oops I didn't read Jesse's message earlier properly.
> 
> That patch which probably fixed it is (from his message):
> I think the commit id that is missing from 2.6.14.X is
> fb5f5e6e0cebd574be737334671d1aa8f170d5f3

This patch is in the linux-2.6.14 stable tree, I just
verified this.

Re: KERNEL: assertion (!sk->sk_forward_alloc) failed

[Krzysztof Oledzki]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1036 bytes --]



On Fri, 10 Mar 2006, David S. Miller wrote:

> From: Ian McDonald <imcdnzl@gmail.com>
> Date: Fri, 10 Feb 2006 08:37:48 +1300
>
>> On 2/10/06, Boris B. Zhmurov <bb@kernelpanic.ru> wrote:
>>> Hello, Ian McDonald.
>>>
>>> On 09.02.2006 22:25 you said the following:
>>>
>>>> Is it possible for you to download 2.6.16-rc2 or similar and see if it
>>>> goes away?
>>>
>>> It'll be better, if I get only patch fixs that problem, not all 2.6.16-rc2.
>>
>> Oops I didn't read Jesse's message earlier properly.
>>
>> That patch which probably fixed it is (from his message):
>> I think the commit id that is missing from 2.6.14.X is
>> fb5f5e6e0cebd574be737334671d1aa8f170d5f3
>
> This patch is in the linux-2.6.14 stable tree, I just
> verified this.

So it must be another problem: I had this message with 2.6.15.2:

KERNEL: assertion (!sk->sk_forward_alloc) failed at net/core/stream.c (279)
KERNEL: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (148)

Best regards,

 			Krzysztof Olędzki

Re: KERNEL: assertion (!sk->sk_forward_alloc) failed

[Michal Feix]

> So it must be another problem: I had this message with 2.6.15.2:
> 
> KERNEL: assertion (!sk->sk_forward_alloc) failed at net/core/stream.c (279)
> KERNEL: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (148)
> 

Confirmed in 2.6.15.6. Exactly the same assertion in kern.log from time to time
on all my boxes with this kernel. Previous posts mentioned possible relevance
with e1000 ethernet card. Well, all these boxes has e1000 too, which probably
means nothing.

--
Michal Feix

Re: KERNEL: assertion (!sk->sk_forward_alloc) failed

[Jan-Frode Myklebust]

On 2006-02-09, Boris B. Zhmurov <bb@kernelpanic.ru> wrote:
>
>> Is it possible for you to download 2.6.16-rc2 or similar and see if it
>> goes away?
>
> It'll be better, if I get only patch fixs that problem, not all 2.6.16-rc2.

I just got this same warning on a system running 2.6.14.5. It's been
up for 50 days, quite heavily loaded, and I've seen this only once. 
Should i be conserned ? Could someone tell me what it means ?

# uname -a
Linux mail 2.6.14.5 #1 SMP Tue Dec 27 14:39:55 CET 2005 i686 i686 i386 GNU/Linux
# dmesg|grep KERNEL
KERNEL: assertion (!sk->sk_forward_alloc) failed at net/core/stream.c (279)
KERNEL: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (148)
# ethtool -k eth0
Offload parameters for eth0:
rx-checksumming: on
tx-checksumming: on
scatter-gather: on
tcp segmentation offload: on
# ethtool -k eth1
Offload parameters for eth1:
rx-checksumming: on
tx-checksumming: on
scatter-gather: on
tcp segmentation offload: on


  -jf

Re: KERNEL: assertion (!sk->sk_forward_alloc) failed

[Johan Lundgren]

I have the same problem.

Upgraded to 2.6.16-rc5, the problem does not go away.

I also have intel nics and the e1000 driver. Upgraded to the latest
driver via intel website, that didn't fix it either.

The only fix is to turn "tcp segmentation offload" off. Not a good
solution.

Anyone got any idea? Is there a patch somewhere I can apply that
should fix this?

Regards,
Johan

KERNEL: assertion (!sk->sk_forward_alloc) failed

[Mark Nipper]

        I received the following in my system logs recently:
---
Nov 27 22:56:20 king kernel: KERNEL: assertion (!sk->sk_forward_alloc) failed at net/core/stream.c (279)
Nov 27 22:56:20 king kernel: KERNEL: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (151)

        All I could find related to this was some potential bugs
mentioned in 2.6.9 and in particular with relation to TSO.
However, I'm running a vanilla 2.6.13.4 at the moment.  But, I do
have an e1000 and checking ethtool does show TSO on.

        Anyway, ignore if this is unimportant.  The machine is
still up and running, so it doesn't appear to be fatal.  Let me
know if you need my .config or output from dmesg or whatever.  I
guess I'll upgrade to 2.6.14.? or wait for 2.6.15.[12] just to be
safe!

-- 
Mark Nipper                                                e-contacts:
832 Tanglewood Drive                                nipsy@bitgnome.net
Bryan, Texas 77802-4013                     http://nipsy.bitgnome.net/
(979)575-3193                      AIM/Yahoo: texasnipsy ICQ: 66971617

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GG/IT d- s++:+ a- C++$ UBL++++$ P--->+++ L+++$ !E---
W++(--) N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--)
Y+ PGP t+ 5 X R tv b+++@ DI+(++) D+ G e h r++ y+(**)
------END GEEK CODE BLOCK------

---begin random quote of the moment---
"They that can give up essential liberty to obtain a little
temporary safety deserve neither liberty nor safety."
 -- Benjamin Franklin, _Historical Review of Pennsylvania_, 1759
----end random quote of the moment----

Re: KERNEL: assertion (!sk->sk_forward_alloc) failed

[Miquel van Smoorenburg]

In article <20051128123601.GA32346@king.bitgnome.net>,
Mark Nipper  <nipsy@bitgnome.net> wrote:
>        I received the following in my system logs recently:
>---
>Nov 27 22:56:20 king kernel: KERNEL: assertion (!sk->sk_forward_alloc)
>failed at net/core/stream.c (279)
>Nov 27 22:56:20 king kernel: KERNEL: assertion (!sk->sk_forward_alloc)
>failed at net/ipv4/af_inet.c (151)
>
>        All I could find related to this was some potential bugs
>mentioned in 2.6.9 and in particular with relation to TSO.
>However, I'm running a vanilla 2.6.13.4 at the moment.  But, I do
>have an e1000 and checking ethtool does show TSO on.

I'm seeing the same on 2.6.14.2, also with e1000. It wasn't there on
2.6.11.12 which I was running previously.

# dmesg | tail -4
KERNEL: assertion (!sk->sk_forward_alloc) failed at net/core/stream.c (279)
KERNEL: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (148)
KERNEL: assertion (!sk->sk_forward_alloc) failed at net/core/stream.c (279)
KERNEL: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (148)

# ethtool -k eth0
Offload parameters for eth0:
rx-checksumming: on
tx-checksumming: on
scatter-gather: on
tcp segmentation offload: on

Mike.

Re: KERNEL: assertion (!sk->sk_forward_alloc) failed

[Jesse Brandeburg]

This should really be on netdev, so I copied it.

On 11/28/05, Miquel van Smoorenburg <miquels@cistron.nl> wrote:
> In article <20051128123601.GA32346@king.bitgnome.net>,
> Mark Nipper  <nipsy@bitgnome.net> wrote:
> >        I received the following in my system logs recently:
> >---
> >Nov 27 22:56:20 king kernel: KERNEL: assertion (!sk->sk_forward_alloc)
> >failed at net/core/stream.c (279)
> >Nov 27 22:56:20 king kernel: KERNEL: assertion (!sk->sk_forward_alloc)
> >failed at net/ipv4/af_inet.c (151)
> >
> >        All I could find related to this was some potential bugs
> >mentioned in 2.6.9 and in particular with relation to TSO.
> >However, I'm running a vanilla 2.6.13.4 at the moment.  But, I do
> >have an e1000 and checking ethtool does show TSO on.
>
> I'm seeing the same on 2.6.14.2, also with e1000. It wasn't there on
> 2.6.11.12 which I was running previously.

I don't believe this is related to e1000 because we don't mess with
the sock (sk) struct.  Did you try disabling TSO?  I bet the netdev
guys can help.