[트러블슈팅]KERNEL: assertion (!sk->sk_forward_alloc) failed at net/core/stream.c (279) and net/ipv4/af_inet.c (148)

 

# dmesg
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)
# uname -r
2.6.14.1
http://lkml.org/lkml/2006/2/8/300
e1000? and 2.6.14 related
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?
금일 커널 stable 버전은 2.6.23
2.6.17 이상을 쓰면 좋겠군요. 얼마나 크게 문제가 되는지는 모르겠지만 말입니다.
http://www.mail-archive.com/netdev@vger.kernel.org/msg06380.html
http://bugzilla.kernel.org/show_bug.cgi?id=5946
Please retest with 2.6.17-rc1. Davem and Hubert found several errors in e1000
driver. One of them would have caused this error.
This patch is already in 2.6.16 and later
http://www.mail-archive.com/netdev@vger.kernel.org/msg09795.html
E1000 has some TSO bug most likely, try reproducing with
"ethtool -K eth0 tso off", replacing "eth0" with your actual
e1000 interface name(s).
Can someone explain to me the
possible relation of e1000 (and maybe TSO) and sk->sk_forward_alloc?
http://kerneltrap.org/node/397
tcp segmentation offload (or TCP Large Send)
e1000 support for TSO under Linux
os - network - e1000 - tso bug - dmesg - warn? or error? or critical?
http://www.fi.muni.cz/~kas/blog/index.cgi/2005/09/index.html
Surprisingly enough, the tests without TSO were faster than with it enabled.