The bad news is that I haven't yet been able to capture traces.
Once every three days or so I get a crash of 2.6.18-rc[67] which
*probably* end in tcp_ack(), but I don't have the exact dump.
My .config is indeed heavy on TCP congestion stuff:
$ zcat /proc/config.gz | grep -i tcp
CONFIG_INET_TCP_DIAG=y
CONFIG_TCP_CONG_ADVANCED=y
# TCP congestion control
CONFIG_TCP_CONG_BIC=y
CONFIG_TCP_CONG_CUBIC=y
CONFIG_TCP_CONG_WESTWOOD=y
CONFIG_TCP_CONG_HTCP=y
CONFIG_TCP_CONG_HSTCP=y
CONFIG_TCP_CONG_HYBLA=y
CONFIG_TCP_CONG_VEGAS=y
CONFIG_TCP_CONG_SCALABLE=y
CONFIG_TCP_CONG_LP=y
CONFIG_TCP_CONG_VENO=y
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m
CONFIG_IP_NF_TARGET_TCPMSS=y
# CONFIG_NET_TCPPROBE is not set
# CONFIG_ISCSI_TCP is not set
# CONFIG_NFSD_TCP is not set
However, I haven't specifically configured anything.
$ dmesg | grep -i tcp
[ 33.106317] TCP established hash table entries: 131072 (order: 8, 1048576
bytes)
[ 33.107086] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[ 33.107476] TCP: Hash tables configured (established 131072 bind 65536)
[ 33.107605] TCP reno registered
[ 40.985770] IPVS: Registered protocols (TCP, UDP, AH, ESP)
[ 41.105710] TCP bic registered
[ 41.105833] TCP cubic registered
[ 41.105957] TCP westwood registered
[ 41.106080] TCP highspeed registered
[ 41.106203] TCP hybla registered
[ 41.106328] TCP htcp registered
[ 41.106452] TCP vegas registered
[ 41.106574] TCP veno registered
[ 41.106698] TCP scalable registered
[ 41.106822] TCP lp registered
$ cat ipv4/tcp_congestion_control
lp
I hope to follow up this message with the actual backtrace, but this is
already an heads up.
Sorry for not yet being able to be more specific.
bert
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://netherlabs.nl Open and Closed source services
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
