Latest -current complete lockup (tcp changes?)
Andrey Chernov
ache at freebsd.org
Tue Mar 27 05:28:13 UTC 2007
On Tue, Mar 27, 2007 at 10:11:01PM +0000, Garrett Cooper wrote:
> > The problem is deeper than that (((
> > I still got the same lockup, just with more net activity.
> > I even try to completely disable sack, with the same result, so probem is
> > somewhere else. Last working kernel still from Mar 22.
>
> I'll give a CVSup / upgrade a try and see what happens.
Additional non-default details from my machine which may (or may not)
affect the thing:
net.inet.tcp.recvspace:
65536
->
65160
net.inet.tcp.sendspace:
32768
->
65160
net.inet.tcp.keepidle:
7200000
->
600000
net.inet.ip.ttl:
64
->
128
kern.ipc.somaxconn:
128
->
1024
net.inet.tcp.blackhole:
0
->
2
net.inet.udp.blackhole:
0
->
1
net.inet.tcp.mssdflt:
512
->
1460
fxp0: Microcode loaded, int_delay: 1000 usec bundle_max: 6
fxp0: flags=9843<UP,BROADCAST,RUNNING,SIMPLEX,LINK0,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether xx:xx:xx:xx:xx:xx
inet xxx.xx.xx.xx netmask 0xffffff00 broadcast xxx.xx.xx.xxx
inet xxx.xx.xx.xx netmask 0xffffffff broadcast xxx.xx.xx.xx
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
Additional routing options:
ignore ICMP redirect=YES
--
http://ache.pp.ru/
More information about the freebsd-current
mailing list