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 [email protected]
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----
In article <[email protected]>,
Mark Nipper <[email protected]> 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.
This should really be on netdev, so I copied it.
On 11/28/05, Miquel van Smoorenburg <[email protected]> wrote:
> In article <[email protected]>,
> Mark Nipper <[email protected]> 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.