Date: Sat, 20 Aug 2011 16:58:59 -0700 From: =?iso-8859-1?Q?Ask_Bj=F8rn_Hansen?= <ask@develooper.com> To: =?iso-8859-1?Q?Ask_Bj=F8rn_Hansen?= <ask@develooper.com> Cc: embedded@freebsd.org, net@freebsd.org Subject: Hang with ZERO_COPY_SOCKETS or TCP_SIGNATURE enabled? (was: system locks up with vr driver on alix board) Message-ID: <865C098E-2A24-481B-9B97-2E426AE481CB@develooper.com> In-Reply-To: <F1B3D7C0-6AC7-4C10-9C99-AAC6A89D8415@develooper.com> References: <D8B41107-90ED-4357-A7DA-4FF987C70567@develooper.com> <4E4AB3BE.4090603@sentex.net> <9255C71C-BB78-417E-A900-85140FC2050C@develooper.com> <20110817002911.GA7614@michelle.cdnetworks.com> <C64CDCB3-A1DE-48CF-BEE5-54BA7084B3CB@develooper.com> <F1B3D7C0-6AC7-4C10-9C99-AAC6A89D8415@develooper.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 17, 2011, at 7:52, Ask Bj=F8rn Hansen wrote: > Grasping at straws here, but when enabling BREAK_TO_DEBUGGER I noticed = that the kernel had ZERO_COPY_SOCKETS and TCP_SIGNATURE enabled. I = disabled those, "just in case". Hi everyone, Thanks again for your help and hints getting this fixed for me. I just wanted to send an update that those kernel options seemed to be = the ticket to make it stable again. I haven't had it hang since = disabling IPSEC, ZERO_COPY_SOCKETS and TCP_SIGNATURE (I wasn't using md5 = signatures, having any ipsec sessions or to my knowledge running any = applications that'd be using zero copy sockets). - ask=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?865C098E-2A24-481B-9B97-2E426AE481CB>